Products » Support Forums 

Support Forums

HomeHomeDotNetNuke Modu...DotNetNuke Modu...Url MasterUrl Master301 Redirects for Domain Migration301 Redirects for Domain Migration
Previous
 
Next
New Post
1/7/2010 10:31 AM
 

Ok, so setting up these redirects is easy, except if you want to re-use that other domain.

There's two choices:

1) in the reckonlimited.com.au site, add the reckon.com.au portal alias, and make sure the site responds to the reckon.com.au domain.  This probably won't work if you're re-using the reckon.com.au domain straight away (because you can't get the same domain to work on two different installs).

2) in the reckon.com.au site, use the 'permanent redirect' function of the existing tabid 88 and tabid 63 pages, and set up the redirected urls to be the reckonlimited.com.au/about-reckon pages.  In other words, setup the redirects in the first to send the user to the second portal.

I hope that makes sense.

-Bruce

 
New Post
1/8/2010 1:17 AM
 

Hi Bruce

Unfortunately we do need to re-use the reckon.com.au domain (the reason for the migration in the first place).

What I was planning on doing is what you've descibed in the second option, however, as the URL Master module pre-populates the domain when entering new redirect URLs this is not possible.

I have even tried adding reckonlimited.com.au as another alias for the reckon.com.au site so it would appear in the URL Master module - however, it appears that you cannot select from portal aliases when setting up these URLs.

Thanks

Sam

 
New Post
1/8/2010 1:28 AM
 

Sam - with the option 2 - I didn't mean use the Url Master Page Urls page, I meant go into the 'Page Settings' for the page you want to redirect, and add the Url into the 'Permanent Redirect' option (it's toward the bottom of the 'Page Settings' page - you need to tick the 'permanent redirect' option and enter the redirection url).  This means that requests for the reckon.com.au url will be redirect to the reckonlimited.com.au page.

Unrelated to the solution, but just to explain, the portal alias you see on the page urls page is dictated by the current portal alias for the requested site.  If you have two portal alias for your site, then requesting the alias1.com/admin/pageurls url will result in the displayed urls showing alias1.  Requesting alias2.com/admin/pageurls will result in the displayed urls showing alias 2.  The unchangeable value you see on the page is just the current portal alias being shown.  This is why it is in the admin (site specific) menu instead of the host (installation wide) menu.

 
New Post
1/8/2010 5:10 AM
 

Hi Bruce

Thanks for your response - I know the advice that you have given is away from your module and is quite useful.

The unfortunate issue with our situation is that we have already undertaken the domain migration, and as such the new URLs are the only ones that exist - and work. I was hoping to use the URL Master module to redirect the old URLs to the new ones.

Thanks

Sam

 
New Post
1/8/2010 12:35 PM
 

Well, the only way you're going to get the Url Master module to handle it is if you can get the correct website (the one with the new url) to respond to the old urls.  To do that you'd have to point the reckon.com.au domain at the reckonlimited.com.au site, which I assume you can't do because you've already created the new reckon.com.au site.

If you have already created the new reckon.com.au site, and it's got the Url Master module installed, you may be able to still redirect them.

Here's what you would do:

1. Create two new tabs, one for each of the to-be-redirected urls.  As you don't want them to be visible from the menu, exclude them from the menu via the page settings.  Customers won't see these urls unless they're using an old link or search engine reference.

2.  Put in the Url to redirect to in the 'external url' field

3. Create custom Urls for those new pages in the 'Page Urls' page.  These will look like /pagename/tabid/xx/default -  note, no .aspx on the end.  Set the http status to '200'.

4. Go to the friendly url settings page, expand the 'advanced rewriting section', and select the option which says to 301 redirect to external urls.

Save all the change and try it out.  What should happen is that your request the /pagename/tabid/xx/default.aspx page, which will then load up the page you created.  However, the Url Master module will detect that you have selected to do a redirect to the external page, and will forward on the request, which will go to the reckonlimited.com.au version as desired.

Give it a try and see how it goes.

 
Previous
 
Next
HomeHomeDotNetNuke Modu...DotNetNuke Modu...Url MasterUrl Master301 Redirects for Domain Migration301 Redirects for Domain Migration


Support Guidelines.. Please read before posting

To get support on iFinity products and services, please search the forums for the the answer to the problem you are seeking. If you cannot find a solution, post a question in the relevant forum.   Ensure that you specify the relevant versions of the problem, and the actual error message or a detailed description of the problem.    You will need to register with this site to post on the forum.  If you have a Microsoft Live (Hotmail/Passport) account you can use that.  If you have a Open Id account you can use that.  If you neither of these, you will need to register a user Id and password.

Please note : If you are posting a new thread for the Url Master module, please include the following information where applicable:

- Url Master version

- DotNetNuke version

- Example Url where possible

- If there is an error, please post the full error text and/or stack trace (from the DotNetNuke event log).