leeego Posted October 17, 2013 Share Posted October 17, 2013 (edited) I've set up a DEV and PROD shop to get a proper update management. I did this by duplicating both DB (of course new name and user) and the folder with all the files. I then changed the shop url within the DB to match the subdomain of the DEV shop and also changed the details in settings.inc.php to match the DEV DB. Everything seems to work fine. The DB connection is established, the subdomain routes to the DEV files. However, if I log in to the backend of DEV or PROD, they still have the same setting for the shop url. Even worse, they get synced! So if I change it in DEV, it also changes in PROD. On the dashboard, I get the following warning: You are currently connected under the following domain name: dev.myshop.com This is different from the main shop domain name set in the "Multistore" page under the "Advanced Parameters" menu: www.myshop.com But Multistore is not enabled in neither DEV nor PROD. How is that possible? I also noticed that other configuration details get synced. So there is some connection between the two I can't see yet. Edited October 18, 2013 by leeego (see edit history) Link to comment Share on other sites More sharing options...
NemoPS Posted October 18, 2013 Share Posted October 18, 2013 Have you changed the database connection settings in settings.inc.php (config folder)? Link to comment Share on other sites More sharing options...
leeego Posted October 18, 2013 Author Share Posted October 18, 2013 Yes, I changed _DB_NAME_, _DB_USER_ and _DB_PASSWD_ accordingly to the DEV database. Link to comment Share on other sites More sharing options...
NemoPS Posted October 18, 2013 Share Posted October 18, 2013 So if you check the configuration information on the dev site, it's the same as your PROD site? Even though credentials are different? Link to comment Share on other sites More sharing options...
leeego Posted October 18, 2013 Author Share Posted October 18, 2013 Yes, exactly. As soon as I update something in the config (via backend), it is automatically applied to the other shop config as well. Link to comment Share on other sites More sharing options...
NemoPS Posted October 18, 2013 Share Posted October 18, 2013 What if you try changing a couple of settings in the database manually? Say, if you change a product's name? Is it reflected in the back office/front office of either or both of the 2? Link to comment Share on other sites More sharing options...
leeego Posted October 18, 2013 Author Share Posted October 18, 2013 Ok, I just did a couple of checks and it seems both PROD and DEV connect to DEV DB only. But the credentials in settings.inc.php on the PROD correctly point to the PROD DB. I'm confused. Link to comment Share on other sites More sharing options...
NemoPS Posted October 18, 2013 Share Posted October 18, 2013 Can you backup the settings file, delete it and see what happens? Link to comment Share on other sites More sharing options...
leeego Posted October 18, 2013 Author Share Posted October 18, 2013 Ok, they both seem to listen to the same settings.inc.php (the one from the DEV). If I delete the settings.inc.php from the PROD, nothing happens. Both shops still work. If I delete the settings.inc.php from the DEV, I get the following error: Error: "install" directory is missing Link to comment Share on other sites More sharing options...
NemoPS Posted October 18, 2013 Share Posted October 18, 2013 What's their folder structure? Link to comment Share on other sites More sharing options...
leeego Posted October 18, 2013 Author Share Posted October 18, 2013 They're next to each other in the document root: www/ myshop.com/ dev.myshop.com/ Link to comment Share on other sites More sharing options...
leeego Posted October 18, 2013 Author Share Posted October 18, 2013 Or did you mean something else? Link to comment Share on other sites More sharing options...
NemoPS Posted October 18, 2013 Share Posted October 18, 2013 No, that;s what I meant. I don't really get it Link to comment Share on other sites More sharing options...
leeego Posted October 25, 2013 Author Share Posted October 25, 2013 (edited) Ok, I fixed the problem. It wasn't related to PrestaShop but the Apache VirtualHost configuration of PROD and DEV. I've set a wrong redirect somewhere. Edited October 25, 2013 by leeego (see edit history) Link to comment Share on other sites More sharing options...
Recommended Posts