• Resolved vickyweb

    (@vickyweb)


    When we post a new vacancy or insight post (both are custom post types), they do not appear on the vacancy or insight archive pages, without first manually purging the cache in W3 total cache.

    I have seen a few similar support posts but all dated a year or more ago, and have all been marked as resolved following a plugin update.

    In my case, I didn’t have a problem until I updated to the latest 2 versions of the plugin. I am currently using Version 2.1.2 and I had same issue with 2.1.1. I think 2.1.0 was fine.

    Please can you advise a fix?

    I know that I can tell the plugin never to cache the vacancy and insight archive pages as a short term solution, but I wanted to know if there is a better fix/a problem with the plugin?

    thanks

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

    (@vmarko)

    Hello @vickyweb

    Thank you for your inquiry.
    You can add the URL of the custom post in Performance>Page Cache>Purge Policy and Specify additional pages to purge. Including parent page in path. Ex: parent/posts.
    Thanks!

    Thread Starter vickyweb

    (@vickyweb)

    Hi Marko

    Thanks for you fast reply.

    Please can you clarify how I would enter my archive/post urls into this ‘additional pages’ section? I am unclear what is meant by the Ex: parent/posts.

    Would I only need to put the archive url here or would I need to cover wildcard paths for the individual posts under the parent path as well?

    eg, would I just put:
    /insights (to cover the insights archive page)

    or would I also need to put the individual post paths with * so that I include all the individual posts as well?
    /insight/*
    (to cover /insight/post1, /insight/post2 etc…)

    Also, is this a recent change in the plugin? if not I don’t understand why this has only recently started happening for us.

    Thanks

    Thread Starter vickyweb

    (@vickyweb)

    Hi Marko

    This ticket is not quite resolved.

    Please can you clarify how I would enter my archive/post urls into this ‘additional pages’ section? I am unclear what is meant by the Ex: parent/posts.

    Would I only need to put the archive url here or would I need to cover wildcard paths for the individual posts under the parent path as well?

    eg, would I just put:
    /insights (to cover the insights archive page)

    or would I also need to put the individual post paths with * so that I include all the individual posts as well?
    /insight/*
    (to cover /insight/post1, /insight/post2 etc…)

    Also, is this a recent change in the plugin? if not I don’t understand why this has only recently started happening for us.

    thank you

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vickyweb

    Thanks for the info.
    Nothing has been changed in W3 total cash when it comes to this.
    SO no update of the plugin could cause this. We are investigating this at the moment and I’ll get back to you as soon as i have more info.
    Thanks!

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vickyweb

    Thank you for your patience.
    Can you please confirm if you are using the Disk: Enhanced Caching method?
    What you can try is to add:
    /category/page
    to Performance>Page Cache>Purge Policy>Aditional Pages:
    Thanks!

    Thread Starter vickyweb

    (@vickyweb)

    Hi Marko

    All I know is that when we were using 2.1.0 or older, the vacancy and insight custom post types were auto clearing after creation. But since updating to 2.1.1 and 2.1.2 they do not auto clear cache after creation. The only other thing that has changed is the server the site is on but I don’t see how that can effect this.

    I am not sure where the disc enhanced method option is. I have gone to general settings > miscellaneous and there is something called ‘Optimize disk enhanced page and minify disk caching for NFS’ but that is unticked.

    I am happy to try the page cache > purge policy > additional pages suggestion, but I need you to clarify the exact page path to put in there please.

    /category/page suggests I would have to list out every single insight post, which will change when I add new ones.
    Please can you confirm using my insights file path as an example?

    /insights is my insights archive page
    /insight/post1, /insight/post2 etc are my individual insight post paths…

    so would I just need to put:
    /insights and /insight ???

    thanks

    Thread Starter vickyweb

    (@vickyweb)

    Hi Marko

    To double check the server change side of things, I have just done a test new custom post type on the old server version of the site, which using plugin 2.1.1 and that also forced me to clear the cache before seeing the new post.
    I can’t find a copy of 2.1.0 to double check that, but we don’t remember it doing this before 2.1.1.

    But if that is just how it is now, that’s fine, I just wanted to understand why I now need this page policy thing when I didn’t before.

    If you can clarify exactly what I need to put in the page purge policy bit, that would be great.

    Thanks

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vickyweb

    Thank you for the information.
    The Page Caching method can be found in Performance>General settings> Page Caching. Simply check what is selected under Page Cache Method: (Disk: Enhanced or Disk: Basic)
    Can you please share the example of the custom type post (The URL)
    Thanks!

    Thread Starter vickyweb

    (@vickyweb)

    Hi Marko

    Ok I found it, it says ‘Disc Enhanced’.

    Post type urls are..

    Archive: mywebsite.com/vacancies/
    1 vacancy example: mywebsite.com/job/contract-attorney/

    and

    Archive: mywebsite.com/insights/
    1 insight example: mywebsite.com/insight/what-are-the-next-steps

    mywebsite.com is not the actual website url.

    Thanks

    • This reply was modified 3 years, 7 months ago by vickyweb.
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vickyweb

    Thank you for the info.
    Before adding these, try enabling the following in Performance>Page Cache>Purge Policy:
    Post comments feed
    Post author feed
    Post terms feeds
    Daily archive pages
    Monthly archive pages
    Yearly archive pages
    Save all settings and purge the cache and see if the custom post types are cleared upon publishing.
    Thanks!

    Thread Starter vickyweb

    (@vickyweb)

    Hi Marko

    Thanks for this.
    I have enabled those options and clicked the ‘save settings and purge caches’ button. Tried to post new vacancy but it still doesn’t show on the archive page until I manually cleared cache.

    I tried refreshing it a few times and force refreshed my browser, but still didn’t show it until I manually cleared the cache.

    tried in 2.1.1 and 2.1.2

    Thanks

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vickyweb

    Thank you for the info.
    Try adding the /insight/what-are-the-next-steps to Performance>Page Cache>Purge Policy>Aditional Pages:
    Then try editing that page and see if the cache is cleared.
    Thanks!

    Thread Starter vickyweb

    (@vickyweb)

    Hi MArko

    Surely that will only fix that individual insight post?

    For now I have added
    /vacancies/
    /insights/
    to the additional pages purge policy and it seems to be working.

    On a side note, is it possible to allow non admin user roles to purge cache please? and if so where do I select that option?

    thanks

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vickyweb

    Thank you for the info.
    Yes, I asked you to this for testing purposes.
    If it works with
    /vacancies/
    /insights/
    You should keep it like this.
    As for your question about non-admin roles, this is not something that is controlled by W3TC. So you need to change the permissions for the user roles manually or with some plugin.
    Unfortunately, I haven’t had any experience with this.
    Thanks!

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Custom post types are still cached after publishing’ is closed to new replies.