Migrating from test domain to live - relative file paths

[nwlinux]

I am developing a Get Simple site at www2.domain.com. Looking at the file paths in the XML, I will have to open up each file and "search and replace" the www2 out of the relative file path. I read a couple of forums posts on the topic, none of which worked well. Any progress on this problem, or is there a better method of working here?

References:
http://get-simple.info/forum/topic/3434/...pdf-links/
http://get-simple.info/forum/post/23856/#p23856

[yojoe]

Unfortunately there's no solution other than "search&replace" after you created the content w/o fixing relative urls before adding images/links.

thread: http://get-simple.info/forum/post/26929/
useful software: http://get-simple.info/forum/post/14952/#p14952

[nwlinux]

That is the answer that I was expecting. However, it was worth a shot. The domain has a little over a hundred pages, so it won't be a deal breaker. Either way, I am pleased with the sub one-second page loads on the new GS site :-)

Thank you for your input yojoe.

Mark

[Connie]

if you use an editor like Notepad++, you can open all files at once and do a global search and replace ..

there are other tools out there as well which replace the strings in all files of one folder

[shawn_a]

Connie wrote:if you use an editor like Notepad++, you can open all files at once and do a global search and replace ..

there are other tools out there as well which replace the strings in all files of one folder

There is another thread where we are discussing solutions, not very successfully, but feel free to comment if you can find it.

[nwlinux]

I ended up using grep and sed to replace strings within the XML. It took around 0.5 second to accomplish the task. It couldn't have been any easier.

Overall, not a big impass. The input command for Linux systems is at http://nwlinux.com/fix-get-simple-cms-ur...w-domain/.

[octopus]

In 3.0 the best way to avoid this problem is to set your WebiteURL on the setting page to just '/'. That way it does not put the domain name into every embedded link. Unfortunately 3.1 does not allow this without modification



One way to get around this is to go into your /data/other/website.xml file directly and set your SITEURL to just '/'. You need to do this very early on before you start building your site and before you start embedding anything via the editor. Maybe the developers will release the new restriction theyve added to the URL field on the setting page. (?? hopefully)