-
Notifications
You must be signed in to change notification settings - Fork 11
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
🚨 Read for issues when installed from Nextcloud App Store 💁 #66
Comments
Hello, your composer instructions are not up to date, see here for updates: https://getcomposer.org/download/ any updates on this plugin ? Thanks! |
Hi @f4grx! In upcoming changes1 composer (and instructions) should all be removed. The plugin install should "just work" with no other / manual steps needed. As far as updates go, work is underway to support the latest Nextcloud release (NC25). For progress, read along in #110. Footnotes
|
Unpinning this, as this should no longer be an issue. This ticket is only here as a reminder until everything is proven to be resolved. |
Hi, I'll have a try, thanks! |
If you are reading this you probably ran into some issues when trying to get things up and running.
First of all, thank you for trying out the Solid-Nextcloud plugin!
Next, we owe you an apology: In moving to the app store, there was an oversight which causes the plugin to not work.
The major problem is that the third-party dependencies are currently not added to the release. Because of this, things just don't work.
This is because the process has not yet been automated, and the step is sometimes missing from the manual process.
At the time of this writing, the workaround is to download
composer
and runcomposer install
manually. 😞Short Term Workaround
Permanent Fix
Once the package release has been automated (#64) a step to add the
vendor
directory can be added (#65) assuring this problem does not arise again.Until this has been resolved, this issue should be pinned, to draw attention to it.
I would like to thank @aakerbeere for bringin this problem to our attention.
The text was updated successfully, but these errors were encountered: