when propagating an element, cross-site validate if we’re changing the status to enabled #16533
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
When propagating an element to a site, we only run cross-site validation on the changed custom fields (#13675). However, when the site status changes to enabled, we should make an exception and cross-site validate everything.
Related issues
#16505
steps to reproduce:
siteA
, create a new entry in that section, fill out only the title and fully savesiteA
& fully savesiteA
again, togglesiteB
to be enabled and fully savesiteB
now despite not having the plain text field filled outsiteB