Hello @filoumouton
You may be using reader mode/classic mode when you have an old AMP plugin
Are you using transitional mode now?
nevertheless, we are working on adding a custom URL structure that will be available sooner and is currently in the testing phase. once it is released you will be able to choose between ?amp=1 /amp/
Feel free to download the prod build zip file and give it a try
https://github.com/ampproject/amp-wp/pull/5558#issuecomment-725867606
Once downloaded and activated you will find the new section in the AMP setting called Paired URL Structure where you get to choose between ?amp and /amp/`
Let us know if you run into issues.
I did not update my version because I ran into the issue “Cannot read property ‘i18n’ of undefined” when accessing the settings of AMp plugin.
(i have the same problem with the version you gave in the comment)
if you have a fix for this it would be apreciated too 🙂
So I stayed to 0.7.2 that worked well.
—
Anyway, is there a “simple” solution to set the URL to /amp/ and not ?amp ? (without changing version? ==> I ask ths because it was the case previously)
Hello @filoumouton
I did not update my version because I ran into the issue “Cannot read property ‘i18n’ of undefined” when accessing the settings of AMp plugin
It’s not an issue with the AMP plugin your theme or plugin may have conflicts, in order to determine which plugins conflicts we asked you site health information so we can provide a fix or determine the culprit plugin
Feel free to submit the site info using this form.
Anyway, is there a “simple” solution to set the URL to /amp/ and not ?amp ? (without changing version? ==> I ask ths because it was the case previously)
The only way to do that without changing version is to switch to legacy Reader mode.
In regards to the Cannot read property ‘i18n’ of undefined error, can you share the full error in the browser’s console? It would be helpful to see which JS file specifically is causing the problem. The issue may be that we need to fix how we’re polyfilling wp-i18n.
The issue may also be resolved by updating WordPress to the latest version, if you haven’t done so already.
As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.
