Gracefully handle conflicting version of PHP-CSS-Parser being loaded #1743
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Via https://wordpress.org/support/topic/500-error-on-post-pages-without-yoast-glue-plugin/
When another plugin/theme is installed which also has a copy of PHP-CSS-Parser, if its Composer autoloader wins then the required methods and functionality of our fork will not be available. In this case, all of the CSS processing will not be available, including tree shaking.
So this PR detects for a conflicting version being installed, and it will show a warning:
Additionally, feature detection is now done with fallbacks to the methods that are available.
When the required PHP-CSS-Parser is not available, then the
style[amp-custom]
manifest comment will indicate this with a warning:Classic mode in particular should work acceptably when the required version of PHP-CSS-Parser is not available.