I need to do some changes in webshop based on TeaCommerce. Client complains about /en/ in url path. I have tried to turn on useDomainPrefixes property, but it's not working properly.
So I would like to rename it from 'en' to 'da', but I wouldn't like to destroy whole site. Do you think it's safe just to change name of this node?
Of course I know that I need to check all scripts, if there is anywhere hardcoded path with 'en'.
If you use the starter kit there is a 301 redirect module installed that will redirect from the /en url's to the new /da. If you don't use the starter kit - you should make 301 redirects for all old url's so your page rank doesnt drop.
There is nothing in Tea Commerce that needs the /en node (except we need to associate the hostname here). We normally set the useDomainPrefixes = true to hide the /en(or /da) from the url path and it works. Try and republish your entire site and refresh the xml cache to see if it works.
Thing is, that I don't want to redirect to da node. In nodes tree ther is only one, 'en', but site is in Danish, so client would like to have da instead of en. This site was built by someone else, I need only to make some changes.
I will try again with useDomainPrefixes (but first after weekend). When I set it to YES lately, for some subpages I got "too many redirections" error in webbrowser (chrome), so I set it back to NO. But I haven't republished site and refreshed xml cache, so I try do to it again.
I thought, that maybe if there is only one "language" node, I can easly change it's name...
If your site is only in one language you could remove the /en/ or /da/ completely for the site.
Just remember that your navigation is going to be one level higher. But you also have to change things in the javascript to do this, so can get a bit messy.
But diong this you have the advantage of not having to link all products to the catelogue, they can go direct in the structure.
Dont know what you have to change in the java script to handle the "missing" /en??
If you only have /en - you can still just have the products in the /en section and not use the master catalog. The master catalog is only good if you have multiple languages and want to manage your site more easy.
Changing name of "en" node
Hi everyone!
I need to do some changes in webshop based on TeaCommerce. Client complains about /en/ in url path. I have tried to turn on useDomainPrefixes property, but it's not working properly.
So I would like to rename it from 'en' to 'da', but I wouldn't like to destroy whole site. Do you think it's safe just to change name of this node?
Of course I know that I need to check all scripts, if there is anywhere hardcoded path with 'en'.
Regards
Thomas
Hi Thomas
If you use the starter kit there is a 301 redirect module installed that will redirect from the /en url's to the new /da. If you don't use the starter kit - you should make 301 redirects for all old url's so your page rank doesnt drop.
There is nothing in Tea Commerce that needs the /en node (except we need to associate the hostname here). We normally set the useDomainPrefixes = true to hide the /en(or /da) from the url path and it works. Try and republish your entire site and refresh the xml cache to see if it works.
Kind regards
Anders
Hi Anders
Thanks for reply.
Thing is, that I don't want to redirect to da node. In nodes tree ther is only one, 'en', but site is in Danish, so client would like to have da instead of en. This site was built by someone else, I need only to make some changes.
I will try again with useDomainPrefixes (but first after weekend). When I set it to YES lately, for some subpages I got "too many redirections" error in webbrowser (chrome), so I set it back to NO. But I haven't republished site and refreshed xml cache, so I try do to it again.
I thought, that maybe if there is only one "language" node, I can easly change it's name...
Regards
Thomas
To many redirects is because of an infinite loop of redirects. So you have to check which redirection is active at the different nodes
Kind regards
Anders
If your site is only in one language you could remove the /en/ or /da/ completely for the site.
Just remember that your navigation is going to be one level higher. But you also have to change things in the javascript to do this, so can get a bit messy.
But diong this you have the advantage of not having to link all products to the catelogue, they can go direct in the structure.
Am I right Anders?
Your right rich :)
Dont know what you have to change in the java script to handle the "missing" /en??
If you only have /en - you can still just have the products in the /en section and not use the master catalog. The master catalog is only good if you have multiple languages and want to manage your site more easy.
is working on a reply...