Linking supporting pages in a custom feature

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.
7/15/2009 10:18:45 AM
Gravatar
Total Posts 8

Linking supporting pages in a custom feature

I have an online class I'm developing in mojoPortal. The classes consist of static content.  I have created a new feature and plugged into the framework.  My question is regarding the linking of pages and the preferred mechanism for doing so. 

What is the preferred method of linking to supporting page 1, then 2 and so on?  Just develop multiple aspx pages and use the links feature?

Thanks,

Evan

7/15/2009 10:27:05 AM
Gravatar
Total Posts 18439

Re: Linking supporting pages in a custom feature

Hi Evan,

I recommend you look at the source code for existing features that have supporting pages like the blog and forums or WebStore.

Basically they all work the same way, the supporting pages inherit from mojoBasePage which makes them visually integrated, you build the links to the pages internally from your feature module and you must pass in the pageid and your moduleid and any other params you may need. Passing in the pageid and moduleid allow you to use some functionality in the base page to check permissions and enforce security and it will also ensure that the menu stays highlighted on the correct page. 

The ModuleTitleControl if used in your module can help create a heading that is styled like other features and it can link to an edit page by you telling it the relative url ~/pathtoyoureditpage.aspx,it will automatically pass the module id and page id.

The code in existing features is pretty easy to read and understand so I recommend studying exisiting code for examples of lots of things you would commonly need to do.

Hope it helps,

Joe

7/15/2009 10:29:50 AM
Gravatar
Total Posts 8

Re: Linking supporting pages in a custom feature

Thanks Joe.  I really appreciate the quick response.

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