Initialize the Autosaves controller, even if revisions are disabled #8682
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
danielbachhuber
added
[Type] Bug
4 tasks
danielbachhuber
approved these changes
Aug 7, 2018
Member
|
Worth noting: I tested this independently in #8692 |
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.
Description
Fixes #8536
Fixes #7442
Fixes #7348
Revisions are not required to support autosaves - see https://codex.wordpress.org/Revisions#Revision_Options
How has this been tested?
I verified the endpoint shows up even with revisions disabled for a post type.
Types of changes
Removed the check for revision post type support when loading the autosaves controller.
Checklist: