FIX Do not publish dataobject in requireDefaultRecords() #1162
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.
Issue #1130
As far as I can tell there's absolutely no reason to publish the Page/DataObject at this point. I think the intention was originally to ensure that any owned ElementalAreas would be published ... however they'll just get published when you publish the page/dataobject
I even tested the following succesfully:
There are no network or console warnings when doing this, database records have the correct IDs etc