matthieul

AmyS matthieul yap, that's exactly it =)....but just in case it wasn't clear: You do NOT specify @override when "adding" the component anywhere (in quilts, other components etc.), the component ID stays the original one, that's the point of @override, you don't have to change your components in hundreds of quilts if you want to "override" an original one...

Hey, 

Are you just changing the domain from A to B? Are you using a domain that exists today, do you intend to migrate any content? 

Answers to the above aside, if you're simply going from A to B and B is brand new and not used before then this is simple with no real issues or concerns, Khoros will be able to switch the domains for you, and support with adding the new domain to your security certificate, just raise a case.

Your old domain needs to stay active and providing Khoros redirect correctly "no reason they shouldn't" all your old links will work fine and you'll have no SEO impact. 

Google for example will see that your domain has changed as it will hit a 302 and over time will update it's index meanwhile all your links will work fine so other than checking your 404's on the day and after the switch to make sure the switch is working ok there isn't much you need to worry about. 

We still have redirects in place for a few of our legacy "help" domains which are on a 302, Ideally should be a 301 redirect but to be honest the 302 was enough to update organic search, i think the likes of google seem to know whilst its a 302 "temp" it's actually permanent. 

For example http://help2.talktalk.co.uk/ resolves to Khoros who 302 it to https://community.talktalk.co.uk/

Hello matthieul  try with restadmin() instead of rest()