You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was something that was suggested in the support forums
Currently, the AMP plugin warns you when there's randomly generated content on a page. That doesn't work well with the post-processor cache.
In the case from the support forums, that randomly generated content was likely due to some HTML comments. Now the question is whether random content in HTML comments can be ignored for this purpose, e.g. by simply removing any HTML comments from the source code. That would make the cache logic more robust.
The text was updated successfully, but these errors were encountered:
A problem with stripping the comments is that we'd need to restore them after post-processing. Also, the removal would need to be suspended when doing validation because comments are how invalid markup is attributed to plugins/themes.
We may also need to consider whether the post processor is just not robust enough of an idea to be feasible and if it should be yanked. Better to have someone rely on a page cache.
This was something that was suggested in the support forums
Currently, the AMP plugin warns you when there's randomly generated content on a page. That doesn't work well with the post-processor cache.
In the case from the support forums, that randomly generated content was likely due to some HTML comments. Now the question is whether random content in HTML comments can be ignored for this purpose, e.g. by simply removing any HTML comments from the source code. That would make the cache logic more robust.
The text was updated successfully, but these errors were encountered: