Articles not displaying after update

  • Resolved ABX

    (@buddha1822)


    1 month, 3 weeks ago

    Tried updating to the latest version of the plugin 2.7.6 this week. But encountered some major issues where pages were not displaying at all. I have never had any issues with the plugin before and never had this kind of problem. I had to rollback to the previous 2.7.5 version today and things seem to have cleared up. One reader told me they tried to click to Page 2 on the homepage and got a basic 500 “not found” error. I noticed there was NO more traffic on the main website at all, nothing hitting, none of the pages seem to be loading for anyone. Only when I disabled the plugin and rolled it back did it seem to get back to normal. The problem is other than this page loading issue I can’t find any other errors or explanations or details on what was going on. I know something was SERIOUSLY broken because traffic had dropped by about 80% and returned after rolling back. But that’s all I have on this – something is not working correctly within 2.7.6.

    My first guess is some cache validation issue with the browser cache. Some people are seeing this error because the page / browser cache isn’t correctly syncing and when the user (who has been to that page before) clicks onto Page 2 they get an error because the cache isn’t working correctly. Others who visit the pages for the first time don’t have any browser cache saved and do get a working page. It’s the only explanation that makes sense thinking about it without finding more errors. I run an nginx server with MariaDB and all the usual – my WordPress and PHP is fully updated.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @buddha1822

    I am sorry about the issue you are experiencing and I am happy to help!

    Can you please sahre the content of the wp-content/w3tc-config/master.php so I can check which settings are enabled.
    Also, have you purged the cache after the latest update and if not can you please let me know if the problem persits after the cache is purged?
    It would be great if you could share the website URL

    Thanks!

    Thread Starter ABX

    (@buddha1822)

    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, 3 weeks ago by ABX.
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @buddha1822

    Thank you for your feedback.

    Can you please share the website URL? Also, I understand that the same settings are enabled, so I was wonering if you can share the master.php of the know working version of the plugin

    Thanks!

    Thread Starter ABX

    (@buddha1822)

    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.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @buddha1822

    Thank you for your feedback.

    I’ve checked your website and what I can see from the source is Page Caching using Redis (Page is front page)
    This means that the Page Caching is disabled for the Front page. This being said the issue may be with Redis or a corrupted installation.
    The master.php should not be empty. This file contains the configuration of the W3 Total Cache.
    This may be an environment problem. Is there a chance you can upgrade to the most recent version and restart the Redis service and let me know if the issue persists?
    Thanks!

    Thread Starter ABX

    (@buddha1822)

    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.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @buddha1822

    Thank you for your feedback.
    Since the pages are not cached, the most likely reason may be that the DB cache or Object Cache and the Redis service that needs to be restarted.
    I understand that this caused issues however, this is the only problem of this kind reported after the release and we were unable to replicate the problem for the similar type of website.
    It would be great if you could troubleshoot further and test the things mentioned my previous reply, so we can get to the bottom of this.
    I understand that you may not be willing to spend time on this, and I assure you that we are making tests and making sure that the release is stable and we are looking for any issues.

    Thanks!

    Thread Starter ABX

    (@buddha1822)

    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.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @buddha1822

    Thank you for your feedback.
    I am not sauing that the issue is related to the page cache not running corrdctly, I’ve stated the oposite.
    Since the pages are not cached, the problem is NOT with the Page Cache and this is what I am stating.
    Again, I understand your concern and caution. What I would advise is to make a backup of the wp-contnent/w3tc-content/master.php and remove the W3 Total Cache completly

    1. Check .htaccess File (make backup)
    W3TC will create many directives in .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
    Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
    2. Delete wp-content files and folders
    – cache folder
    – w3tc-config folder
    – object-cache.php (if exists)
    – advanced-cache.php (if exists)
    – db.php (if exists)
    – upgrade folder
    – delete w3-total-cache folder in wp-content/plugins/ (if exists)

    1. Delete Cached Files from CDN (if using CDN)
      Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
    2. Go to your wp dashboard and re-install the fresh latest of the W3 Total Cache

    The clean install will be installed and you can check for issues (no worries you can aloways disable the plugin)
    If the issue is gone (check the incoignito and other browsers while logged out) You can enable the settings one by one and after each one after purging the cache check the website.
    We would like to troubleshoot this with you, however, as we do not have access, It would be great if you could check this.
    You can always disable the plugin if the issue occurs, or revert back the settings that may cause the problem

    Thanks!

    Thread Starter ABX

    (@buddha1822)

    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.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @buddha1822

    Thank you for your feedback.

    We are working on the furure update so please wait for the next update and report back if you see any issues.
    Thanks!

    Thread Starter ABX

    (@buddha1822)

    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??

Viewing 12 replies - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.