• Resolved alexandref85

    (@alexandref85)


    Hello

    I have a WordPress site that has been translated into several languages for years using Translatepress.

    A few years ago, I used WProcket, which was very compatible. For performance reasons, I switched to Cache Enabler. The latter was more efficient, but when a new article was published, only the cache for the native language was updated, not the cache for the translated languages. I had to purge the cache manually every day (not ideal).

    A few days ago, I switched to Cloudflare APO instead of Cache Enabler. It works well, but again there is the same incompatibility with Translatepress. When I publish a new article, the native language cache is updated but not the translated language cache, which I still have to purge manually.

    I obviously contacted Translatepress, who recommended that I switch to LiteSpeed Cache.

    I want to stay with Cloudflare APO (I have a subscription), but I can’t figure out who should make the effort to be compatible with the other: TranslatePress or Cloudflare APO.

    In short, does anyone have any ideas or solutions to offer? A script, hook, or something else I can use so that when I publish an article, it also updates the cache in the other languages?

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Remkus de Vries

    (@defries)

    Hi @alexandref85,

    The caching behavior of Cloudflare APO, which the Cloudflare plugin here facilitates, is pretty straightforward. It simply caches content that WordPress generates and purges whenn that content is updated. TranslatePress by @cozmoslabs deviates from this standard, so the onus is on them to make sure their implementation of translated (default WordPress) content is respected.

    Telling you to move to LiteSpeed Cache is IMHO not the right answer. They can easily hook into our cache release functionality to refresh whatever and whenever. There’s tons of plugins out there that do the same.

    Or you build a helper plugin that does that. That’s your other option.

    Thread Starter alexandref85

    (@alexandref85)

    Hello,

    There is a good reason why I switched from Wprocket to Cache Enabler and then Cloudflare APO over the last few years.

    Obviously, TranslatePress told me to sort it out with Cloudflare, and Cloudflare told me to sort it out with TranslatePress. It reminds me of my years in a web marketing agency when the client was stuck between two service providers.

    In short, I am developing a plugin that purges the Cloudflare cache of pages linked to the article published in all languages (home, category, tags). I think this will solve my problem.

    Have a nice day.

    Plugin Contributor Remkus de Vries

    (@defries)

    I hear ya. It’s a shame TranslatePress isn’t picking this up because it’s clearly them deviating from the norm (that is standard WordPress content and its caching behavior).

    Good to see you’r taking matters into your own hands, though!

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

You must be logged in to reply to this topic.