Trouble Moving Cart to Root Folder

[webgear_aus]

Thanks for your prompt responses and help.
I found another resource which gave me a clue on how to solve this.
I made a fresh installation, saved the two new configure files, then deleted the installation.
I copied the relevant parts of the new config files containing the correct paths to the old config files.

For reference here are the updated paths (maybe this will help solve this for someone else in the future);

define('HTTP_SERVER', 'http://www.shop.mydomain.com');
define('HTTPS_SERVER', 'https://www.shop.mydomain.com');
define('HTTP_CATALOG_SERVER', 'http://www.shop.mydomain.com');
define('HTTPS_CATALOG_SERVER', 'https://www.shop.mydomain.com');

define('DIR_WS_CATALOG', '//');
define('DIR_WS_HTTPS_CATALOG', '//');

define('DIR_FS_CATALOG', '/path1/path2/path3/shop/');
define('DIR_FS_SQL_CACHE', '/path1/path2/path3/shop/cache');


This now works :) except for one minor unknown issue...
I had a new admin theme set up but the admin section has somehow reverted back to the original zencart admin theme, even though all the files are the original ones in the new location.

Anyway, I'll figure it our or re-instal the admin theme.

Thanks again for your help.

[Design75]

define('DIR_WS_CATALOG', '//');
define('DIR_WS_HTTPS_CATALOG', '//');

Part of your problem is the double // (in red) remove one so it looks like this

define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_CATALOG', '/');

[webgear_aus]

Thanks for your assistance.
Actually it works with both // (this was the correct coding taken from the config file of the new install)
Case is closed.
The posted code in thread #11 works :)

[anysigns]

Since the standard Classic template doesn't include that link, yours has been hard-coded in your template to point to the old URL. Use the Admin - Tools - Developers Tool Kit to search for vinyl-stickers.

Thanks! That fixed the issue I was having. Looks like I'm all set. Thank you very much.

[dbltoe]

Thanks for your assistance.
Actually it works with both // (this was the correct coding taken from the config file of the new install)
Case is closed.
The posted code in thread #11 works :)

The case is NOT closed as // is NOT a standard designation and may ruin SE results. You need to find out why it needs // to work and fix it.

[RodG]

Actually it works with both // (this was the correct coding taken from the config file of the new install)
Case is closed.
The posted code in thread #11 works :)

Sorry, but case not closed.

The double slashes // are incorrect, and although 99.9% of the time this will not cause any problems or issues, it is the other .1% you need to worry about.

Is it worth arguing the point when reverting back to a single slash will mitigate the issue(s) that will otherwise be very difficult to debug?

We are urging you to do this for our sanity, else you'll be back here in the not so distant future asking why some customers are reporting random 'page not found' errors, but by that time, this thread will be long forgotten about and we will probably end up asking you all sorts of unrelated questions before we finally work our way back to this cause.

We won't be impressed.

Cheers
Rod