Extensionless URLs issue on mojoPortal Ver.2.3.6.5

This forum is primarily for reporting issues about Web Accessibility such as difficulty using mojoPortal with a screen reader or other assistive technology.

Post any feedback here related to improving the accessibility or usability of mojoPortal. As stated in our Accessibility documentation, it is an important goal of the project that both the front-end customer experience and the back end administration and content publishing features be accessible to as many people as possible. Ideally, if you post about problems, we will also be glad to have suggestions on how the problems can be fixed but all constructive feedback on these issues is welcome.

This thread is closed to new posts. You must sign in to post in the forums.
10/3/2011 2:29:12 AM
Gravatar
Total Posts 57
Web Platform Evangelist.

Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi Joe,

I've been working with mojoPortal from its previous versions since 2.1.3.0 and i've been analysing the changes on it and also had built few custom modules to exercise the richness of the MojoPortal. I always thank you wholeheartedly for creating such an "Awesome CMS" that's damn flexible to be customized.

Here today i wanted to bring in notice about the issue that's being prevailing on its version 2.3.6.5, that is, the previous build version. Please check out the Web Deploy release or its source of this version. The user will not be able to have an automated URL redirection after having enabled with a ExtensionLess URL feature. I tested the same version many times on various servers(IIS 7.5) and found this issue. I wanted you to look at this isue and check whether this has been fixed or should it needs to be fixed in its future release that is after ver.2.3.7.0.
 

--
Regards
Guruprasad Balaji,

10/3/2011 12:42:07 PM
Gravatar
Total Posts 18444

Re: Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi Guruprasad,

When you say:

The user will not be able to have an automated URL redirection after having enabled with a ExtensionLess URL feature.

I have no idea what you mean about automated url redirection, please explain it more clearly in terms of

  • steps to produce the problem
  • expected results
  • actual results.

Best,

Joe

10/5/2011 11:47:57 AM
Gravatar
Total Posts 57
Web Platform Evangelist.

Re: Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi Joe,

Thanks for replying. The situation would be,

1. After setting up the mojoPortal (v2.3.6.5 or v2.3.7.0) the user isn't allowed to create a extensionless url that should automatically get redirected to the right extension. i.e., say you create a new page with the name "~/newpage" and have canonical url as "~/newpage.aspx" [having canonical url with .aspx, in case if the site needs to b revoked to "Mandatory Extension" in mere future, if required], the redirect should automatically be setup fro "~/newpage.aspx" to "~/newpage" or itself right?[having the right things setup on web.config as per the documentation in http://www.mojoportal.com/extensionless-urls.aspx ] Here, the situation is it isn't creating a redirect url or mapping itself on the "301 Redirect Manager", resulting in failure of opening the page when any user tries to open it with ".aspx" extension.

2. This feature was working fine until version 2.3.6.0. This is what im trying bring in this scenario and make it work again.

Hope this is clear right? Joe? can you please let me know why this had happened and is that an obsolete feature that comes bundled up with mojoPortal or ignored by mistake while building the portal or is that a bug?

10/5/2011 2:24:16 PM
Gravatar
Total Posts 18444

Re: Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi,

You should use the actual url for the canonical url, you do not want the canonical url to be an url that does a redirect. You want to avoid un-needed redirects as much as possible. When there is a redirect the response is sent to the browser with status code 302 (object moved) for a temporary redirect or 301 (object moved permanently) for a permanent redirect and the new url is provided then the browser navigates to the new url. So you have extra web requests going on for every redirect. For good SEO avoid un-needed redirects.

You certainly don't want your canonical url to do a permanent redirect. Its like saying this is the correct url but then saying no it isn't this page moved permanently to this other url. Don't make your page use extensionless urls and then have .aspx in the canonical, its a very bad idea.

There has not been any change in how urls work in mojoPortal.

mojoPortal only creates a 301 when you change the url of an existing page so that the old url will redirect to the new one. It does not create any redirects for new pages and you should not need any. You either use .aspx or you use extensionless urls but not both for the same page.

[having canonical url with .aspx, in case if the site needs to b revoked to "Mandatory Extension" in mere future, if required]

The only way that would happen is if you think you may need to move the site to an older version of IIS where the extensionless urls might not work like Windows 2003/IIS 6. If you really think that is a risk to be concerned about then my advice is don't use extensionless urls, just stick with .aspx and don't change them. You definitely should not have the canonical url with .aspx and the actual url without it.

Hope that helps,

Joe

10/5/2011 5:13:57 PM
Gravatar
Total Posts 57
Web Platform Evangelist.

