Trac: Changes required for the new WordPress.org header #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n DomDocument to migrate the HTML5 -> XHTML required by Trac
6 tasks
|
|
12 tasks
|
Turned out that the jQuery issues were caused by the WordPress.org headers loading jQuery 3.x, but Trac using (and bundling) jQuery 1.x. I've updated the script to exclude the jQuery |
This was referenced Jan 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a PR for migrating Trac to the new WordPress.org headers. See WordPress/wporg-mu-plugins#53
Invalid HTML from the header is fixed. Search menu item is invalid HTML wporg-mu-plugins#87There are several load-order issues on the Trac side still, resulting in JS errorsjQuery is not loaded for the Header, instead relying upon the jQuery 1.x loaded by Trac.