Serious Problem with WordPress 6.0.1 Backup Plugins
-
I have a Windows 10 64 bit Home edition box with Mozilla Firefox version 103.0.2.
Having tried to download and setup the latest version of WordPress, 6.0.1, from the website, to use it with Bitnami XAMPP, I have noticed the new (beta version) Theme Editor. Now, I have no major problem because I have kept a backup of the previous version of WordPress, which is working as desired.
The problem has been that with this latest version, it gets to the point where I need to load in my archive file backup of my website project. I have been using free WPvivid, and I have had 31 folder directories holding all the incremental backups of my project from the beginning.
I have found that the backups can’t load in and restore my latest backup, which I need to. The project has been utilising the Twenty-Twenty-One theme. It seems the beta version of the Theme editor has made WordPress incompatible with any unknown backup import and/or restore plugins, since the beta Theme Editor presently leaves a problem between Themes and free or pay backup plugins.
My plugin is free WPvivid. But there are other ones, and the beta Theme Editor, or the full (coming) version of the Theme editor need to be more compatible with backup plugins. Because if it is not, there will be people with multiple backed up projects and multiple incremental version chains of backups, who cannot successfully load them into the latest version of WordPress, anymore. The backup plugins and the backups themselves are no longer compatible enough to work with latest WordPress any more.
This situation has to be addressed, certainly with the relevant backup plugins that are in the (add new plugin) WordPress plugins database. Otherwise, people can’t use the latest version of WordPress, will have stick with a slightly older version of WordPress, or will have to turn to
https://en-au.ww.wp.xz.cn/download/releases/
This situation can’t be left forever, because eventually the plugins may evolve as WordPress evolves, but the backup file formats may not, which in serious terms can’t be left to happen.
The latest version of WordPress needs to be fixed so that it can continue to successfully upload and restore previous website backups, such as those made with the previous version of WordPress and the free WPvivid backup plugin, and the way that it reads and writes information. I look forward to reading any replies to this thread!
-
There’s nothing inherently broken in WordPress 6.0.1 with respect to backing up a site. Last week alone, I used different backup plugins to migrate over a dozen client sites… all without a hitch. (OK, there were some hitches, but these were all due to various hosting limitations that had nothing to do with WordPress or even the backup plugins I used.)
The WPVivid plugin’s author has even tested the latest version of their plugin with WordPress 6.0.1, and has proclaimed support for it: see the “Tested Up To” in the right side of the plugin’s listing: https://ww.wp.xz.cn/plugins/wpvivid-backuprestore/
If the WPVivid plugin isn’t working for you, kindly post in the plugin’s support forum, so its developer can help you fix it. But I’ll recommend you focus on describing the specific problem you’re facing, including any error messages you are seeing. Here’s the plugin’s support page: https://ww.wp.xz.cn/support/plugin/wpvivid-backuprestore/
If any other plugin is not working for you, please find the plugin at ww.wp.xz.cn/plugins, click the “Support” tab, and make a post in that plugin’s support forum for the author to assist you. Again, for the author to be able to help you, you need to describe in detail the specific error you’re seeing, including any error message. A screenshot works wonders when it comes to tech support.
Good luck!
I have been finding that in terms of the different features in version 6.0.1 of WordPress, the previous versions of it available from the archive site, at:
https://en-au.ww.wp.xz.cn/download/releases/
previous versions, including 6.0.0, and 5.9.X. insist on the user updating them to version 6.0.1. So strongly is this insistence, in fact, that it is not possible to use 6.0.0 or 5.9.X versions as they were, without not only the option, but a total compulsion, to update to version 6.0.1.
Now it would be easiest for me to use 6.0.0, or 5.9.X if I had to, but they cannot be used without updating them to version 6.0.1, with the beta Themes editor feature.
Is there some way for WordPress to stop this requisite broadcasting of older, earlier versions of WordPress to 6.0.1, because I need to utilise an earlier version of WordPress, without updating it, which is presently impossible. Can this issue either be change with the mentioned archive versions of WordPress (6.0.0 or 5.9.X), or can those primary responsible for WordPress please stop internet broadcast this compulsion to update, so that I can utilise older WordPress and eat least have the active option to not upgrade, and keep using them, please?
On the issue of my WPVivid restores not working, I would be willing to submit a copy of my website project to you via WeTransfer or Smash, so that you can have a look at what I have got. I am finding that the restore crashes with no real error message, or that the link in the image on my Splash page doesn’t go on to my Main area. If you or others over there can either test or fix either my archive files or something in latest WPvivid with 6.0.1 WordPress, I would be very happy about that! If possible, could someone reply here with a live email address so that I can use WeTransfer or Smash to get my WPvivid archives over there, to be scrutinised?
On updates:
WordPress has had automatic updates as far back as 3.7, so nothing new here with respect to 6.0.1. And these automatic updates can be disabled completely or selectively: https://ww.wp.xz.cn/support/article/configuring-automatic-background-updates/
Also of note: the Site Editor (Beta) feature came with 6.0, not 6.0.1. See screenshot below from a site running WordPress 6.0 (with a prompt to upgrade to 6.0.1) and featuring the Site Editor (Beta) feature already.
And I’m unable to follow your narrative of how this Site Editor (Beta) feature has anything to do with backup plugins.
Is there some way for WordPress to stop this requisite broadcasting of older, earlier versions of WordPress to 6.0.1, because I need to utilise an earlier version of WordPress, without updating it, which is presently impossible.
Staying with an older version is certainly possible: see my comment and link above.
On the issue of my WPVivid restores not working and asking for help outside the forums…
Please note that all solicitations and offers to help, even for free, are strictly forbidden by the forum rules: https://ww.wp.xz.cn/support/guidelines/#the-bad-stuff.
I am finding that the restore crashes with no real error message,
You may not see error messages on your screen, but the error is very likely logged somewhere on the server. So check your BitNami/XAMPP server’s logs. See also: Debugging in WordPress: https://ww.wp.xz.cn/support/article/debugging-in-wordpress/
Whats more, the plugin’s develer may very well what’s going on here, that’s why I asked you to post in the plugin’s own support forum. But it seems you’ve not done that yet. 😀
The topic ‘Serious Problem with WordPress 6.0.1 Backup Plugins’ is closed to new replies.