Hello Fabio,
First, I want to thank you for your interest and message, they are clear concise and easy for me to work with. Not that its always possible for me to help, but I try.
Now – to this question. W3TC.
First, you are correct, no invalidation happens.
I have only added one Caching plugin support (Super cache) and there I wrote the invalidation my self.
Following your post I have found w3tc_pgcache_flush_post($post_id); and have added the code for doing the invalidation to the codebase (should be in the git soon).
If you wish to test this, let me know, as I don’t have a good testing env for this.
However, just one note, the extra translation requests will happen, but as translations are cached, the translation servers won’t be bugged again.
Hi, thank you for your words, you are very kind.
I would be really happy to be able to help you and test these changes, just let me know how I should do it.
I look forward to your reply.
I hope for your help and as always i thank you for your courtesy and professionalism, thank you very much.
Hi Fabio,
I have added the code you requested, and sent it to you for testing, when you verify that it does the trick for you, I will be happy to add it to the coming release.
Thanks for all your inputs.
Hi,
I replaced the old file with the new and updated one, everything seems to work fine.
Can you tell me how i can check if the invalidation with W3TC – W3 Total Cache works correctly with this new file update ?
Thanks in advance for the support.
Hi,
That is indeed a great question, I know that invalidation is called, but since I don’t have a site using W3TC, nor am I familiar with how exactly to test it, I didn’t fully test it.
The main method for testing will be: load a page that is cached, make any translation happen for that page (either manual or automatic), check that the page now loaded is newer. That should be about it
