You couldn't get it to work with my method? It should work, maybe I'm just confusing you with the terminology though.
You can't make a skin that doesn't load the controls, the system is setup so they have to go somewhere. That is why a requirement for every skin is that you have a ContentPane in it.
But using your approach you could do it by placing some javascript in the page to do the redirect.
If you make the one and only Portal Alias for the portal in question point to your temporary page it will accomplish what you are trying to do.
When DNN attempts to find the correct alias and it is not able to it will automatically redirect to the first Portal Alias.
I did try and it redirects to the default portal - if the domain I want to direct to the new portal is
www.mydomain.com then using
www.mydomain.com/anotherfile.html there is no match and it finds the default portal.
Your right I did create a contentpane td in my image page. Why will not going anywhere cause a problem? - I agree not the correct usage, but it does seem to do the job.
Oh right, i guess didn't make that clear. I was thinking about one portal.
The system redirects to the default portal's first alias if an alias cannot be found.
For the Skin thing, the modules will all be added to the ContentPane if the pane that they are originally assigned to cannot be found, so they will show up anyway.
One way to hide them though is to place a little inline CSS in your Pane elements:
Caroig
Member
200 Points
40 Posts
Re: Replace home page with a link to HTML doc
Jul 19, 2006 05:02 PM|LINK
The only way I can see to achieve what I want is to create a skin that just loads my image and no dnn controls - so I think I'll go with that.
Seems a shame that there's no easy way to do this - all the elements seem to be there.
Thanks
J7Mitch
Star
13145 Points
2632 Posts
Re: Replace home page with a link to HTML doc
Jul 19, 2006 06:34 PM|LINK
You couldn't get it to work with my method? It should work, maybe I'm just confusing you with the terminology though.
You can't make a skin that doesn't load the controls, the system is setup so they have to go somewhere. That is why a requirement for every skin is that you have a ContentPane in it.
But using your approach you could do it by placing some javascript in the page to do the redirect.
Something like this.
<script language="Javascript1.1" type="text/javascript">
location.href = 'www.newsite.com/mypage.html';
</script>
Caroig
Member
200 Points
40 Posts
Re: Replace home page with a link to HTML doc
Jul 19, 2006 08:07 PM|LINK
I did try and it redirects to the default portal - if the domain I want to direct to the new portal is www.mydomain.com then using www.mydomain.com/anotherfile.html there is no match and it finds the default portal.
Your right I did create a contentpane td in my image page. Why will not going anywhere cause a problem? - I agree not the correct usage, but it does seem to do the job.
Thanks for the ideas though.
J7Mitch
Star
13145 Points
2632 Posts
Re: Replace home page with a link to HTML doc
Jul 19, 2006 09:30 PM|LINK
Oh right, i guess didn't make that clear. I was thinking about one portal.
The system redirects to the default portal's first alias if an alias cannot be found.
For the Skin thing, the modules will all be added to the ContentPane if the pane that they are originally assigned to cannot be found, so they will show up anyway.
One way to hide them though is to place a little inline CSS in your Pane elements:
<td id="ContentPane" runat="server" style="display:none" >