• Resolved paulg2555

    (@paulg2555)


    This probably has been mentioned before, if so, I’m sorry, but I cannot find any solution.

    Problem: The backend views get counted and updated normally. Front-end displays a whole different thing, a much older count.

    Settings: Vanilla WordPress site with Autoptimize, W3 total cache, and Cloudflare. WPP displayed with the widget.

    I attempted to turn on/off the Ajaxify option to no avail. Using code instead of the widget gives the same issue. And flushing caches don’t do anything.

    Another thing is that if I change the “Show up to: 8 posts” to for example “7”, it updates itself, but if I return to 8, again shows the old previous stuck count. And then 7 will begin to be stuck too…

    What else can I try?
    thanks.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Hector Cabrera

    (@hcabrera)

    Hi @paulg2555,

    Yep, all that definitely sounds like a caching issue. Please answer the following questions:

    • How often does W3TC regenerates its cache? (Performance > Advanced > Garbage collection interval)
    • Is WPP’s built-in data caching feature enabled? If so, how often is it set to expire?

    Also, since you’re using a caching plugin, you’ll want to keep the Ajaxify widget option enabled (and make sure to flush W3TC’s cache at least once so it picks up this change).

    Thread Starter paulg2555

    (@paulg2555)

    In W3 pagecache, the Garbage collection interval: 3600 seconds
    WPP: Refreshes cache every: 56 minutes

    Ajaxify is on

    and it displays the most viewed count from 14 days ago.

    • This reply was modified 6 years, 4 months ago by paulg2555.
    Plugin Author Hector Cabrera

    (@hcabrera)

    Ok, did you clear W3TC’s cache after enabling the Ajaxify widget feature? And how do you know that the most viewed list is exactly 14 days old?

    Thread Starter paulg2555

    (@paulg2555)

    Yes, I cleared cache several times.

    I know is exactly 14 days old (day up or down), because the front end is stuck and displaying the most popular post from that day ( I have a 24hour most popular count).

    I also forgot to mention I am using a plugin called “Tabber Tabs Widget”, and I placed 3 times the WPP widget inside. To display 24hour 7day and All time.

    Plugin Author Hector Cabrera

    (@hcabrera)

    Could you please share your site’s URL so I can have a look?

    Thread Starter paulg2555

    (@paulg2555)

    its NSFW site, can i send u DM?

    The last thing I noticed is that when I disable WPP “Data Caching” it works normally as intended. (but my server load spikes considerably).

    But when I enable that option back it displays again a very old version in the front end.

    Plugin Author Hector Cabrera

    (@hcabrera)

    (…) when I disable WPP “Data Caching” it works normally as intended.

    WPP: Refreshes cache every: 56 minutes

    When Data Caching is enabled, the plugin will cache the popular posts list for a fixed amount of time (56 minutes, in your case). During that time, the popular posts list won’t be updated. Instead, WPP will use the cached data to display your popular posts to reduce the load on your database server and in consequence the list displayed on your homepage will likely be different from what’s shown on WPP’s Stats page. Once the Data Cache expires, WPP will query your database again, refresh the list, and cache the new data for another 56 minutes.

    Of course, if you disable the Data Cache feature WPP will query your database in real-time and thus both the popular posts lists from the front-end and the ones displayed on the Stats section will be exactly the same.

    its NSFW site, can i send u DM?

    We don’t have DMs on this site. If you don’t want to post your site’s URL here, feel free to get in touch with me using my contact form.

    Plugin Author Hector Cabrera

    (@hcabrera)

    Marking as resolved due to inactivity.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Cache problem? front end not updating’ is closed to new replies.