Nextcloud 19

[nebulon]

I have revoked the release now just to avoid more people hitting that issue after manually updating. We can just wait for at least the next patch release to iron out the rough edges.

[jdaviescoates]

@nebulon wise move.

I note the release announcement says:

If you are on an existing Nextcloud, the updater will notify you of the new version once we make it available. We usually roll out gradually and often, especially if issues are found, only make the first minor release available to all users. If you don’t want to wait and upgrade sooner, version 19 is in the beta channel. You can enable the beta channel, refresh the page, then upgrade. After the upgrade you can go back to the stable channel and you’ll be notified when 19.0.1 is out!

Sounds to me like it might make sense to nearly always wait until the first minor release before pushing updates to Cloudron.

[d19dotca]

@oj I wouldn't make it red, because updates are often fixing many issues too and are usually fine to update a bit early, but a cautionary yellow/orange would do the trick. haha

[girish]

I have added a caution note for the next release (5.3)

[nebulon]

Since 19.0.1 is out, I was wondering if the db migration is fixed, however https://help.nextcloud.com/t/nc-19-document-not-editable-with-external-collabora-server-doctrine-dbal-exception-invalidfieldnameexception/83751 does not have any resolution, besides some manual hack. @necrevistonnezr do you have any more input on this?

[necrevistonnezr]

@nebulon No, not really. I haven’t tried the manual solution proposed there

[nebulon]

Since there is no update on the issue, we are rolling out the new app package slowly. If you hit any issues, please restore the the previous version and disable automatic updates for that app for the time being.

[jdaviescoates]

@nebulon sounds like this is just an issue for people using Collabora instead of OnlyOffice, right? So perhaps a warning somewhere that if you are using Collabora you might not want to update?

[adrw]

I recently updated to 19.0.1 and see in Settings that DB migrations aren't updated for some optional columns. Should I manually run those commands or should those be included in the Cloudron image?

[girish]

@adrw Not sure why that wasn't part of nextcloud migration but indeed you can run sudo -u www-data php -f /app/code/occ db:add-missing-columns and it should fix the problem. I have added this to the next release of our package.

[adrw]

@girish said in Nextcloud 19:

sudo -u www-data php -f /app/code/occ db:add-missing-columns

Perfect, that did the trick! No more warnings in Nextcloud Settings.