Skip to content

Require being in Recovery Mode for extensions to be paused. - #38

Closed
TimothyBJacobs wants to merge 1 commit into
WordPress:masterfrom
TimothyBJacobs:46130
Closed

Require being in Recovery Mode for extensions to be paused.#38
TimothyBJacobs wants to merge 1 commit into
WordPress:masterfrom
TimothyBJacobs:46130

Conversation

@TimothyBJacobs

@TimothyBJacobs TimothyBJacobs commented Jan 29, 2019

Copy link
Copy Markdown
Member

@ocean90

ocean90 commented Mar 8, 2020

Copy link
Copy Markdown
Member

Closing as the ticket was fixed a few months ago.

@ocean90 ocean90 closed this Mar 8, 2020
enricocarraro added a commit to enricocarraro/wordpress-develop that referenced this pull request Oct 7, 2020
enricocarraro added a commit to enricocarraro/wordpress-develop that referenced this pull request Oct 15, 2020
ironprogrammer referenced this pull request in ironprogrammer/wordpress-develop Feb 4, 2022
Allows semi-colons in URLs, typically indicative of an HTML entity, such as `&` or `&`.
westonruter pushed a commit to westonruter/wordpress-develop that referenced this pull request Apr 27, 2023
Script Loading Strategy - ML2 WordPress#14 - Update `do_item` method.
HasnainAshfaq added a commit to HasnainAshfaq/wordpress-develop that referenced this pull request Jul 26, 2026
…e when content contains <

When a no-texturize tag (script, pre, code, etc.) contains a raw '<' character
— as in JavaScript like `if(a<b)` — wp_html_split() misidentifies the content
after that '<' as an HTML element delimiter. Previously, the texturize loop
would encode '&' characters in that false delimiter (e.g. '&&' became
'&WordPress#38;&WordPress#38;'), corrupting script content.

Fix: only run the '&' → '&WordPress#38;' substitution when we are not already inside a
no-texturize tag stack. Real HTML tag attributes (e.g. <a href="foo&bar">) are
only encountered at the top level, so the fix does not affect them.

This became more user-visible in WordPress 7.0, which introduced a dedicated
JavaScript panel in the Custom HTML block where users enter code that can
contain '<' comparisons.

Fixes #43785.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants