robertosanchezwp

hello @westonruter yes, a /u0026 when the HTML is printed ends up as & but the amp-analytics module i think it′s before that and i need the same codificaction on amp and noamp pages, so the JSON remains the same way.

with add_filter( 'amp_enable_optimizer', '__return_false' ) the problem dissapears but i think I’m deactivating some good features too…

sorry, server issue, not plugin related.

Thank you

I can’t share a URL since my problem occurs on a preproduction site. I can give you another example, this one on amp-analytics module, inside <script type='application/json'>:

this is a json that i need to print, but between cp1 and cp2, must be an ampersand and shows de unicode character instead. In noamp mode, it shows the & normally

{"requests":{"custom_params":"cp1=test\u0026cp2=test"},"vars":{"env":"-preproduction"},"triggers":{"trackConsent":{"on":"visible","request":"impression"}}}

@westonruter thanks a lot, I tested the pre-release build and now works perfectly.

Thank you again and I will gratefully wait for the next stable release

Hi again, the UUID is ampwp-5991a725-b446-5d7f-8ce0-03e71d300b44

if it helps, I tried to install the v2.2 version on a fresh new single site in the same server and does it work. I think may be it’s related to the multisite instances due the sources and routes may defer from the single site instances.

Thanks again for your help.

Hello again!

Thanks a lot for the quick reply.

Is there any info about the release date of the new version of the plugin?(free and PRO)

And do you know if version upgrade requires some aditional config to work?

Thanks a lot again.

Kind Regards