ksaveras
Forum Replies Created
-
something like this:
RewriteCond %{REQUEST_URI} (timthumb\.php|phpthumb\.php|thumb\.php|thumbs\.php) [NC] RewriteCond %{HTTP_REFERER} ^.*mysite.tld.*I vote for support several keywords in SEO analysis
Forum: Plugins
In reply to: [W3 Total Cache] [Plugin: W3 Total Cache] TC do not detect user logouthughra, You should identify Your problem. Update to latest version plugins. Disable all plugins, enable W3TC, test. If it does not work – perhaps starting from fresh install would be solution.
Enable one plugin, test. Enable second plugin, test … etc.My post was about concrete problem when several plugins used ‘wordpress’ in their cookie names and I used debugging tools to find out the problem.
It does not mean that it will work for all problems. It it did not help You it means that problem is another.Forum: Plugins
In reply to: [W3 Total Cache] [Plugin: W3 Total Cache] TC do not detect user logoutThis plugins does not work fine with other plugins that use ‘wordpress’ word in their cookie names.
I had same problem as previously persons. Quick story:
2 browsers: FF(10) and IE(9), WP 3.3.1
FF open wp page, login and enable W3TC – (cache user logged in is disabled).
Open front page, other pages, posts – Page Caching using disk: enhanced (User is logged in) This is good.
Open IE, user is NOT logged in, cleared caches, open pages – Page Caching using disk: enhanced (User is logged in) WTF? User is NOT logged in.Ok browsed google for answers found this topic. Strange – no solution.
Tried to see myself why W3TC thinks that user is logged in. Looked for code where it echoed that he thinks that user is logged in and found that cookie name is checked if it starts with ‘wordpress’ text. BTW – developers aren’t really smart and good – some code is repeated twice and this is not best practice example. Ok I left this as is.
Hmm next question – why W3TC founds cookie with ‘wordpress’ start in cookie names? Quick press F12 in IE and use developers tools. I found that Polylang plugin sets last used language in user cookie. Yes it’s good for Polylang users, but breaks W3TC.
Who to blame? If register Polylang issue, then maybe there are other plugins that also use ‘wordpress’ start string in their cookie names? I don’t want to find them all.
If W3TC could change cookie name checking – maybe this could solve the problem? Sounds good.
Examined WP cookies when user is logged in and not logged in. Found that special wordpress_logged_in_{hash} cookie exists at the same time with wordpress_{hash} cookie when user is logged in and they both are absent when user is logged off.File: lib/W3/PgCache.php
748: if (strpos($cookie_name, ‘wordpress’) === 0) {
changed to
748: if (strpos($cookie_name, ‘wordpress_logged_in’) === 0) {File: lib/W3/Db.php
614: if (strpos($cookie_name, ‘wordpress’) === 0) {
changed to
614: if (strpos($cookie_name, ‘wordpress_logged_in’) === 0) {Tested again with FF and IE – now results are much better and functionality looks not broken.
Now developers should reject or accept this change.
Forum: Fixing WordPress
In reply to: duplicate headers -> errorfile: wp-includes/functions.php
line: 746
comment line
@header(“Status: $header $text”);make it:
//@header(“Status: $header $text”);it works for me.