Prisna Google Translate Incompatibility Home

Cache Enabler does not cache POST requests.

Have you tried disabling other plugins in your WP setup and reverting to a default theme to verify if the issue is not caused by something else?

Thanks Cody. I’ve tried many troubleshooting steps including turning off various plugins.

However, why would adding the page ID to the exclusions section within Cache Enabler allow it to suddenly work?

I have Autoptimize and Cloudflare enabled. These are the only two other items I can think of aside from my htaccess that may affect Cache Enabler behavior later on.

regarding autoptimize; try to add ?ao_noptimize=1 to the URL of your homepage, this should disable AO for that request (confirm if so by cheching HTML source, should be no “autoptimize” in there) and should allow you see if this is due to AO.

hope this helps,
frank (ao dev)

Thanks Frank and Cody.

I’ve tested the above and it works so it appears to be AO caching a file so Cody is probably correct (I say probably because this is above my pay grade at this point lol.) What that file is, I don’t know and I will have to look later to see where it is going wrong. I’ll also update the plugin author with this information as well as KeyCDN as I find out more.

Open to suggestions.

Thank you both again!

OK, now Autoptimize does not cache pages (nor POST-requests), it merely optimizes CSS and JS. So what _might_ be happening (to be confirmed by the Prisna Google Translate developer) is that Prisna Google Translate uses javascript and that something goes wrong when that JS is being optimized. This can we worked around easily by excluding the relevant JS from AO optimization (see AO FAQ for more info). The Prisna Google Translate should be able to tell you what JS to exclude.

frank

Understood.
Do you think it’s more related to .js versus .css?
I see the following .js files in its javascript directory:

• admin.class.js
  common.class.js
  translator-bar.js
  translator-dropdown.js

When I have more time (may be a few days or even two weeks) I can test them by adding them to your exceptions list one-by-one.

The confusing part is that the plugin works on subsequent pages – just not the homepage. That part doesn’t make much sense to me.

The confusing part is that the plugin works on subsequent pages – just not the homepage. That part doesn’t make much sense to me.

indeed … maybe check if you get an JS error on the browser console on the HP. could be a homepage-specific JS problem blocking execution of the autoptimized JS …