Nextcloud 19

[necrevistonnezr]

Thanks for the detailed explanation - but in line editing of documents doesn't work for me.

I have set up the Cloudron Collabora package, installed Collabora Online Nextcloud app and pointed to the Cloudron Collobora url. I get a "green light" i.e. it can connect:

However, if I click on a odt document for example to edit, it tells me

Collabora Online Development Edition could not be loaded

even though the Collabora Online Nextcloud app is not pointed to the Collabora Online Development Edition but to the separata Cloudron Collabora installation.

The logs in the admin account of Nextcloud are filled with things like this:

Doctrine\DBAL\Exception\InvalidFieldNameException: An exception occurred while executing 'INSERT INTO "oc_richdocuments_wopi"("fileid","owner_uid","editor_uid","version","canwrite","server_host","token","expiry","template_destination","hide_download","direct","is_remote_token","template_id") VALUES(?,?,?,?,?,?,?,?,?,?,?,?,?)' with params [708914, "username", "username", 0, true, "https:\/\/nc.MYROOTDOMAIN.tld\/", "Xx1zy2tgxFRDxPiUWUbvFQ4zPgreLEip", 1591344464, 0, false, false, false, 0]: SQLSTATE[42703]: Undefined column: 7 ERROR: column "template_id" of relation "oc_richdocuments_wopi" does not exist LINE 1: ...ation","hide_download","direct","is_remote_token","template_... ^

and

ResourceLocator can not find a web root (root: /app/data/apps/spreed, file: css/spreed/e6bc-1805-merged-files.css?v=184d440645b8bb9e5d3642f9160f9b28, webRoot: , throw: true)

[nebulon]

The resource locator error in the logs should be irrelevant for this issue and it something which is there since a long time. We have to investigate again if it is finally possible to make Nextcloud not complain here.

Regarding the other issue about the database error, this looks like some db migration went wrong during enabling that connector app. Can you maybe remove the connector app and readd it?

[necrevistonnezr]

@nebulon said in Nextcloud 19:

Regarding the other issue about the database error, this looks like some db migration went wrong during enabling that connector app. Can you maybe remove the connector app and readd it?

Disabled and then removed app. Added it again, checked settings, logged out as admin and logged in as user, Collabora still doesn't load.

Admin log still:

Doctrine\DBAL\Exception\InvalidFieldNameException: An exception occurred while executing 'INSERT INTO "oc_richdocuments_wopi"("fileid","owner_uid","editor_uid","version","canwrite","server_host","token","expiry","template_destination","hide_download","direct","is_remote_token","template_id") VALUES(?,?,?,?,?,?,?,?,?,?,?,?,?)' with params [80482, "user", "user", 0, true, "https://nc.domain.tld/", "X9YFmDsPRZMIvvuejigppXn7yuOQTzaR", 1591346839, 0, false, false, false, 0]: SQLSTATE[42703]: Undefined column: 7 ERROR: column "template_id" of relation "oc_richdocuments_wopi" does not exist LINE 1: ...ation","hide_download","direct","is_remote_token","template_... ^

[nebulon]

I cannot really reproduce this, maybe you can report this upstream with the connector app and maybe the authors know better what is missing or went wrong in your instance.

[necrevistonnezr]

@necrevistonnezr said in Nextcloud 19:

I noted that the "Community Document Server" (based on Only Office) as part of Nextcloud Hub is marked as "not-compatible" with NC 19.

And this https://www.collaboraoffice.com/press-releases/collabora-online-as-default-in-nextcloud-hub/ states that Collabora will be the standard for Nextcloud Hub starting with NC 19?!

BTW the reason for the switch could be https://github.com/ONLYOFFICE/DocumentServer/issues/805

[necrevistonnezr]

@nebulon said in Nextcloud 19:

I cannot really reproduce this, maybe you can report this upstream with the connector app and maybe the authors know better what is missing or went wrong in your instance.

Reported here: https://help.nextcloud.com/t/nc-19-document-not-editable-with-external-collabora-server-doctrine-dbal-exception-invalidfieldnameexception/83751

[oj]

Hi:

I faced an issue while trying to use the Cloudron LDAP with a fresh install of Nextcloud 19.

If "access control" is either set to "all Cloudron users", or to a specific "Cloudron group" or to a specific "Cloudron user" while installing Nextcloud 19, the list of relevant Cloudron users keeps on being added repeatedly - roughly once every second when seen under the "Everyone" tab in the "Users" section on Nextcloud.

Since my fresh install was only for demo purposes, I have solved my immediate problem by delegating "access control" to Nextcloud.

I am reporting this odd behaviour so that the Cloudron-Nextcloud LDAP settings can be fixed, if required.

[YurkshireLad]

I don't want to be a party pooper, but I would hold off using Nextcloud 19 until the next point release. I hit some problems, one of which they've already fixed. The worst one was duplicate pictures in the Photos app. (Edit for details)

I deleted all the example pictures and uploaded one via the Android app (which is also broken). If I clicked the picture in NextCloud, it was displayed full screen. If I closed it, the photo was duplicated in the photo gallery.

Deleting documents in the Android app is impossible as selection is completely broken at the moment.

[girish]

There's also this strange bug that in the user listing the users keep re-appearing like infinite scroll...

edit: oh this is exactly what @oj has reported.

@oj this is a bug in nextcloud and also it's a display issue, it's harmless otherwise.

[oj]

@girish Your new "UPDATE" button is in an "inviting green" color... asking to be pushed.

What if it was switched to a "scarry red" with a scary message like "You sure you cannot wait for a few days for the devs to push you a nice, stable release of this app as an autoupdate??? By proceeding, you risk ruining your hitherto trouble-free app updates experience on Cloudron!!!"

[girish]

@oj That's a good idea. Currently, we don't have a way to distinguish between automatic stable update vs manual-possibly-unstable update. Seems worth adding.

[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?