Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue backing up wp-content #301

Open
AdamJSoftware opened this issue Feb 5, 2024 · 2 comments
Open

Issue backing up wp-content #301

AdamJSoftware opened this issue Feb 5, 2024 · 2 comments

Comments

@AdamJSoftware
Copy link

I am running wordpress inside a bitnami container. It seems that XCloner doesn't recognise wp-content (doesn't even show in the section where you can choose which folders to ignore). My guess is that bitnami uses a symbolic link to connect the wp-content folder and this confuses xcloner. Is this something that can be fixed?

@Nox-404
Copy link

Nox-404 commented Aug 23, 2024

Can confirm,
The lib used to read the filesystem doesn't support symlinks.

The plugin cannot backup bitnami's wp-content folder & wp-config.php file...

Local fs adapter initialization:
https://github.com/watchfulli/XCloner-Wordpress/blob/master/xcloner-backup-and-restore/lib/Xcloner_Filesystem.php#L84

Local fs adapter code:
https://github.com/thephpleague/flysystem/blob/3.x/src/Local/LocalFilesystemAdapter.php#L52-L60 - symlink handling flags
https://github.com/thephpleague/flysystem/blob/3.x/src/Local/LocalFilesystemAdapter.php#L217-L222 - symlink handling (skip or throw)

Symlink support has been denied:
thephpleague/flysystem#599

So either create a new local adapter supporting symlinks, or maybe allow to include other arbitrary folders (in that case /bitnami/wordpress/... alongside the wp root directory /opt/bitnami/wordpress/) ?

@Nox-404
Copy link

Nox-404 commented Aug 23, 2024

I managed to work around it using this command inside the container:
wp option add xcloner_start_path '/bitnami/wordpress'

Then I deactivated/activated the plugin and now it sees the mounted volume instead of wordpress root
(which shouldn't need backup anyway as it's in the container's image)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants