Support

Akeeba Backup for WordPress

#39785 Updating manual to 8.1.0 has sometimes issues

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

WordPress version
6.3.2
PHP version
8.0.30
Akeeba Backup version
8.1.0

Latest post by nicholas on Friday, 10 November 2023 01:03 CST

alex.preyer

I started to manual update my sites to Akeeba 8.1.0

On some sites I have an issue. The reason are, as far as I seen, old site entries in the ak_stats table. To explain, for my Wordpress developing sites, I use a Site template where Akeeba is already installed. It seems that websites I created years ago have Akeeba stats from the devolping site in the table and this makes problems.

When entering the Akeeba Backend after manuall copy the files to wp-content/plugins/akkebabackupwp an information appears (see attached screenshot).

When clicking on "More information and Migration" an error appears:

## 1064 Application Error

RuntimeException: 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 ')' at line 3 SQL=UPDATE `wpvmp_ak_stats` SET `filesexist` = 0 WHERE `id` IN ()

Β 

In the server log I see:

.974499 [NOTICE] [26071] [T0] [77.24.123.77:56802-H3:86D3BF-496#APVH_architekturbuero-kunert.com:443] [STDERR] PHP Warning: file_exists(): open_basedir restriction in effect. File(/var/www/vhosts/preyer.info/site-kunert.preyer.info-20190924-181228cest.jpa) is not within the allowed path(s): (/var/www/vhosts/architekturbuero-kunert.com/:/tmp/) in /var/www/vhosts/architekturbuero-kunert.com/httpdocs/wp-content/plugins/akeebabackupwp/helpers/Solo/Model/Migreight.php on line 133\n

/var/www/vhosts/preyer.info/site-kunert.preyer.info-20190924-181228cest.jpa is an entry where the site was in developing state.

Β 

I tried to resolve this with deleting these entries in the database. But the message box in Akeeba still appears.

Β 

Β 

alex.preyer

Sorry, forgot the screenshot.

nicholas
Akeeba Staff
Manager

There is a SQL error after finishing the migration of backup archives when there are more than a hundred or so of them for which the files no longer exist but are not already marked as such.

I have addressed this in this dev release: https://www.akeeba.com/download/backupwp-dev/8-1-1-dev202311100642-reve7c494a8.html Can you please install it, run the migration with it and let me know if it worked for you?

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

alex.preyer

I tried it on two sites where I had the issue. After pressing the "Migration" button it looks good on both websites. So it is no problem that such old entries in the database? Or should it be cleaned?

nicholas
Akeeba Staff
Manager

No problem with the old entries. The error you got was at the end of the code which was handling these old entries, when it ran out of old entries to take care of. The work was already done at this point. What I did now was to tell it "okay, the work is done, go away now" so the final instruction, mark the migration complete, could finally run.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!