featureDefinition with featureSetting and featureSecurity

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
5/30/2013 7:18:06 AM
Gravatar
Total Posts 75

featureDefinition with featureSetting and featureSecurity

This is regard to this old thread: https://www.mojoportal.com/Forums/Thread.aspx?pageid=5&t=8523~1

The idea has came up again and I think I wasn't very clear in what I was looking to do.  I hope to clarify in this thread.  So for a any Feature Instance there are two different categories in security, roles that can view content and roles who can edit content.  Could it be possible to add to those categories?  For example, "Roles that can Approve Requests" or "Roles that can Moderate".  These security settings could be setup under the featureDefinition as a featureSecurity or something like that.  It would then be up to the custom module to use those new security settings just like featureSettings.  What do you think?

5/30/2013 7:56:28 AM
Gravatar
Total Posts 18439

Re: featureDefinition with featureSetting and featureSecurity

There exists an ISettingControl that you can use for scenarios like that. For example in the next update to Form Wizard Pro we wanted to add a way to allow users who don't have edit rights to be able to review but not delete the form submissions. So we added a setting for the allowed roles:

<featureSetting
            resourceFile="FormWizardResources"
            grouNameKey="Permissions"
            resourceKey="RolesThatCanViewSubmissions"
            defaultValue=""
            controlType="ISettingControl"
           controlSrc="~/Controls/AllowedRolesSetting.ascx"
            helpKey="sts-FormWizard-RolesThatCanViewSubmissions-help"
             sortOrder="30000"
            regexValidationExpression=""
            />

The control AllowedRolesSetting.ascx is part of mojoPortal and you can use it in your own custom features, and of course it is up to you what to implement with that data to protect your feature. The control just allows you to store the allowed roles as a module setting, it is up to you to implement use of it.

Hope that helps,

Joe

5/30/2013 8:08:42 AM
Gravatar
Total Posts 75

Re: featureDefinition with featureSetting and featureSecurity

That is what I was looking for. I am sorry for the duplicate thread.  I didn't realize you had already talked about this solution.  Thank you for your help!

You must sign in to post in the forums. This thread is closed to new posts.