Updating Joomla site from V3 to V5 how to transfer hikashop to new site.

  • Posts: 33
  • Thank you received: 3
2 weeks 6 days ago #369132

-- HikaShop version -- : 5.1.5
-- Joomla version -- : 5.4.0
-- PHP version -- : 8.1.33
-- Browser(s) name and version -- : n/a
-- Error-message(debug-mod must be tuned on) -- : none

Hi,

The life site safka.co.nz is being updated from joomla v3 to v5.

This is being done on a dev site: internet4success.co.nz which I have updated to joomla v5
Both life and dev are using hikashop v5.1.5

Since life site is still receiving orders and customers - how do I go about copying hikashop from life to dev site?

I understand I need to:
1/ export "hikashop" tables from live site to dev site. Adjust the table prefix if needed.
2/ Copy images from life site to dev in the following folders:
images/com_hikashop/upload
and
media/com_hikashop/upload/safe
There is some confusion on these 2 folders as I get different information depending upon where I am looking.

Is this correct am I missing anything?

Thanks
Henk

Please Log in or Create an account to join the conversation.

  • Posts: 84692
  • Thank you received: 13776
  • MODERATOR
2 weeks 6 days ago #369138

Hi,

You need to check the "upload folder" and "upload secure folder" settings of the HikaShop configuration:
www.hikashop.com/support/documentation/5...nfig.html#main_files
These are the folders you need to migrate.
Since you can potentially change them in the configuration, I can't say for sure if the default ones you found in other threads are the ones you need to migrate on your website. So check the settings and migrate the folders in them accordingly.

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 3
2 weeks 5 hours ago #369210

Thanks,

Images sorted.

When exporting hikashop tables from live site and importing to dev site. I read somewhere existing hikashop tables need to be renamed.
Is this necessary or can i simply import the sql file with hikashop tables into the dev site to sync the hikashop databses?

Thanks
Henk

Please Log in or Create an account to join the conversation.

  • Posts: 84692
  • Thank you received: 13776
  • MODERATOR
2 weeks 1 hour ago #369212

Hi,

It depends.
In the Joomla configuration, you have a setting "table prefix" where you can configure some text to be prepended to the tables of the website. This also include the tables of HikaShop.
So, if both websites don't have the same table prefix configured, the tables of HikaShop won't have the same name in the database, thus requiring a renaming.
But if you configure your J5 website to use the same prefix as your J3 website, then you can export / import the tables of HikaShop without renaming.

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 3
1 week 6 hours ago #369291

Hi,

Thanks for that - I have confirmed that the live site and dev site databases are using the same prefix.

I managed to export a sql database of the hikashop tables from the live site - it is over 2G in size.
The size I guess if related to the approx 45K orders in the site, going back to 2012.

