Interfacing With Physical Pages

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.
2/9/2012 2:41:52 PM
Gravatar
Total Posts 148

Interfacing With Physical Pages

Hi:

Is there a way to develop a physical .aspx page inside Visual Studio and use it in a mojoPortal website but still interface with it like a dynamically created page during development.  I would like to create a physical page but I would also like to be able to use the "Edit Page" mojoPortal menu so I can add controls I have installed.

2/9/2012 2:46:17 PM
Gravatar
Total Posts 2202

Re: Interfacing With Physical Pages

Hi,

I don't think there is a way to do this because in order to publish a module on a page, that page must exist in the mp_Pages table and if you're using a "physical" file for that page, it will not exist in the table.

What is your goal? Maybe there is another way to accomplish that goal besides using a "physical" page.

Thanks,
Joe D. 

2/9/2012 2:53:06 PM
Gravatar
Total Posts 148

Re: Interfacing With Physical Pages

Hi:

I would like to use the more traditional structure for my pages.  For example, when someone is on a page I would like the location to read http://mysite/mypage/default.aspx instead of http://mysite-mypage-default.aspx.  I remember reading on this site that could be accomplished with physical pages but not with dynamic ones.  Is there a work around for dynamic pages to look more traditional?

2/9/2012 3:06:42 PM
Gravatar
Total Posts 1204
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: Interfacing With Physical Pages

I see this type of question crop up periodically, but it always puzzles me why people want to mimic the "old school" HTML hierarchy within a CMS. In any case, you are talking about a pretty extreme workaround, even if you can get it functioning correctly. Honestly, if it's that important to you, it might be better to use a different CMS if you really need to see those extra "/" segments in your URLs.

More info about why these are not needed or desired in mojoPortal is in the Search Engine Optimization document.

Jamie

2/9/2012 3:11:37 PM
Gravatar
Total Posts 2202

Re: Interfacing With Physical Pages

I don't see that type of url structure as traditional but rather as antiquated. Way back in the day when I was building websites using notepad, an ftp account and a Unix server, we did things that way to we wouldn't have to use the .html at the end of our urls. www.mysite.com/about-us would bring up the index.html document that was stored in the about-us directory.

This type of url structure has long since been dropped by the majority of the web and for good reason. It doesn't provide any additional value to the user now that we have things like extensionless urls. Also, SEO isn't improved by using a "directory" structure to urls. In fact, it is very easy to get carried away with that kind of thing.

So many other CMS platform put all kinds of sillyness in their urls making the resulting link so hard to remember that we needed url shortening services to create new tiny urls that have no basis on what is actually on the page.

Anyway, I'm not sure of a solution that will help you do this and I'm not sure you would be any better off doing it.

Thanks,
Joe D. 

2/9/2012 3:17:51 PM
Gravatar
Total Posts 69

Re: Interfacing With Physical Pages

Having default.aspx as part of every url is pointless, it adds no meaning and makes an ugly url.

Why would you want an url like

www.mysite.com/mypage/default.aspx

?

Why not just use extensionless urls like

www.mysite.com/mypage

which is supported in mojoPortal and is a prettier url?

2/9/2012 3:18:30 PM
Gravatar
Total Posts 148

Re: Interfacing With Physical Pages

Hi:

I happen to agree with you.  I appreciate the reasons to use the "new" urls.  I can use your info to convince my boss.

I just thought I would ask before I spent two weeks trying only to end up at a dead end.

Thanks.

2/9/2012 3:22:25 PM
Gravatar
Total Posts 148

Re: Interfacing With Physical Pages

Hi:

So I can use www.mysite.com/mypage?  I didn't think we could use any "/" in our page definitions.

2/9/2012 3:25:59 PM
Gravatar
Total Posts 69

Re: Interfacing With Physical Pages

there is no extra segment in that url, it just has one / after the domain name

you can use

www.mysite/mypage

but you can't use

www.mysite/mypage/

2/9/2012 3:40:16 PM
Gravatar
Total Posts 2202

Re: Interfacing With Physical Pages

See the Extensionless Urls documentation for more information.

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