This happens when a directory exists with the same name as the downloaded file.
e.g. when your file is named my-backup.wpress and there is a folder /my-backup in the same directory the extraction is stopped since it would override the content in the /my-backup folder on extraction.
You could simply rename the .wpress file (e.g. from my-backup.wpress to my-backup-1.wpress) to workaround this.
The reverse direction (creating a .wpress file from a directory) is a bit more complicated.
Inside the .wpress file are stored some metadata (e.g. installed plugins, Wordpress version etc.) that are not available in a local file context.
When providing this metadata manually, it would be possible to create a .wpress file.
But this is out of scope for me since I currently have no time to extend the tool further.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This happens when a directory exists with the same name as the downloaded file.
e.g. when your file is named
my-backup.wpress
and there is a folder/my-backup
in the same directory the extraction is stopped since it would override the content in the/my-backup
folder on extraction.You could simply rename the
.wpress
file (e.g. frommy-backup.wpress
tomy-backup-1.wpress
) to workaround this.I can't thank you enough. This really helped me. Wish you all the best
Out of curiosity, is there any way to convert a regular file to a .wpress file?
The reverse direction (creating a .wpress file from a directory) is a bit more complicated.
Inside the .wpress file are stored some metadata (e.g. installed plugins, Wordpress version etc.) that are not available in a local file context.
When providing this metadata manually, it would be possible to create a .wpress file.
But this is out of scope for me since I currently have no time to extend the tool further.