W3 Total Cache Upgrade with Port 80 Issues

  • We updated the W3 Total Cache plugin to the last version v0.9.5. We had installed v0.9.4.1 and did not have any problems at all. Our website is configured to work on port 80 and 443 and for some reason, it doesn’t updates cache, only on port 80 version, after a recent post is published.

    Is there any solution for this issue?

    Thanks, Carlos.

Viewing 9 replies - 1 through 9 (of 9 total)

  • For anyone in the future wondering port 80 handles all normal internet traffic all your http taffic while port 443 handles your SSL traffic.

    So did you set in the page cache settings there to be an alias for https and make sure to cache http and https pages uniquely?

    Thread Starter carloscaro

    (@carloscaro)

    Great! Just added the alias on page cache settings for http version (port 80) and now is working properly. Thank you so much!

    Thread Starter carloscaro

    (@carloscaro)

    One last question, if I enable the option: Cache SSL (https) requests / Cache SSL requests (uniquely) for improved performance and leave the http alias enabled, will still work?

    Yes the alias feature is to tell W3TC to clear the cache of say https and http that way users who are on https don’t get stale content while those on http still get regular content.

    Thread Starter carloscaro

    (@carloscaro)

    Sorry! Still with problems. Because I changed the page cache settings, I had to reset the cache manually and it worked for every version. But after that happend, we published a new post and the cache was generated for the https version but not for port 80. The strange part is that we have all configured to work on http and it works only for https. Any other suggestions?

    Did you try visiting the page on the http version to see if it cached it then. You could also try disabling the disable https uniquely for improved performance option (after that) which is odd its not working in the way i thought it would.

    Thread Starter carloscaro

    (@carloscaro)

    Yes, I visit the http version and compare it with https and they are different. The most recent post is not showing on http version. We didn’t have this problem on v0.9.4.1. What else could I do? Because if there isn’t a solution I think I will go back to the last version.

    In case of doing a downgrade, I just need to replace actual plugin folder with last version, delete the advanced-cache file in /wp-content/ folder, re-activate the plugin and finally, clear all cache, right? Thanks!

    Hi,
    in “Live Trafic” of Wordfence plugin, show this message:

    “Notice: Undefined index: HTTP_REFERER in /home/talenzo/wp-content/plugins/w3-total-cache/DbCache_WpdbInjection_QueryCaching.php on line 366”

    Thanks.

    • This reply was modified 8 years, 5 months ago by felibv.
    • This reply was modified 8 years, 5 months ago by felibv.
    Thread Starter carloscaro

    (@carloscaro)

    I had to revert my installation and did a downgrade to v0.9.4.1. It seems that is working now only for http, had to enable the “Cache SSL (https) requests” option and at this time it’s doing cache for https only and not for http :(.

    I saw this error on the logs today:

    PHP Fatal error: Call to undefined function w3_is_database_error() in /wp-content/plugins/w3-total-cache/lib/W3/Plugin/TotalCache.php on line 516

    Any ideas?

    • This reply was modified 8 years, 5 months ago by carloscaro.
Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘W3 Total Cache Upgrade with Port 80 Issues’ is closed to new replies.