I believe this size is causing a number of issues:
1/ I need server techs to import file into the upgraded site, as I can not upload a sql file of that size.
2/ When they import the hikashop database file - they encounter an error:
ERROR 1064 (42000) at line 1592718: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ''a:1:{s:13:"0000_00000001";O:8:"stdClass":19:{s:11:"taxation_id";s:1:"...' at line 31
3/ As the file is so large I can not open it on a local computer to view in Notepad++ or Textpad 8
Some can not look at line 31.

Database Version on live site is: 11.4.9-MariaDB - reported by Joomla system info.
Database Version on Dev site is: mysqlnd 8.1.33 - reported by phpinfo

Would you know what is causing the error when importing hikashop tables - and how to rectify?

If I remove a few years worth of old orders - would this reduce the export hikashop table sizes dramatically?
What would be the best method of removing old orders?

Also there are 25K users in the tables - would it help to reduce these?
In the joomla users tables there are multiple "not - enabled" and "not - activated" is it save to delete all these?
If so what is the best way to do this?

Thanks
Henk

Please Log in or Create an account to join the conversation.

  • Posts: 84692
  • Thank you received: 13776
  • MODERATOR
6 days 21 hours ago #369296

Hi,

Instead of exporting all the tables in one file, you can select only some tables and export them. That way, you can do it in several steps so that each exported file is smaller.
stackoverflow.com/questions/30121003/how...tables-in-phpmyadmin
Also, in PHPMyAdmin, on the listing of tables, you can see the size of each table. So, for really big tables, you can export / import them one by one, and then for the small ones, you can do them all together. That way, if you have a problem with one of the files during the import, you'll be able to open it with notepad++ as it will be smaller.

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 3
4 days 14 hours ago #369350

Hi,

Thanks some useful suggestions, my main issue is the live site needs to continue while i prepare database sync between the two sites. I have very limited time to work through DB conversion - once we take shop offline.
Also new site is running a different version of mysql - and the only way I can find of updating DB is via running the site update via the php/mysql update. This seems to take care of DB changes.

To take you point re large tables. I will look at reducing table sizes as follows:
Email log:
There is no entry for records older than XX. If I add a duration eg. 30 days - how long before system deletes older logs?
I.e. what triggers this?
Can I totally empty the hikashop email log table in phpadmin safely?

Joomla users table Hikashop users table - there are a large number of disabled/unactivitated users in joomla users - can I safely remove these without affecting hikashop users?
Also a number of users with .ru email addresses some of these are also in hikashop users. Since site does not ship to Russia - can we delete these - will hikashop user DB update or should I delete these in hikashop also?

Orders: We can delete orders before 2017 - If I delete these orders via hikashop is this safe without causing issues for hikashop?

I'll look at other large tables and might have more questions on these.

Thanks
Henk

Please Log in or Create an account to join the conversation.

  • Posts: 84692
  • Thank you received: 13776
  • MODERATOR
4 days 4 hours ago #369354

Hi,

Email log:
There is no entry for records older than XX. If I add a duration eg. 30 days - how long before system deletes older logs?
I.e. what triggers this?

This is handled by the HikaShop Email history plugin. It has a setting for the number of days if you edit it via the Joomla plugins manager.
Each time an email is sent, the plugin will run a MySQL query to delete the entries older than that.

Can I totally empty the hikashop email log table in phpadmin safely?

Yes, that's not a problem. The table is there only for the Customers>Emails history menu so that you can check that the emails are properly being sent. You can even turn off the plugin if you don't need it.

Joomla users table Hikashop users table - there are a large number of disabled/unactivitated users in joomla users - can I safely remove these without affecting hikashop users?

If you delete a user via the Joomla user manager, the corresponding entry will be deleted automatically in hikashop_user.
If you clear the users of the users table of Joomla via PHPMyAdmin, you can click on the "check database" button of the HikaShop configuration page. It will update the link with the users in the user_cms_id column of the table.
Then, you could run a MySQL query in your PHPMyadmin to delete the entries in hikashop_user with a user_cms_id at 0. Note that this supposes that you don't have "guest checkout" activated. Guest users will have their user_cms_id at 0 because there is no Joomla user account for them.

Orders: We can delete orders before 2017 - If I delete these orders via hikashop is this safe without causing issues for hikashop?

If you do it via the interface of HikaShop in the backend, then no problem.
If you do it via PHPMyAdmin, note that you need to delete the entries in hikashop_order but also the corresponding entries in hikashop_order_product and hikashop_history.

Note that the problem is not necessarily with tables with a lot of entries but with tables with a lot of data. A small table could have millions of entries but only integers (numbers) and it could still be quite small. On the other hand, a table with a couple hundred entries filled with big texts / data could lead to a big size.
So, for example, the email log table can be a real issue because it stores the whole content of each email, but the users table normally shouldn't matter too much as it normally doesn't store much data for each user.

Please Log in or Create an account to join the conversation.

  • Posts: 33
  • Thank you received: 3
3 days 14 hours ago #369365

Thank you heaps for your reply.

I will look into this feedback.

I really appreciate your quick and clear responses.

Cheers
Henk

Please Log in or Create an account to join the conversation.

Time to create page: 0.075 seconds
Powered by Kunena Forum