Hi all, is there a way that I can easily change the default home page for my site? My structure is as follows
Content
----Home
----------Blog
----------Account
----------Etc
I know simply browsing to my site using http://sitename will display my 'Home' page by default. Is there an easy way that I can change my default 'Home' page to instead go to 'Blog' without having to append the page name to the url?
Right click on the 'blog' node and select 'manage hostnames' and add your domain, and this will then make 'blog' load as the default document of the domain.
Using our.umbraco.org/.../umbracoredirect on as top-level node causes xslt to be unable to save without disabling error checking, for some strange reason.
How to change the default home page?
Hi all, is there a way that I can easily change the default home page for my site? My structure is as follows
Content
----Home
----------Blog
----------Account
----------Etc
I know simply browsing to my site using http://sitename will display my 'Home' page by default. Is there an easy way that I can change my default 'Home' page to instead go to 'Blog' without having to append the page name to the url?
Hi Andy,
Have a look at these wiki pages:
http://our.umbraco.org/wiki/reference/umbraco-best-practices/umbracointernalredirectid and http://our.umbraco.org/wiki/reference/umbraco-best-practices/umbracoredirect
Hope this helps.
Regards,
/Dirk
Thanks for your reply. Do you have any examples on how to use this feature?
Hi Andy, this Wiki entry might shed some light on it for you.
http://our.umbraco.org/wiki/how-tos/creating-content-folders
-- Nik
Right click on the 'blog' node and select 'manage hostnames' and add your domain, and this will then make 'blog' load as the default document of the domain.
Using our.umbraco.org/.../umbracoredirect on as top-level node causes xslt to be unable to save without disabling error checking, for some strange reason.
http://forum.umbraco.org/yaf_postst8720_Xslt-file-could-not-be-saved-anymore.aspx
If this affects you after redirecting your top node, try this redirect package for a 'proper' 302 redirect - >http://www.afdeling18.dk/blog/2007/7/19/redirect-package.aspx (seems to work fine on v4)
is working on a reply...