• Resolved T4ng

    (@schwipps)


    My websites is translated in multiple languages, through WPML.

    Let’s say our website is website.com. The domain is the native languages, while alternative are on subfolders. So that the alternative homepages are:

    website.com/es/
    website.com/fr/
    website.com/de/

    I just noticed that, after modifications, “Purge current page”, for all of those home pages, native language and translations, wouldn’t clear the page cache, so that modifications won’t be publicly available until the page is purge by expiry, OR by purging the whole website.

    It’s not the case for other pages, whose changes apply right after a “Purge Current Page”.

    Is that a normal behavior?
    How can I clear that page without clearing the whole website?

    Thanks

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

    (@vmarko)

    Hello @schwipps

    Thank you for reaching out and I am happy to help!
    If the same content is accessed from different domains you can try enabling Cache alias hostnames: in Performance>Page Cache>Aliases, and add the websites:

    website.com/es/
    website.com/fr/
    website.com/de/

    Please note that you will need to sae all settings and purge the cache in order for changes to take effect.

    Let me know if this helps!

    Thanks!

    Thread Starter T4ng

    (@schwipps)

    Hi,

    Very sorry for the belayed reply.

    No, these pages aren’t accessed from different domains, so I don’t think this setting would change anything. Is it?

    Is this the expected behavior? I mean, that’s a very common setup for translated website, to have alternative languages under subforlders. So is it normal not being able to clear their home page cache?

    Thanks

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @schwipps

    Thank you for your feedback.
    Just to confirm, have you tried enabling this and adding subdomains and see if the cache is purged for all translated pages?

    Thanks!

    Thread Starter T4ng

    (@schwipps)

    Hi,

    No I didn’t, for 2 reasons:

    • The tip of the option doesn’t seem to relate to the issue I’m facing :
      “Specify full home URLs of your mirrors so that plugin will flush it’s cache when content is changed.”
      For example:
      http://my-site.com
      http://www.my-site.com
      https://my-site.com
    • You said “If the same content is accessed from different domains”, and I’m not falling into that case – All my pages are accessed from the same domain.

    But since you insist for me to test, I just added the WPML homepage alternatives (one per line, full URLs), like this:

    https://mysite/fr/
    https://mysite/de/
    https://mysite/es/
    […]

    I did not tick the “Cache alias hostnames:” tickbox.

    Then I purged all caches, and tried reloading.

    Unfortunately, it did not help: I still cannot purge these pages individually.

    Thread Starter T4ng

    (@schwipps)

    Hi,

    I’ve been working on these pages today. Surprizingly, today I was able to clear the page cache for there homepages, multiple times. It worked consistantly.

    I was surprized, because I’m quite sure of the clearing I processed yesterday, right after adding the setting you asked for.

    • I cleared all W3TC caches, from the W3TC admin > Top Right Save Settings button > bottom arrow > Clear caches button
    • My browser cache (another browser, on which I’m not connect as admin, of course)
    • and CloudFront as well…

    But today, it just worked, like a charm.

    I must admit though, that I had a doubt about the actual clearing from the first step I mention (Top Right Save settings > bottom arrow > Clear caches butoon, where I did get a proper page reload…

    Anyway… I’ll stick with these settings and hope it keeps working in the long run. I’ll keep you posted if something comes up.

    Thanks a lot for your help here.

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

The topic ‘Can’t purge page cache from WPML Alternative homepages’ is closed to new replies.