SiteModuleControl to be used traditional User Control

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.
11/3/2011 11:25:28 AM
Gravatar
Total Posts 14

SiteModuleControl to be used traditional User Control

We created feature by inhering from SiteModuleControl,

we wanted to put in the master page by using the traditional way that used for putting user control in the ASP.NET page, when we put it the "Edit Link" and "Settings Link" [The title control] are  not shown

 

My Question is there a way to put SiteModuleControl control without adding it as feature to the content page?

Regards

Tarek

 

11/3/2011 2:00:12 PM
Gravatar
Total Posts 18439

Re: SiteModuleControl to be used traditional User Control

There is a hacky way to do it with ModuleWrapper control. But this approach doesn't work well with many features. SiteModule is meant to be a base class for a CMS page plugin which requires publishing on a page to be able to correctly enforce page allowed roles and module allowed roles. It "may" work with your custom feature if your custom feature doesn't have supporting pages. Use it if you must, avoid it if you can.

See also

Hope that helps,

Joe

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