Viewing 15 replies - 1 through 15 (of 25 total)
  • Hi Cristian,

    With any caching plugin, you will want to set certain pages to be excluded from the cache. These pages contain important state variables used during posting/editing of ads that will cause problems.

    They include:
    Place Ad (/place-ad)
    Edit Ad (/edit-ad)
    Payment Thank You (/payment-thank-you)

    If you renamed these pages, you can find their new names under Classifieds->Settings, Classifieds Pages tab.

    These should be excluded in your cache so the user doesn’t pick up cached values of data.

    Show Ad (/show-ad) does NOT need to be excluded unless you’re seeing issues. It should work fine in a cache.

    Thread Starter Cristian Vacca

    (@cristianvacca)

    Place ad was already never cache.
    I put in EDIT AD in never cache.

    Got It Empty all cache

    The problem is always the same …

    Hmmm. I wonder if I missed something here then.

    What specific page are you seeing old data on?

    Can you walk me through exactly how to show this problem on your site?

    Have you tried a full conflict test to see if W3TC is really the cause?

    Here is an article about how to test for theme and plugin conflicts with AWPCP, which may help pinpoint the issue: https://awpcp.com/forum/faq/how-to-test-for-plugintheme-conflicts/

    Try that and report back.

    Thread Starter Cristian Vacca

    (@cristianvacca)

    It w3 total cache is the cause. I say sure!

    If I deactivate w3 total cache, the problem goes away immediately.

    The problem is in the widgets latest published.

    Sorry if I was not clear in the explanation. I had to say before now.

    In order to resolve this, you’ll need to add AWPCP URLs to W3TC’s “excluded pages” setting.

    These pages should be excluded to make AWPCP work:
    Place Ad
    Edit Ad
    Payment Thank You
    Payment Cancel

    The URLs for these pages will depend on what you have them named, which you can find under Classifieds->Settings, Classified Pages tab.

    Does that make sense?

    Thread Starter Cristian Vacca

    (@cristianvacca)

    I found the problem.
    Dave you’re right!

    I am hosting on Siteground.
    Here we plugin SG CachePress

    I have excluded pages here.

    Now everything works fine.

    Thank you.

    Glad it works!

    Thread Starter Cristian Vacca

    (@cristianvacca)

    I still have problem.
    When user enters ad w3 total cache stores the new page created.
    I approve ad, but appears as not approved because cache
    Look screenshoot:
    https://imgur.com/a/z8GDs

    I have to empty the cache of single files manually (normal procedure w3 total cache does not work in this situation).
    How is it possible to ping to w3 total cache when I approve ad?

    Thread Starter Cristian Vacca

    (@cristianvacca)

    Just recently he returned this problem, I do not understand why.
    It ‘very important to say that AWPCP expect to share!
    In fact, if the file cache shows disapproved ad AWPCP does not share on Facebook.
    I did experiment on ad arrived three hours ago.
    I have approved and I have manually deleted the file from the cache folder.
    AWPCP not shared ad on Facebook.
    When I deleted the cache file and the display of ads is approved AWPCP shared immediately.
    Awpcp did overtime!
    In this case you can ping?

    Nothing is broken here…This is how caches work, Cristian.

    The cache is storing the older state of a page until the cache is flushed.

    The cache will update on its own after some time. AWPCP doesn’t control this.

    If you remove the Show Ad page from the cache, the site will slow down a bit, but you will see live, real-time data. By adding the cache, you trade speed for live data, and it’s faster, but you don’t get the latest state.

    We don’t have a way to ping the cache to refresh it today. We can investigate it, but it’s not an API that was previously available AND if it was, then it would be different per plugin…

    Hello, is there any guide for excluding those pages with WP Super Cache?

    This plugin has also this setting:
    – Don’t cache pages for known users.

    Maybe this is enough when checked?

    Hi John,

    No, you want to do more than that with caching plugins.

    We recommend that you don’t cache the following pages (exclude the URLs in the cache settings):
    – Place Ad
    – Payment Thank You
    – Payment Cancelled

    These pages require a fresh state each and every time, otherwise you mix data between users which is very bad. Show Ad shouldn’t be excluded, per the reasons I stated above. The others are fine, but with the limits of a cache I already mentioned.

    Thanks for this but I really can’t find where and how to exclude pages in WP Super Cache… Any idea?

    … the only relevant setting I found is about:
    strings (not a filename) that forces a page not to be cached.

    Not sure of the specific settings because my host rejects the use of caching plugins (they provide this service natively) but this support thread should help: https://www.ads-software.com/support/topic/plugin-wp-super-cache-exclude-specific-pages

    If not, try Googling “WP Super Cache Page Exclusion”…

Viewing 15 replies - 1 through 15 (of 25 total)
  • The topic ‘Awpcp setting w3 total cache’ is closed to new replies.