Well I am not that familiar with Wordpress and certainly not your plugin. But I know usually Wordpress backups are basically in two parts. Wordpress system and the database. I would guess most of these folders are the Wordpress system and would need to be copied into a working system (but not a live system). I would start looking at the database.sql file and the contents of the backups-jmr95 folder
You should not really paste anything into a db, the folders would be part of Wordpress. You need to create a db and use the sql to import data into it. Copying and pasting files into a db can break it and probably will
I would start with a fresh wordpress install and look first at importing your sql into the db it creates. You can deal with plugins etc later. I would concentrate on getting the data back into WP first
You can do this with phpmyadmin and use the same to view the database structure and access the contents using the parameters in wp-config
I’m retired mate, got to keep my wife and dog happy, in that order usually but apart from that it’s mostly Nat Geo and The Food Network!
If there is any way I can get a look at any of your files I may be able to help more. I’m OK to help out but my times are different since I live in Egypt, internet is ‘temperamental’ but I did start to write my own backup restore for Wordpress in PHP so I’m familiar with the concepts.
One thing you must understand is generally speaking you literally can’t just paste a file into a MtSQL / MariaDB database. you cant even simply add another database or table that way. Everything needs to be imported using SQL or created via something like phpmyadmin.
Start with a new ‘expendable’ Wordpress setup, try and identify the theme and any plugins that were being used and add them. Then look at the SQL files you have and then try importing the SQL using phpmyadmin
If you have any other questions just ask, I’ll reply and help when I can
Do you understand how Wordpress actually works, examining the database, viewing the different tables etc?
That is very kind of you. I am based in Sicily (still North Africa) we are not that far apart.
No worries I wasn’t really expecting to solve that so easily.
I’ve never dabbled with databases, SQL and the likes but I do understand the principles. I’ll be proceeding one step at a time.
How can I show you my files?
After a flash check
Phpmyadmin can import compressed (gzip, zip) or uncompressed files. I guess I have to understand what to do with the .wpress file. I guess it is somehow compressed.
As said earlier it doesn’t seem to be a clone of a entire database.
Also, I read phpmyadmin may have some problem with large files, is 2.4 GB considered as large?
The folder plugin and themes lists most of what was installed. Most of them are free, the theme unfortunately is not. Do I have to buy it back?
I think the problem regarding large files is a PHP limitation and I think it can be overwritten in the config on the server if you have access.
I don’t know about themes but I believe some plugins modify the database so depending on the sql you may end up trying to update a table that does not exist. But no point in buying the theme at this stage unless you really need to.
I really think that your best approach is to extract any sql and see what it actually consists of, if it creates tables and if so which ones. But once you have valid sql you actually have useable data to play with… and yea, with files of that size I’m not really going to be able to view them easily but start by unravelling the sql to see what you are dealing with.
The other problem you may hit is that if the backup was created by a plugin, it may not be in raw sql format and you may need the plugin to extract the data again, so as satishinnovstudio said you may need to get hold of all in one wp migrate
If this is the case, I found out that some previous version of All-in-One WP allows to import up to 512 MB (the current release 40 MB only). Maybe is possible to split the backup in several parts or prioritize the essential?
@kerry14 have a look at this, I had overlooked it before, but after your explanation I went back checking all sources and that seems to be close to what I need. They indeed say
" rename the folder to “wp-content ”, delete the one from the new WordPress you install, and then just move it there. Lastly, you need to clean the new WordPress database and import the SQL you got from the “wpress " archive.”
Well if you look at the code there are comments at the beginning which may assist -
then the code is in a number of sections, each of which deletes a table if it already exists and then creates a new one -
DROP TABLE IF EXISTS `SERVMASK_PREFIX_acfw_store_credits`;
CREATE TABLE `SERVMASK_PREFIX_acfw_store_credits` (
Then the SQL continues by inserting data into the newly created empty table row by row -
INSERT INTO `SERVMASK_PREFIX_acfw_store_credits` VALUES (1,1,'2022-03-28 05:39:43','increase','admin_increase','50',6,'');
The ‘SERVMASK_PREFIX’ is probably a universal prefix that gets applied to all tables. Wordpress usually gives you the option to ad a prefix to all tables or it could have been defined elsewhere, maybe in a plugin.
I notice further down in the SQL there are a number of tables containing within their name - aioseo
A google search reveals the above link which is an SEO plugin for Wordpress, so that certainly looks like this plugin was installed.
This would be the basis of your process, import the tables into your database and find out what each table is for. You may also need to reinstall your Wordpress with the same table prefix so it finds the tables.
I tried importing the entire SQL but got a number of errors, so I tried breaking the SQL into individual create/insert sections. Some worked and created tables and rows, other gave errors.
So really now its detective work, importing what you can, viewing data, investigating errors and understanding what data you have and what it is used for.
I do think however that it is going to be a very long job importing the data, deciphering what the data is and what plugins and settings are needed to access it and you will basically be trying to create a Wordpress install bit by bit. It may be easier to bite the bullet and by the plugin, but if you like solving problems you have many interesting and fun filled evenings ahead
Can you also let me know your opinion about the aforementioned guide? In short they say to switch wp-content folder with the one inside the backup and then to import the database. It seen too easy, what’s the catch?
By the way I have already extracted the .wpress backup file, here is what it’s inside:
I tried importing into an empty MariaDB / MySQL database (the same as Wordpress uses) but the database was created, and the import performed purely using phpmyadmin. So completely independent of Wordpress or any Plugins. It was purely an error updating a database with that SQL. So purely a database / SQL error possibly due to version or database settings. Possibly may have more luck using a working (but expendable) Wordpress install - but these were not ‘Wordpress’ or ‘Plugin’ errors on my attempt.
Those folders look very much like they belong in the Wordpress wp-contents folder. but the database sql and possibly the contents of backups-Jmr95 would look like good candidates for database data.
I did what they said out of curiosity. IT WORKED!!!
Swapping the wp_content was easy, for the database there are mathematical chances I messed up something.
After the database swapping I logged in but as soon as I did I was prompted to chose a language and register a new user as if it was a fresh installation. Done that I could access the dashboard where I found the list of all backed up plugins and themes (taken likely from wp_content) and nothing else.
What I did with the database was emptying the existing database folder and replace the content by importing the .sql file from the backed up site. One thing I immediately noticed is the imported database tabs prefix is different than the standard ( servmask_prefix_… rather than wp_…), could this be one issue?
I tried to change prefix in wp-config.php but that gives PR_END_OF_FILE_ERROR. I notice it tries to connect to the original domain instead of http://localhost/wordpress/wp-login.php
@kerry14 do you have any suggestion? I know, I opened the Pandora box…
I really admire who everyone is trying to find a way for the user. Here are my suggestions for you, hope could help. As you created a file by All-in-One WP Migration plugin you can restore your data backup by following a few steps:
By using the same plugin you can import the backup file but for that you have increased the upload limit to 2.4 GB. Try this by editing your php.ini file. Use a tool that can extract the backfile into a folder then upload your site via Control Panel. Also merge database.sql files into your site’s database using a tool like phpmyadmin etc. Hey and you can also try WPvivid Backup Pro3, simply install this plugin on your site and then upload the backup file.