@android1pro What version of the plugin are you using?
Also, the deprecation warning may indicate your server has an old version of the ICU library which needs to be updated. See https://github.com/ampproject/amp-wp/pull/1440
Then I believe the issue is you need to update the ICU lib that the intl PHP extension is using.
I am running PHP 7.2 without issue, and we’re running unit tests through PHP 7.2 as well on Travis CI.
Thread Starter
droid
(@android1pro)
May be not as again it could be AMP plugin issue,
since Google console indicate many amp specific errors here are some of those errors texts:
1) Only amp-boilerplate and amp-custom ‘style’ tags are allowed, and only in the document head.
2) Tag found outside the document head which is only allowed as a direct child of the document head.
Please share the URL to the AMP page having the issue.
Thread Starter
droid
(@android1pro)
Unfortunately it is not practical to share over 100 URL with those same errors,not to mention security issues that are obvious when sharing on public forum here.
However will be more than happy to send to secure email to help you out because many has those errors as communicated by colleagues that do
Only sharing one URL is sufficient. When starting this support topic there should have been the URL for your site supplied. Other support topics link to the sites relate to. So it’s not a security issue.
Thread Starter
droid
(@android1pro)
Thread Starter
droid
(@android1pro)
1) In Google console under the the title error
“AMP Only amp-boilerplate and amp-custom ‘style’ tags are allowed, and only in the document head.”
…
2) Under error titled “AMP Custom JavaScript is not allowed.”
…
I just pasted all of the URLs into https://validator.amp.dev/ and there were no validation errors reported for any of them. So apparently the issue is no longer occurring.
3)In Google console under the the title error
“AMP URL marked ‘noindex’”
I don’t see any noindex on those URLs.
Thread Starter
droid
(@android1pro)
Thank you for the prompt good precise support!
2 vital follow up:
1) Are you diagnosing from this that Google Console is not accurate in its reporting regarding above 3 errors and therefore at fault here?
If not then what is your best accurate solution in this case?
2) The error log keep reporting the following error still today
“Deprecated: idn_to_utf8(): INTL_IDNA_VARIANT_2003 is deprecated in /home/wp-content/plugins/amp/includes/class-amp-http.php on line 233”
Hosting assured me yesterday that the ICU lib that the intl PHP extension is using, is already updated.so what is the best solution in this case?
Can you manage to accurately correctly fix the above 2 vital issues?
Again,
Thank you for your confirmation as soon as accurately correctly completed today.
Keep up the good work!
Regarding 1) you’d need to find out whether that was an error that was diagnosed in the past and is still shown although already resolved, or whether it is still an active issue.
Regarding 2) I just verified the code. If you’re using the latest version of the AMP plugin, then it should only show the above warning if the ICU within the ‘intl’ extension is not up-to-date.
You can verify the version of the ICU yourself in the output that you get from phpinfo(). For example, if you have access to the server’s shell, you can use the following to see the version:
php -r "phpinfo();" | grep ICU
On my system right now, this is what I get:
ICU version => 64.2
ICU Data version => 64.2
ICU TZData version => 2019a
ICU Unicode version => 12.1
