There should be a way to set permissions for non-creatable types too


It makes sense to set type-level permissions even if a type is not creatable. So IMO even non-creatable types should be listed on pages of roles and there shouldn't be a check in Orchard.Core.Contents.Security.AuthorizationEventHandler ln 28.


jao28 wrote Feb 12 at 11:59 PM

This is similar to https://orchard.codeplex.com/workitem/19905 where I have a "hack" solution - be great to have it resolved (and I think this one is proposing a better solution, even though it will provide a lot more permissions to manage).

Piedone wrote Jun 10 at 11:48 PM

Piedone wrote Jul 2 at 1:54 PM

mjy78 wrote Fri at 1:17 AM

I just added quite a lengthy comment to work item 19905 discussing this which I probably should have added here. Please take a look and let me know your thoughts.


mjy78 wrote Mon at 2:31 PM

The following fork contains a a fix for this. It adds a "Permissions Enabled" option to the content type settings.