ABX

I’m also running PHP 8.3.X on my server and hoping for an improve AIOSEO plugin without any errors showing up. Hopefully the final patch / update will be ready soon. Thank you.

Doing some additional deep research and found a set of errors that are appearing with W3TC cache plugin now. I’m still downgraded and running W3TC 2.7.5. But still getting this error. We upgraded to PHP 8.3.12 from 8.1.X and getting these PHP errors. No idea how to fix or analyze them from here and every time we try updating W3TC again it causes more problems & we lose lots of traffic.

[19-Oct-2024 10:46:56 UTC] PHP Fatal error: Uncaught Error: Class “\W3TC\BrowserCache_Core” not found in /releases/web/wp-content/plugins/w3-total-cache/Dispatcher.php:16
Stack trace: 0 /releases/web/wp-content/plugins/w3-total-cache/BrowserCache_Plugin.php(328): W3TC\Dispatcher::component() 1 /releases/web/wp-content/plugins/w3-total-cache/BrowserCache_Plugin.php(198): W3TC\BrowserCache_Plugin->_get_url_mutation_operations() 2 [internal function]: W3TC\BrowserCache_Plugin->link_replace_callback() 3 /releases/web/wp-content/plugins/w3-total-cache/BrowserCache_Plugin.php(168): preg_replace_callback() 4 [internal function]: W3TC\BrowserCache_Plugin->ob_callback() 5 /releases/web/wp-content/plugins/w3-total-cache/Util_Bus.php(21): call_user_func() 6 /releases/web/wp-content/plugins/w3-total-cache/Generic_Plugin.php(535): W3TC\Util_Bus::do_ob_callbacks() 7 [internal function]: W3TC\Generic_Plugin->ob_callback() 8 /releases/web/wp-includes/functions.php(5427): ob_end_flush() 9 /releases/web/wp-includes/class-wp-hook.php(324): wp_ob_end_flush_all() 10 /releases/web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 11 /releases/web/wp-includes/plugin.php(517): WP_Hook->do_action() 12 /releases/web/wp-includes/load.php(1280): do_action() 13 [internal function]: shutdown_action_hook() 14 {main}
thrown in /releases/web/wp-content/plugins/w3-total-cache/Dispatcher.php on line 16

Any idea what’s wrong and why we’re getting this error??

I already did all of this and already tested everything. We run an nginx server we don’t have htaccess files – I already listed this in the first post. It’s nothing wrong with the server, something is wrong with the plugin and since we’re not making any progress here I won’t add anything else until there’s a new version updated to test then. Thank you.

No sorry you are wrong. It has NOTHING to do with this front page cache not running correctly. It’s not a matter of time it’s a matter of danger – I can’t risk having pages not loading like this. We already tried to investigate errors but couldn’t find much, all I know is that we had a MASSIVE traffic drop which is VERY harmful and pages were sending back a 500 error without any clear explanation – all of this after the most recent update.

At the moment I cannot take this risk with the plugin and lose traffic again. It was REALLY bad. And not easy to debug since there was no error but it was seriously noticeable until I turned off the plugin and rolled back. There’s too much danger. We can try restarting redis but I don’t think it’ll fix everything that simply. Something is wrong with this latest plugin version.

Yes the front page is not cached because we kept having readers say they weren’t seeing new posts on the front page as soon as they were published. The front page is not the issue, it’s clicking to any OTHER pages that would not work and give “not found” messages.

I am using the working version of the plugin and there’s still nothing in the master.php file when I go there. It shows nothing. The website is https://onfs.net/3zB1hZ9.

Yes of course I purged the cache! It doesn’t matter. For nearly 24-48 hours I was missing a large amount of traffic because the website was giving this error – no matter how many times I purged the cache or updated changes or otherwise.

I tried checking the master.php file and it’s blank. I have no idea why. No errors it just shows a blank page. I have already downgraded the W3TC back to 2.7.5. And for the record, all of my settings have remained the same for a year and I haven’t changed anything. But after this recent 2.7.6 update, nothing is working correctly. Despite the same settings as before.

• This reply was modified 1 month, 4 weeks ago by ABX.

Also – testing the wp-json system, everything works fine. WordPress is not blocking it or disabling anything with the REST API system. I don’t use a firewall plugin or disabler. I can get a response by visiting https://www.MYSITE.com/wp-json/disqus/v1/ meaning it works. However, the /webhook page gives a 404 error, /settings gives a 401 error. And I’ve double checked server configs and nothing is blocking either. Not really sure where else to check or what else to do with the server, so strange…

Is there any support for this? Any help solving these problems? I had to uninstall the plugin because it keeps breaking like this… And no support, no fixes. No idea what to do about this.

Thank you for the fast response. I am thinking that the original sitemap file size being so large is not a good idea. But I don’t know what the best practice is for SEO and for best performance of the site. But if you recommend 100 per page, this might be what I will try and see what happens.

Yep that’s the exact version I’m still using. Too afraid to upgrade… Can’t take the risk. But 4.1.1 works nicely and doesn’t cause any problems.

STILL getting the same Telegram error in .29 despite an investigation. And now Twitter “works” but it runs WAY slower than before. Don’t think much has been fixed yet with this…

Thank you for the help solving this. Hopefully we can figure out what’s going on. I’ve submitted my support request on your site, not sure what else there is to do now.

Yes but then this sounds like something is wrong with your latest versions and the way you’ve changed the Twitter API in the plugin. Maybe you need some fallback code that allows BOTH old AND new accounts to still properly use and work with the new Twitter API. Because it seems all the old accounts are broken and old systems don’t work with the upgraded plugin.

Support request has been submitted.

Actually no this is wrong. I shifted both of my Twitter apps under a “Project” as your “Known Issues” page explained. This did NOT fix anything within versions .28 or .29. But when I downgraded to .26 it still works perfectly fine. Even without your new Twitter API upgrade, it still sends tweets perfectly fine after switching over to the “Projects”. The problem is with the plugin, not with the Twitter app switch. Even after making the switch, .28 and .29 are still broken. Sorry.

• This reply was modified 2 years, 4 months ago by ABX.