Post Types: Move back-compat registration later to avoid Gutenberg fatal #980
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
iandunn
force-pushed
the
wcposttype-backcompat-fatal
branch
from
6576b41
to
09f1e33
Compare
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.
There's a fatal error on
wp-admin/site-editor.php?wp_theme_preview=twentytwentythree&return=themes.phpbecauseWordCamp_Post_Types_Plugin_Back_Compat::__construct()callswp_get_theme()->get_stylesheet();That used to work, but nowgutenberg_get_theme_preview_path()hooks in and callswp_get_current_user(), which isn't registered at this point.Moving the registration later avoids the issue.