Repository navigation
Fix formatting issues from WordPress' Classic Editor - #81
Merged
Merged
Conversation
This file contains hidden or 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
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 pull request attempts to fix text formatting issues for conent imported from WordPress' Classic Editor.
It doesn't seem like the Classic Editor saves
<p>tags when a post's content are saved in the database. Here's an example:However, when content is displayed on the frontend, it gets passed through WordPress'
wpautopfunction which essentially runs the content through various regexes before outputting HTML to the browser.However, since the content doesn't get passed through
wpautopduring an export, we end up with the unnormalized "string" which breaks TipTap (the library behind Bard).In order to workaround this, we've added a config option which'll run your content through
wpautopbefore transforming it into the right format for Bard.Fixes #62.
Replaces #65.