Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

Error when creating Asset Backup #26

Open
gdubois414 opened this issue Mar 6, 2020 · 5 comments
Open

Error when creating Asset Backup #26

gdubois414 opened this issue Mar 6, 2020 · 5 comments

Comments

@gdubois414
Copy link

I am trying to get the asset backup working, but I am receiving these errors in the logs:
Create a new volume backup (attempt: 1) - Error (time: 1.562s): Getting unknown property: craft\awss3\Volume::rootPath
yii\base\UnknownPropertyException: Getting unknown property: craft\awss3\Volume::rootPath

The database backup works fine, but not for assets. I have the AWS S3 plugin installed and tried to disable it while testing, but ended up getting different errors.

@timmyomahony
Copy link
Contributor

When you say you have the AWS S3 plugin installed, you mean you are hosting your assets on S3 and not the local volume? Unfortunately at the moment the plugin only supports having your assets on the local volume (i.e. disk). A few people have mentioned using other volume backends though so it sounds like it's something I should add compatibility for.

What errors are you getting when you have the S3 plugin disabled?

@gdubois414
Copy link
Author

I get this error: Create a new volume backup (attempt: 1) - Error (time: 1.017s): Getting unknown property: craft\volumes\MissingVolume::rootPath

The setup is a little wonky, but some volumes are on S3, and some aren't. I'm testing this on our site for a client. The client's website isn't set up on S3 yet, so maybe there won't be any issues when I install the plugin on their website.

@timmyomahony
Copy link
Contributor

Currently the the plugin fetches all volumes in the system and then tried to copy their path to a temporary directory to zip them:

https://github.com/weareferal/craft-env-sync/blob/master/src/services/SyncService.php#L95

This means that it will likely still cause an issue on your client site if any of your volumes are not stored locally on the server. It looks like the S3 volumes don't have a rootPath variables, as the path isn't on the server (it's on the remote S3 bucket).

This is something I need to add a solution for I think

@timmyomahony
Copy link
Contributor

I have another issue here to track it too:

#21

@timmyomahony
Copy link
Contributor

Just to follow up @gdubois414, I've since deprecated this plugin and released two new plugins to take its place:

I don't think it will directly address this issue yet, but hopefully I'll be able to get a fix there

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

No branches or pull requests

2 participants