Exporting from WordPress site


#1

I have a WordPress website hosted by 1and1IONOS and the WO All-in-one migration plugin installed. I used this to export the site and it gave me a file xxxxxxxx.wpress. Local does not recognise anything that is not a .zip file so I compressed it into a .zip.
Local now says it can’t recognise the file and I should unpack it manually.

This does not seem right - what am I doing wrong?

Thanks

David


#2

If you can login to the site and install a different plugin, I’ve had the most luck with BackWPup: https://wordpress.org/plugins/backwpup/

This will give you a backup that is much more portable than the .wpress file.

If all you have is the .wpress file, then you might have to Google around to see if there is a way to extract it.

I found this help doc: https://wordpress.org/support/topic/how-to-open-exported-file-wpress/

It also looks like this utility might be able to unpack the wpress file: https://github.com/fifthsegment/Wpress-Extractor

Once that has been extracted, you can compress the .sql file along with the wp-content folder and use that to import into Local.

Hope that helps give you a direction to work on! If you have any other questions, just let me know!

– Ben


#3

Hi,

I already have a backup plugin installed but it creates about 5 files; the help doc was useless as it extracted the .wpress files but then there was nothing to do with the result. I could not copy the extracted files there was nothing on the site except the file names. So I went the Wpress-Extractor route and that seems to have worked and gave me a whole bunch of file but not one called wp-content. Anyway, I zipped the lot into a .zip file but Local could not use it. Here is an image of the directory I created with all the extracted stuff in it


#4

Hi I’m still stuck, not getting the wp-content file with the extract process as above?

Thanks
David


#5

Just from looking at it, it seems that the folders listed in that view and possibly including the index.php file should be placed in a wp-contents folder.


#6

THANK YOU!
I now have my site in Local, next figure out how to use it !
Cheers
David


#7

It appears I still have a problem - I can load & start the site and in ADMIN mode I can see and edit all the content BUT when I try to view a page or even ‘visit’ the site all I get is a blank white screen.
Am I missing a step or a component here?

Thanks

David


#8

Try adding define( 'WP_DEBUG', true ); to your wp-config.php file. Hopefully it will provide a bit more information.


#9

OK, here’s the result.
Totally blank screen except for

Warning: Use of undefined constant �WP_DEBUG� - assumed ‘�WP_DEBUG�’ (this will throw an Error in a future version of PHP) in /app/public/wp-config.php on line 21


#10

It may be that the single quote didn’t translate correctly from my phone.


#11

I changed the single quote - it doesn’t crash now but I still cannot view the site, blank screen. Where does the debug put any output?


#12

It should output to the screen. Without the actual files I’m not sure what else to do. I’ve never used the backup plugin or the extractor mentioned.


#13

Usually when there is a white screen on the front end, but you are still able to access the backend, that points to the theme causing issues.

You might try temporarily switching to one of the default WordPress themes to verify that the issue is with the theme you are working with.

As to the specifics of debugging this current theme – I would recommend taking a closer look at the Debugging article on the WordPress Codex: https://codex.wordpress.org/Debugging_in_WordPress

– Ben


#14

Possible but why fail under Local by Flywheel and not on the live site?

I’ll try to upload my zip file later


#15

Here’s a link to my zip file - any clues in there?

https://drive.google.com/file/d/1k240VeFzJYezdnAlTgc1ai89Xp6CH_4C/view?usp=sharing


#16

It appears as if you are referencing a child theme that doesn’t exist in your themes folder.

From the dashboard, go to Themes page and activate your BRMC11 theme.


#17

This topic was automatically closed 12 hours after the last reply. New replies are no longer allowed.