Plugin Contributor
bcrodua
(@bcrodua)
Hi,
Can you please confirm that you have the latest version of UpdraftPlus installed? If yes, can you try to re-install and see if you get the same issue? You will not lose your backups in the process.
Thanks,
Bryle
I’m getting this error… I have UpdraftPlus Version 2.23.7.26, and WordPress 6.2.2
-
This reply was modified 2 years, 9 months ago by
mywebmaestro.
@werkc @mywebmaestro can you both post your backups logs from the backup/restore tabs using a tools such as pastebin.com
If possible, could you also post your php error logs
(you can obscure your site name or replace it with something like mysite using a find a replace tool if you like, it is not essential for us to know your site url if you do not want us to)
Same error here, under PHP 8.2.8:
PHP event: code E_DEPRECATED: Creation of dynamic property Crypt_Rijndael::$key_size is deprecated (line 279, wp-content/plugins/updraftplus/vendor/phpseclib/phpseclib/phpseclib/Crypt/Rijndael.php)
There are absolutely no further errors on the webserver log.
And the Pastebin (redacted) for the UpdraftPlus logs is here: https://pastebin.com/Z7vJA1RE
It’s a very simple fix, really. PHP 8.2 deprecated support of creating dynamic properties: https://www.php.net/manual/en/migration82.deprecated.php
But as you can see there are plenty of alternatives to choose from, and aye, they will also work under PHP 8.0/8.1.
Happy bug hunting! 🙂
Further feedback…
You’re using the popular phpseclib, which is fine. But you’re using the 2008 version, which had PHP 4 and 5 in mind. You should really, really, really update that library, it’s 15 years old!
phpseclib, of course, continues to be dutifully maintained: https://github.com/phpseclib/phpseclib/ (last submission was last week, at the date of writing this). I’ve checked the new code for setKey(), which is the function that throws the deprecation error: as expected, the contemporary code is quite different from the 2008 one, and should work flawlessly.
There you go 🙂 You just need to make sure that the rest of your code is compatible with the updated library; if yes, this is a 5-minute-fix (at worst!) to make everybody happy again 🙂
(Fortunately, the deprecation error seems not to affect the backups to Dropbox themselves)
Hi,
Thank you for the report and investigation. I have added a ticket on our internal development board for our development team to look at this.
Thanks for looking into it, @vupdraft 🙂 I see that this change made it into version 1.23.8, so everything should be fine now!