Edit History

7 hours ago, musicmaster said:

Hi Wolf,

 -  For hard copying I would suggest exporting the structure of those extra tables from the old database and importing it in the new one. Then you can add their name to the list of tables that should be copied in the config file.

 - Copy_shopdata has no features for copying multishop. It just copies everything. So it is unclear to me how you want to use it to selectively copy some of the shops of your installation.

- I don't understand your problems with removing a shop in Prestashop. Sure, it may leave some data behind. But you can remove that with the function "Remove deleted shops info" on the Cleanup page of Prestools.

- I see there is a problem in copying ps_shop_url. Probably the best solution is not copying it.

- "copy_shopdata_imghub.php" uses data from the ps_shop_url tables on the lines that cause an error in your case. It needs the correct urls of the old and the new shop to know the locations for the copying. So I would need to know what you did there to solve this problem. In a normal situation it doesn't give errors.

- good idea, that should do

- aaah, ok, that´s the problem, I thought (from the manual saying u have to set-up same shop IDs) that it actually checks the shop IDs while migrating the data

- removing multistore shops is blocked in PS, the delete button vanishes as soon as I think first user is registered within the shop because it does not have functions to move users and connected stuff between shops, I´ve already prepared SQLs for all tables with shop_id column to move or remove all the stuff connected to said shop ID

- yeah, I removed it from the list

- so it´s pretty much connected with the point before, because copying that table doesnt work, url of my primary shop is set up from the installation of the new empty PS, so it does not have the url of the old store(seems like other 3 shops have urls filled with old urls), but the main one has the new url, so that´s why it says old and new directory are the same, you should mention this somewhere in manual as it´s not that obvious

7 hours ago, musicmaster said:

Hi Wolf,

 -  For hard copying I would suggest exporting the structure of those extra tables from the old database and importing it in the new one. Then you can add their name to the list of tables that should be copied in the config file.

 - Copy_shopdata has no features for copying multishop. It just copies everything. So it is unclear to me how you want to use it to selectively copy some of the shops of your installation.

- I don't understand your problems with removing a shop in Prestashop. Sure, it may leave some data behind. But you can remove that with the function "Remove deleted shops info" on the Cleanup page of Prestools.

- I see there is a problem in copying ps_shop_url. Probably the best solution is not copying it.

- "copy_shopdata_imghub.php" uses data from the ps_shop_url tables on the lines that cause an error in your case. It needs the correct urls of the old and the new shop to know the locations for the copying. So I would need to know what you did there to solve this problem. In a normal situation it doesn't give errors.

- good idea, that should do

- aaah, ok, that´s the problem, I thought (from the manual saying u have to set-up same shop IDs) that it actually checks the shop IDs while migrating the data

- removing multistore shops is blocked in PS, the delete button vanishes as soon as I think first user is registered within the shop because it does not have functions to move users and connected stuff between shops, I´ve already prepared SQLs for all tables with shop_id column to move or remove all the stuff connected to said shop ID

- yeah, I removed it from the list

- so it´s pretty much connected with the point before, because copying that table doesnt work, url of my primary shop is set up from the installation of the new empty PS, so it does not have the url of the old store(seems like other 3 shops have urls filled with old urls, but the main one has the new url, so that´s why it says old and new directory are the same, you should mention this somewhere in manual as it´s not that obvious

7 hours ago, musicmaster said:

Hi Wolf,

 -  For hard copying I would suggest exporting the structure of those extra tables from the old database and importing it in the new one. Then you can add their name to the list of tables that should be copied in the config file.

 - Copy_shopdata has no features for copying multishop. It just copies everything. So it is unclear to me how you want to use it to selectively copy some of the shops of your installation.

- I don't understand your problems with removing a shop in Prestashop. Sure, it may leave some data behind. But you can remove that with the function "Remove deleted shops info" on the Cleanup page of Prestools.

- I see there is a problem in copying ps_shop_url. Probably the best solution is not copying it.

- "copy_shopdata_imghub.php" uses data from the ps_shop_url tables on the lines that cause an error in your case. It needs the correct urls of the old and the new shop to know the locations for the copying. So I would need to know what you did there to solve this problem. In a normal situation it doesn't give errors.

- good idea, that should do

- aaah, I thought (from the manual saying u have to set-up same shop IDs) that it actually checks the shop IDs while migrating the data

- removing multistore shops is blocked in PS, the delete button vanishes as soon as I think first user is registered within the shop because it does not have functions to move users and connected stuff between shops, I´ve already prepared SQLs for all tables with shop_id column to move or remove all the stuff connected to said shop ID

- yeah, I removed it from the list

- so it´s pretty much connected with the point before, because copying that table doesnt work, url of my primary shop is set up from the installation of the new empty PS, so it does not have the url of the old store(seems like other 3 shops have urls filled with old urls, but the main one has the new url, so that´s why it says old and new directory are the same, you should mention this somewhere in manual as it´s not that obvious

7 hours ago, musicmaster said:

Hi Wolf,

 -  For hard copying I would suggest exporting the structure of those extra tables from the old database and importing it in the new one. Then you can add their name to the list of tables that should be copied in the config file.

 - Copy_shopdata has no features for copying multishop. It just copies everything. So it is unclear to me how you want to use it to selectively copy some of the shops of your installation.

- I don't understand your problems with removing a shop in Prestashop. Sure, it may leave some data behind. But you can remove that with the function "Remove deleted shops info" on the Cleanup page of Prestools.

- I see there is a problem in copying ps_shop_url. Probably the best solution is not copying it.

- "copy_shopdata_imghub.php" uses data from the ps_shop_url tables on the lines that cause an error in your case. It needs the correct urls of the old and the new shop to know the locations for the copying. So I would need to know what you did there to solve this problem. In a normal situation it doesn't give errors.

- good idea, that should do

- aaah, I thought (from the manual saying u have to set-up same shop IDs) that it actually checks the shop IDs while migrating the date

- removing multistore shops is blocked in PS, the delete button vanishes as soon as I think first user is registered within the shop because it does not have functions to move users and connected stuff between shops, I´ve already prepared SQLs for all tables with shop_id column to move or remove all the stuff connected to said shop ID

- yeah, I removed it from the list

- so it´s pretty much connected with the point before, because copying that table doesnt work, url of my primary shop is set up from the installation of the new empty PS, so it does not have the url of the old store(seems like other 3 shops have urls filled with old urls, but the main one has the new url, so that´s why it says old and new directory are the same, you should mention this somewhere in manual as it´s not that obvious