Re: Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi Joe,
Yeah! That was a great info. thanks a ton. "Joe deserves a Beer". But what if my website's visitor tries to open "~/newpage.aspx", At that time, i feel my site should throw a 404 page and instead shouldn't redirect to the right page. so in that case it matters a lot right? So as per my knowledge there's no other feature on mojoPortal that can do this. Am i right? So, how do I handle that situation?

Plz. take a look at one of my website that i had built using mojoPortal v.2.3.6.5 -- GBinterior.com

--
Regards
Guruprasad Balaji

10/5/2011 6:15:29 PM
Gravatar
Total Posts 18444

Re: Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi,

Yes, if an url does not exist in your site and it is not an url configured to redirect to another url it should result in a 404 page not found.

I think most likely the redirect for ~/newpage.aspx was created by changing the url or page name on an existing page which would change the url, so mojoportal created a 301 redirect automatically if a page url changes.

You can look for that redirect url under Administration > Advanced Tools > 301 Redirect Manager

and you can delete it if it exists and then a request for ~/newpage.aspx should result in a 404

See also the article 301 Redirect Manager

Hope that helps,

Joe

 

10/5/2011 6:54:50 PM
Gravatar
Total Posts 57
Web Platform Evangelist.

Re: Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi Joe,
Whoa! This was the answer i was expecting for. Thanks Joe. By the Way, why do you want to make it fall-back to a 404 page? My question on this thread was, "When i create a extension less url, it should automatically map an entry to ".aspx" as it did in its previous versions but not now. Why so?" have you removed this feature? I dont want to make it result in a 404 page rather it should automatically create a redirect to the extensionless url. This was my scenario. :-)

--
Regards
Guruprasad Balaji

10/5/2011 7:11:15 PM
Gravatar
Total Posts 18444

Re: Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi,

If you created a page /somepage.aspx before you enabled extensionless urls and then you later changed the url to /somepage then I agree it should and it does create a 301 redirect from /somepage.aspx to /somepage because the previous url may be indexed by google or bookmarked so a redirect is needed.

If after you change to enable extensionless urls you create a new page /someotherpage it should not and does not and never has created a redirect from /someotherpage.aspx to /someotherpage because /someotherpage.aspx never existed as an url before in your site and it should be a 404 page not found and not a redirect. So there never was a feature to do that and it has not changed in recent versions.

Hope that helps,

Joe

10/5/2011 7:47:35 PM
Gravatar
Total Posts 57
Web Platform Evangelist.

Re: Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi Joe,

Let me explain you more specifically.

Environment 1: Having Mojoportal ver.2.3.6.0 installed.

  1. Having Extensionless URLs enabled on web.config and followed the documentation as given on your website.
  2. Have set "Default Friendly Url Pattern = page-name"
  3. Now, when i create a sample page other than the default home page that comes pre-installed, with the name say, "~/new-page" as suggested by the url suggester, when i hit save, it saves perfectly and and also when i test simply by requesting "/new-page.aspx" on the web browser, it automatically redirects to the "http://localhost/new-page".


But......

Environment 2: Having Mojoportal ver.2.3.6.5 or ver.2.3.7.0 installed.

  1.     Having Extensionless URLs enabled on web.config and followed the documentation as given on your website.
  2.     Have set "Default Friendly Url Pattern = page-name"
  3.     Now, when i create a sample page other than the default home page that comes pre-installed, with the name say, "~/new-page" as suggested by the url suggester, when i hit save, it saves perfectly and and also when i test simply by requesting "/new-page.aspx" on the web browser, it automatically shows up a "404 page" rather than redirecting itself to the "http://localhost/new-page". And I need to enable it manually on "301 Redirect Manager", then it works correctly, as seen on the Live website GBinterior.com.

    Thank You :-)

 

10/6/2011 7:49:12 AM
Gravatar
Total Posts 18444

Re: Extensionless URLs issue on mojoPortal Ver.2.3.6.5

Hi,

Sorry, but I am 99.99% certain that you are mistaken about environment one and what happens when a new page is created.

I am 100% sure that I never implemented it to create a 301 for new pages. 

I am also 100% sure that I never made a release with version 2.3.6.0, so if that is really your version it was probably something you compiled yourself from source code in between official releases. Perhaps you or someone else modified the code to produce this behavior if it really happens.

There is no need to make a 301 for an url that never existed before because nothing links to it, nothing has indexed it and nothing has bookmarked it. Creating a 301 just in case a user types in the url with a .aspx is not needed in my opinion. Most users never type in urls, they just click links and if they do type in an url they most likely just type in the domain name and then click a link in the menu to get to a page. So there has never been a feature to create 301s for that scenario, and there is no plan to implement such a feature.

Best,

Joe

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