M Asif Rahman

comment out this “/wp-content/plugins/w3-total-cache/inc/functions/activation.php on line 127”

You dashboard will be accessible. Then deactivate the plugin, activate again, and configure if needed.

Version 0.9.2.8 released few hours ago. Now custom hostname works perfectly. Just the test button still does not work.

Folder permission thing got changed. As an effort to fix the exploit, plugin Author trying to harden the security. Deactivate and Activate again should work. Either give temporary full read-write(777) permission to “wp-content” but must be for a very limited time. Or follow the guide and change code as necessary and advised by W3TC itself.

I guess it was working before and you suddenly started getting error after update. Deactivate then activate again. You could give “777” – read-write-all permission to “wp-content” folder and try to auto install. BTW you have to go back to original permission, should be minimum “644”. Or you could follow the code you need to change in all .htaccess. If you use CDN you probably will still have error. You could check the blog post I wrote how to solve this issue with CDN.

If you could get access to your dashboard, you should deactivate the plugin and activate again. Then I checked all the setting again, and it worked for me. Only thing that had issue is CDN. Issues been discussed at this support thread, specially about MaxCDN or NetDNA. I have wrote a detail blog post about how to solve.

So for now use your “temporary url” from MaxCDN/NetDNA, it will be a large url like “zonename.alias.maxcdn-cdn.com” or “zonename.alias.netdna-cdn.com“. And then CDN will work with W3 Total Cache.

I have made a blog post with detail instruction and graphics at my blog Asif.im

in WP-Polls option page look for “Logging Method” select “Do not log” as “Poll Logging Method”. Now user will be able to vote unlimited times. I know its not an ideal option.

Version 2.4 will not help.

Read my reply on the other thread. And read the full FAQ by Alex

https://alexking.org/blog/2012/10/12/twitter-tools-3-0-faq

Version 2.4 will not help. Its all about Twitter actually. Alex already responded and clear things. Twitter shutdown the old API endpoint on October 11. So all plugins like Twitter Tools was not working. And it will not work anymore. What Alex did is a simple try and start of a new process to make it work. If you want to complain do that with Twitter. Here Alex is the guy who made this wonderful plugin, he have to be thankful to him. He is still trying to get this around.

Use HotFix or this one file plugins, I have posted in my blog with all links
Check – https://asif2bd.info/2012/09/11/solution-wordpress-custom-fields-broken-after-3-4-2-update/

Use HotFix or this one file plugins, I have posted in my blog with all links
Check – https://asif2bd.info/2012/09/11/solution-wordpress-custom-fields-broken-after-3-4-2-update/

I think this will be very nice and very useful feature.

It seems resolved after version 1.7.1 released.

But Still multiple try could happen, maybe just bypassing auth cookie.

How about keeping IP and username in table? and block IP in the first place after lockout?

And about site behind proxy?

Yes, and Its not because of your caching for sure. And our test shows if you call that ajax link directly from browser, still it does not increase view count. Error log says the call url most likely not working perfectly.

Did you tested downgrading?

Not recommending 100%, but it could solve issue.

https://www.ads-software.com/extend/plugins/ajax-the-views/

Be aware about server resource usage.