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

Solved Akeebabackup: ErrNo #1062

More
5 years 5 months ago - 5 years 5 months ago #1 by Smirnov
Akeebabackup: ErrNo #1062 was created by Smirnov
Hello,
I have problems with the restoration of the site through akeebabackup.
If I use the old archive (1 month old) - everything is fine.
But if I use the new archive, I get this error:

ErrNo #1062
Duplicate entry 'blablablablabla' for key 'PRIMARY', etc.

I do not have new extensions on the website. Over the past month there have been updates to extensions only. Tell me please, is it possible that new version of Kunena brings these problems?

P. S. The problem is solved by the option Use REPLACE instead of INSERT . But the reason for this collision is unknown to me. Also, if you restore the site without using akeebackup, everything ends without problems.

P.P.S. Another solution . But this does not work for me.

Any ideas? Thank you to your answer.

Attachments:
Last edit: 5 years 5 months ago by Smirnov.

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

More
5 years 4 months ago #2 by rich
Replied by rich on topic Akeebabackup: ErrNo #1062
It seems, the problem is caused by the table *_jotcache. It's a very old topic, but maybe it explains your problem.
www.jotcomponents.net/forum/7-jotcache-o...-huge-database-table
The following user(s) said Thank You: Smirnov

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

More
5 years 4 months ago #3 by Smirnov
Replied by Smirnov on topic Akeebabackup: ErrNo #1062
Cool! Thanks, it really solves my problem:

3. Can I set Akeeba Backup to skip #__jotcache table when backing up?
Yes do it. #__jotcache table is useless in backup content.

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

Time to create page: 0.550 seconds