-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert to tab not working when Group is called 'Content' #11202
Comments
Ah thanks @prjseal for the repro! I had the same problem last week but could not figure out how to reproduce it. I believe this is also a problem for v8, so we'll need to fix both. 👍 |
The composition can't be saved with a You currently have to rename all the generic groups in the document types to something else first (or move the local properties added to the composition group somewhere else), convert the composition group into a tab and then move the local properties back to the composition tab. I hope this makes sense 😇 We already do all the validation and return the invalid property group aliases in the Umbraco-CMS/src/Umbraco.Core/Services/Implement/ContentTypeServiceBaseOfTRepositoryTItemTService.cs Lines 41 to 56 in 4c9d773
Because the validation fails, you do get the save error/cross, but no further feedback why that's the case. This is definitely something we can improve! Not directly related, but something we should also fix is the TODO comment in the Umbraco-CMS/src/Umbraco.Core/Exceptions/InvalidCompositionException.cs Lines 86 to 100 in 4c9d773
|
@ronaldbarendse Thanks for describing the workaround. It would be good if this actually gets fixed though. You should be able to detect the difference between a tab and a group and they should be able to have the same name in my opinion. |
@prjseal We should make sure a helpful validation message is shown when the save fails because of an invalid property group in the compositions (similar to the property type aliases). Fixing it will still require manual steps, because you need to update/save multiple document types (and possibly other compositions as well). Please also note that this is only an issue when multiple compositions bring the same group/tab into a document type or if you have added properties to a group that's inherited from a composition: in that case a 'local' group is added to the document type to contain this property. This is done to ensure the property (and group) isn't deleted if you remove the composition. This is also the reason why you can't reorder/convert to tab on inherited tabs/groups. |
Fixed for 8.18.0 / 9.1.0 in #11373 |
I've got the same issue in 8.18.4 when the section is named 'Generic properties'.
|
Are there any another restricted names? I am not able to convert to tab Settings or Images groups to tab... Getting same error like when trying to convert Content to tab:
|
Which exact Umbraco version are you using? For example: 8.13.1 - don't just write v8
v9 RC 4
Bug summary
In the Content Base composition, when I try to convert the group called 'Content' to a tab and press save I get a 400 error in the console. It does work for other groups not called 'Content'
Specifics
Request Url: https://localhost:44358/umbraco/backoffice/umbracoapi/contenttype/PostSave
Request Method: POST
Status Code: 400
Steps to reproduce
Install the default starter kit using these unattended install commands
Expected result / actual result
I expected to be able to convert my group called Content to a tab called Content.
This item has been added to our backlog AB#14159
The text was updated successfully, but these errors were encountered: