Good things need time: The second beta of Pico CMS for Nextcloud is out now!
Pico CMS for Nextcloud v1.0.0-beta.2
utilizes Pico v2.1.0-beta.1
(bringing Pico 2.1 in beta was the reason why this took longer than expected initially).
Again we’re looking for testers, feedback is highly appreciated I’m assuming Pico CMS for Nextcloud to be stable and ready for production, the second beta is just a way to make things bullet-proof. Pico CMS for Nextcloud v1.0.0 will be released on 24th November 2019 (unless bad things happen in the next two weeks, but I doubt that).
If you’re a developer, we’re also looking forward to your code review - you can find all changes in nextcloud/cms_pico
#77
If you find any issues or want to give feedback, you can either open a new Issue on GitHub , reply to nextcloud/cms_pico
#77 or simply reply to this thread. If you wanna do a code review, please use GitHub’s review feature from within nextcloud/cms_pico
#77.
We’re looking forward to your feedback and reviews! Thank you!
Download
You can download Pico CMS for Nextcloud’s release archive from here:
cms_pico-1.0.0-beta.2.tar.gz
(Click here to download!)
Heads up! If you’re currently running Pico CMS for Nextcloud v1.0.0-beta.1
you MUST check the “I’m running v1.0.0-beta.1
right now” section below before upgrading. This is also true when upgrading to v1.0.0
later - you’ll break your installation otherwise!
Installation and Upgrading
Just refer to the “Installation and Upgrading” section above for install instructions, you just have to use the tarball of the second beta instead
However, if you’re currently running v1.0.0-beta.1
, you MUST check the section below first!
I’m running v1.0.0-beta.1
right now
There’s an issue with the first beta that will make the upgrade fail - no matter to which version you upgrade (i.e. doesn’t matter whether v1.0.0-beta.2
or v1.0.0
). Even worse, if you’re currently running v1.0.0-beta.1
, a later stable release of Pico CMS for Nextcloud won’t show up in your Nextcloud.
All this happens because v1.0.0-beta.1
is falsely identifying itself as v1.0.0
. This is impossible to fix without upgrading to an intermediate version - like v1.0.0-beta.2
. For this reason you MUST upgrade to v1.0.0-beta.2
first Naturally we added a security measure to the build script to prevent stupid errors like this in the future…
Okay, now you know what’s going on, head over to the upgrade instructions.