Add PostValidateBlueprint as ContentController action #15560
Replies: 3 comments
-
We don't plan to add new features for v8. I think the best you can do for now is to make your own validation attribute, that potentially uses reflection to execute the logic from Umbraco. |
Beta Was this translation helpful? Give feedback.
-
It's not only the ContentSaveValidationAttribute that is internal. Its also ContentSaveModelValidator, ContentModelValidator, BlueprintItemBinder, ContentItemBinder and ContentModelBinderHelper. Then you would also need some of the logic from the ContentController methods like SetupBlueprint, EnsureUniqueName, PostSaveBlueprint, PostSaveInternal, SaveAndNotify, AddVariantValidationError, GetVariantName, HandleInvalidModelState, MapValuesForPersistence, MapToDisplay and ofcause some of the logic from the abstract ContentControllerBase that the ContentController inherit from. |
Beta Was this translation helpful? Give feedback.
-
This has been addressed by ##15638 so I'll go ahead and close this discussion |
Beta Was this translation helpful? Give feedback.
-
Since the security update of Umbraco 8.18.12 it is no longer possible to access the PostSaveBlueprint without the user having access to the "Settings" section.
Although this is understandable, it has a negative effect on the commonly used DocTypeGrid editor. This uses PostSaveBlueprint to validate content.
It would be nice if an extra endpoint (for example PostValidateBlueprint) was added to the ContentController so that a blueprint is validated, possibly with validation whether the user has access to either the content section or the settings section.
See also ##15460 (comment)
Beta Was this translation helpful? Give feedback.
All reactions