I'm going to upgrade my store from OC 2.1.0.2 to the latest OC 3 version and probably I'm going to pay for expert service.
However, I want to make the redesign of my store by myself, but I'm not sure if it's the best way to install fresh OC 3 installation, do the redesign, and then hire an expert to migrate OC 2 database (clients, orders, products) to my new installation or there is a better way to do it?
I won't migrate any plugin functionalities, just clients, orders, and products.
Thanks!
That looks like a not so bad plan.
If you want to instead upgrade the entire site first, there's this comment that you should read:
viewtopic.php?f=202&t=205805&p=729542#p729542
Instead of doing what's advised in linked thread, an update is always (does no matter from which version) a hazardous and risky game!
At the end we will see you here again because of all the troubles you now may have.
Instead of "upgrading", follow this:
1. make a full backup of your current store database tables with phpMyAdmin (or another similiar tool you like)
> reason why NOT using the internal backup function is, only that backup will export also the table commands, while the internal backup export only the content!
2. install the new version in a new and separate folder
> this can be also a local instance (e.g. with XAMPP)
3. compare those tables from the database backup with the new table structure
> you have to add some fields, a few can be renamed in the NEW database tables
4. import now - again with phpMyAdmin - those tables you like to have in the new store also
> that would be e.g. customer, category, product, order etc. tables
>> DO NOT IMPORT THE settings table content!
5. copy the images from the old store into the new
6. install those additional extensions only you will need in the new store
7. install the custom theme [optional]
Basically your work is done with these steps.
Open the new store (front- & backend or backend only), and check of all data does exist.
Check the new settings and define them as you need.
This whole process my need 2,3 hours (a beginner may need a bit longer), but you can be ensure that the new store will run from the beginning.
8. If the new store is installed on the same server as the old store is (but separate folder!), reroute the address in your server configuration tool (CPanel, Plesk, etc.) to the folder of the new store
9. now when the new store works as expected, rename the .htaccess.txt to .htaccess
10. enable in the backend the SEO-URLs
Done.
No need to hire someone, pay money for some services, let other (unknown) people on the server.
In the (rare) case you have troubles, come back to this forum and ask.
At the end we will see you here again because of all the troubles you now may have.
Instead of "upgrading", follow this:
1. make a full backup of your current store database tables with phpMyAdmin (or another similiar tool you like)
> reason why NOT using the internal backup function is, only that backup will export also the table commands, while the internal backup export only the content!
2. install the new version in a new and separate folder
> this can be also a local instance (e.g. with XAMPP)
3. compare those tables from the database backup with the new table structure
> you have to add some fields, a few can be renamed in the NEW database tables
4. import now - again with phpMyAdmin - those tables you like to have in the new store also
> that would be e.g. customer, category, product, order etc. tables
>> DO NOT IMPORT THE settings table content!
5. copy the images from the old store into the new
6. install those additional extensions only you will need in the new store
7. install the custom theme [optional]
Basically your work is done with these steps.
Open the new store (front- & backend or backend only), and check of all data does exist.
Check the new settings and define them as you need.
This whole process my need 2,3 hours (a beginner may need a bit longer), but you can be ensure that the new store will run from the beginning.
8. If the new store is installed on the same server as the old store is (but separate folder!), reroute the address in your server configuration tool (CPanel, Plesk, etc.) to the folder of the new store
9. now when the new store works as expected, rename the .htaccess.txt to .htaccess
10. enable in the backend the SEO-URLs
Done.
No need to hire someone, pay money for some services, let other (unknown) people on the server.
In the (rare) case you have troubles, come back to this forum and ask.
Full Stack Web Developer :: Dedicated OpenCart Development & Support DACH Region
Contact for Custom Work / Fast Support.
Thanks for the comprehensive answer! Besides exporting and editing some information in the database I have not much experience in table creation migration of information and so on, that's why I'm willing to pay someone more experienced.OSWorX wrote: ↑Mon Jan 10, 2022 10:07 pmInstead of doing what's advised in linked thread, an update is always (does no matter from which version) a hazardous and risky game!
At the end we will see you here again because of all the troubles you now may have.
Instead of "upgrading", follow this:
1. make a full backup of your current store database tables with phpMyAdmin (or another similiar tool you like)
> reason why NOT using the internal backup function is, only that backup will export also the table commands, while the internal backup export only the content!
2. install the new version in a new and separate folder
> this can be also a local instance (e.g. with XAMPP)
3. compare those tables from the database backup with the new table structure
> you have to add some fields, a few can be renamed in the NEW database tables
4. import now - again with phpMyAdmin - those tables you like to have in the new store also
> that would be e.g. customer, category, product, order etc. tables
>> DO NOT IMPORT THE settings table content!
5. copy the images from the old store into the new
6. install those additional extensions only you will need in the new store
7. install the custom theme [optional]
Basically your work is done with these steps.
Open the new store (front- & backend or backend only), and check of all data does exist.
Check the new settings and define them as you need.
This whole process my need 2,3 hours (a beginner may need a bit longer), but you can be ensure that the new store will run from the beginning.
8. If the new store is installed on the same server as the old store is (but separate folder!), reroute the address in your server configuration tool (CPanel, Plesk, etc.) to the folder of the new store
9. now when the new store works as expected, rename the .htaccess.txt to .htaccess
10. enable in the backend the SEO-URLs
Done.
No need to hire someone, pay money for some services, let other (unknown) people on the server.
In the (rare) case you have troubles, come back to this forum and ask.
OpenCart SEO Services
http://tomeda.bg
No problem, you can contact me (here via PM or my website) whenever you need help.
Full Stack Web Developer :: Dedicated OpenCart Development & Support DACH Region
Contact for Custom Work / Fast Support.
What is there to view?
Comparing the database and the tables is a simple process:
1. check if there are new tables (compared with old database)
2. check if there are tables in the old version which does not exist anymore in the new (very rare)
3. check if there are new tables in the new version (happens sometimes, especially 2.x > 3.x)
4. check if there are renamed table names (e.g. old was oc_table 1 > new is table_2) (happens sometimes)
5. compare each table structure old <> new
6.1. if there are field names in the new renamed (but exists in the old table) > then rename
6.2 if a field structure has changed (e.g. was varchar(32) now is varchar(64) ) > does no matter
6.3. if a field structure has changed (e.g. from int(11) to text(255) ) > should not happen (and happened until now never)
If all that is done, you have 2 options after you have created the new database:
A. let the new tables as they are, TRUNCATE them AND import the old (adopted) tables
or
B. delete all tables in the new database and IMPORT the old (and adopted) tables
It could happen, that you have overseen a few things (e.g. forgot to convert/adopt a field) .. does no matter, the import function of phpMyAdmin will tell you quickly what's wrong > adopt that and try again.
That's it .. and about that you want to see a video ? ?
Important is always: keep at least one untouched backup (copy) of all in a safe place!
And do all work with phpMyAdmin (backups, imports, etc.).
Full Stack Web Developer :: Dedicated OpenCart Development & Support DACH Region
Contact for Custom Work / Fast Support.
Thank you OSworx, that's just what I needed!
I did have a strange issue.
I first imported the customers. You could see them neatly in phpMyAdmin, but not in Backend OC 3040.
After that, I manually cloned the customer group, group description, and IDs within phpMyAdmin.
And voilà, the customers were visible again.
I'm curious about what other issues I might encounter. Isn't there anyone who has a free/open-source script that does this for you in one go?
(Of course, I'm not going to let an online party process my database, you understand?)"
I did have a strange issue.
I first imported the customers. You could see them neatly in phpMyAdmin, but not in Backend OC 3040.
After that, I manually cloned the customer group, group description, and IDs within phpMyAdmin.
And voilà, the customers were visible again.
I'm curious about what other issues I might encounter. Isn't there anyone who has a free/open-source script that does this for you in one go?
(Of course, I'm not going to let an online party process my database, you understand?)"
The already existing and integrated update should make that job.
But unfortunetely, that process does not work as it should (and that since years).
Full Stack Web Developer :: Dedicated OpenCart Development & Support DACH Region
Contact for Custom Work / Fast Support.
Who is online
Users browsing this forum: No registered users and 7 guests
