Kunena 6.3.0 released

The Kunena team has announce the arrival of Kunena 6.3.0 [K 6.3.0] in stable which is now available for download as a native Joomla extension for J! 4.4.x/5.0.x/5.1.x. This version addresses most of the issues that were discovered in K 6.2 and issues discovered during the last development stages of K 6.3

Question Does update process from kunena 3.x to 4.0.x remove data from tables?

More
8 years 10 months ago #1 by joomlauser
Hello friends.
How to prevent losing data from kunena 3.x during update process into Kunena 4.x?
How to perform the update process without loosing data?
Is the database table structure of Kunena 4.x differ from Kunena 3.x?

Sometime ago I perform an update process of Kunena component by installing new version from Extension> Extension mamager> Upload & Install Joomla Extension.
What did I wrong?

Thank you in advance
Kind regards

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

More
8 years 10 months ago #2 by 810
Just make sure you have a backup, in case its going wrong.

But it should not remove data. The structure is the same, but few new columns.

You can use the updater (updates to K4.0.0) , or download Kunena 4.0.1, and use the joomla installer.

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

More
8 years 10 months ago #3 by sozzled

810 wrote: But it should not remove data. The structure is the same, but few new columns.

Is there a list somewhere of the new columns, please?

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

More
8 years 10 months ago #4 by 810
The following user(s) said Thank You: sozzled

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

More
8 years 10 months ago #5 by sozzled
Thanks. If I understand correctly, the following image shows a list of the main database differences between K 3.0. and K 4.0:



There are one or two minor differences in terms of data content (mostly to fix up some of the "problems" people were having with the "new" indicator), but these are not game changers as far anyone should be too concerned about. Very useful information to have both as a user and as a developer. :)
Attachments:

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

More
8 years 10 months ago #6 by joomlauser

810 wrote: Just make sure you have a backup, in case its going wrong.

But it should not remove data. The structure is the same, but few new columns.

You can use the updater (updates to K4.0.0) , or download Kunena 4.0.1, and use the joomla installer.


My updater shows Kunena 3.0.8
My version is 3.0.6.
Should I firstly update from 3.0.6 to 3.0.8 or can I update directly to 4.0.1?

Attachments:

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

More
8 years 10 months ago #7 by xillibit
It's normal because we haven't enabled yet the updater to show k4.0.1 when you have k3.0.8.

You can first update to k3.0.8 then make a backup and try with to update to k4.0.1

I don't provide support by PM, because this can be useful for someone else.

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

More
8 years 10 months ago - 8 years 10 months ago #8 by xillibit
I have updated the database.mwb file, so you can look with MySQL workbench the Kunena database schema : github.com/Kunena/Kunena-Forum/tree/develop/docs

I don't provide support by PM, because this can be useful for someone else.
Last edit: 8 years 10 months ago by xillibit.

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

More
8 years 10 months ago - 8 years 10 months ago #9 by sozzled

xillibit wrote: I have updated the database.mwb file, so you can look with MySQL workbench the Kunena database schema : github.com/Kunena/Kunena-Forum/tree/develop/docs

I am sorry, xillibit, but I do not understand this documentation and I do not know how to use it.

I asked before for a list of the database changes that have taken place since K 3.0.8. In msg #5 I tried to show these changes in a simple way. Did I understand the changes correctly?
Last edit: 8 years 10 months ago by sozzled.

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

Time to create page: 0.602 seconds