Latest update totally broken

BTW, the text shown in the screenshot showed up at the very bottom of the page under the footer.

Yikes! I’ve not seen it do that before. So sorry for the problem! Did you happen to check the javascript console for errors when that happened? It would help me greatly if you could check that and let me know what error you’re getting. Did that happen when you clicked on a link, or just when you loaded the page after updating?

I’ll help any way that I can, and if we need to leave it alone until a maintenance window, I’ll gladly work with you on timing.

It happened only when clicking on an external link. I’m not going to update the plugin for now because it’s a banking website and the external links are going to the customer online banking sites. The bank alerted me to the problem this morning and they were quite upset, so I’m not touching it since it’s working correctly using the older version of the plugin. I did not check anything – just wanted to get it working for them and I knew it was working last week so I just reinstalled the old version from a backup.

I may know what happened. You’re using WP Fastest Cache, and if the old plugin files were still cached, I could see getting the result you’ve gotten. Can you try upgrading the plugin again and immediately deleting the cache on the second tab “Delete Cache” of the WP Fastest Cache settings page?

Please give that a try and let me know if that fixes it for you.

Just saw your previous post and I completely understand. If you could test that sometime I’d love to know if that’s the problem or if I’ve got something else to fix.

Again, so sorry for the problem, and I’ll be more than happy to help in any way that I can. If you want to schedule a time with me I’d be glad to help during a maintenance window or something.

• This reply was modified 5 years, 11 months ago by Curtis V. Schleich.

First thing I tried when I saw the problem was flushing the cache to see if that fixed it but it didn’t. I’ll try clearing the cache, updating and then clearing again, but I want to wait until later tonight.

Okay, flushing the cache the first time didn’t help, but I just updated the plugin successfully after doing multiple cache flushes before and immediately after updating. So basically it would appear that the cache did not totally clear out this morning when we first had the problem. So thank you and problem solved.

Outstanding! So glad it was simple. I always get nervous updating software that so many people use in so many different contexts. You just never know when there will be some kind of interaction like this. I’ll add a note at my next update to make sure people using caching clear it thoroughly after the update. I’m sure in this case the version 1.4 to 1.5 was a problem that others may see because I updated the jAlert component and it changed the file names of included files.

Thanks so much for your quick testing and information. I really appreciate it!