jhmattern

I did that several times with the plugin itself and it didn’t prevent this from happening. Did you delete it via FTP or something instead?

This is happening on my site too. I disabled all plugins and re-enabled one at a time to discover it’s WP fastest cache causing this error. It doesn’t appear when I’m logged into the site, but all logged out users see it.

A user took a screenshot of what appeared before I disabled your plugin. You can see that at the link below if it helps.

https://pbs.twimg.com/media/CMDRpO1UwAA3n5z.png:large

The same thing just happened to me. I signed up for this to test it out, hoping I could recommend it to my blog’s readers. But on the very first test, instead of updating a plugin, it deleted it. That was the Contact Form 7 plugin. I’m just glad I ran the test with a single plugin on a single site before testing mass updates.

I’m having the same issue with the button text. The upgrade caused the button text color to change (not the bar text color). It almost matches the button background color now, so it seems to vanish.

I just wanted to add my voice to the choir here. I updated this morning to 2.6 and now I’m suddenly getting a lot of spam comments when I previously didn’t get any at all with your plugin.

Yeah, you definitely need both of those settings — logged-in users checked and browser caching unchecked. I’m glad you got it working. ??

And I agree. It would be nice if browser caching could still be enabled for logged-in users. I don’t know much about it, flushing the cache on login would be great if it can be done. Either that or limiting caching to no more than a second for certain pages or sections of a site.

Olly, I mentioned it in another thread, but I figured out the issue. It’s the browser cache settings that cause the problem. Logged in users are seeing the cached version saved in their browser instead of the cached version served by the site, which is why the setting to not show cached pages to logged-in users doesn’t work. Disable the browser caching option in WPFC and the login problems go away completely.

It’s not ideal because you lose some optimization. But perhaps you can manually tweak the browser cache timing to get similar results. If so, I hope you’ll share it here. Maybe then we could get the defaults tweaked so people don’t run into this issue. Thankfully the slow-down was minimal when I turned mine off (less than a .2 second decrease in speed, though mileage may vary).

Double-check your .htaccess file, especially if you let this or another plugin leverage browser caching at one point. It took me weeks to troubleshoot this on a site with bbPress forum members.

They would visit the forum, click the login link, and log in. It would automatically send them back to the forum page, where they were given the login link again as though they were logged out. Going to another forum page would show them logged in however. They were simply being shown a cached version of the original page they visited, even though the setting was checked to prevent that for logged-in users.

When I unchecked the leverage browser caching option in my plugin settings, the settings weren’t automatically removed from my .htaccess file. I had to go in manually and remove them. When I did, member logins worked correctly again.

While there’s no guarantee that your problem is the same, I figure it’s worth take a look. I can now have everything enabled other than the browser caching, and login works fine again. ??

Quick update: I had the same issue with the bulk title editor’s “save all” link. But I am able to hit the “save” link for each individual entry, and it saves fine (and thankfully doing so keeps the other entries in place waiting to be saved).

I’m having this issue with the “save all” link in the bulk description editor. I just wrote dozens of descriptions, hit “save all,” and it jumped to the top of the page without saving anything. It didn’t delete what I typed. It just isn’t saving.

I’m not comfortable sending theme files for a premium theme without the dev’s permission. Let me look into this more over the next several days as I have a little more time. I’ll follow-up here again next week whether I fix it or not to update you. And if I’m still having the same problem, I’ll grant you access to the site itself so you can take a look at whatever you need to see. ??

I’m not sure what you mean. The only way I use gzip is by checking that option with your plugin. If you’re asking if I’ve implemented it manually or something, then no. Just through wpfc.

I did try it with plugins disabled, and it doesn’t seem to be a plugin conflict.

I did empty the cache/all folder after upgrading the plugin. I tried a few times. First I emptied it from the plugin before upgrading it in WordPress. That didn’t help. The second time (after reverting to the older version), I did this manually — deleted the entire cache folder on the server, deleted the old plugin, and manually installed the new one. That also didn’t help. Only one file ever gets put in the cache/all folder with the new versions — the index file. And the content of that file looked very different from the one I get with the older version.

I’m a bit swamped with work this week so I don’t want to attempt the upgrade again yet and risk slowing the site down. If I have time this weekend I’ll do it again and see if I can give you any further info about what’s in the index file I get with the new version.

I do use gzip compression. That’s always worked fine with the older version. Should I try disabling it in the newer ones?

Hopefully Kramarz. It’s not a plugin conflict. I disabled them. And there haven’t been any theme changes since the problem started. It was solely tied to upgrading this plugin. If 0.8.1.5 is working perfectly and the two newer versions aren’t, the problem is in the plugin changes somewhere. If I have time before the dev is back, I’ll try to check the specific file changes between the plugin upgrades and see if I can figure something out.

I checked with the guy behind my caching plugin and he said his plugin doesn’t cache images so it shouldn’t have affected them. So I disabled your plugin for a while. It couldn’t have been anything in functions.php either because the problem happened even when I switched to the default theme, so those settings wouldn’t have been active.

When your latest update came out I updated and reactivated it. I ran fresh tests and it seems to be resolved now. No idea what you changed or how it might have affected it, but something got sorted somewhere along the line. So there’s no problem at this point. ??