Nextcloud 19 is near to release and the second release candidate for this version is here!
A lot of issues have been fixed after feature freeze and next week we will make available another release candidate. Nextcloud 19 is now a step closer!
Help us test Nextcloud 19 - RC2 is here
With the release candidate, weāre at a point where there are some open issues we want to address for final, but we canāt find any new issues anymore. So we need help!
Our internal testing has revealed problems, that now are resolved and we canāt find serious problems anymore. But Nextcloud is used in many more ways than we realistically can test: on all kinds of devices, using a crazy variety of web servers, PHP versions, databases and so on. Testing is not that simple!
Every piece in the stack below Nextcloud, from Linux kernels to PHP, webserver, caching server, database and so on ā they all can create problems that we have to work around. But then we have to know about those problems and that is where you all come in. Your help testing Nextcloud in YOUR environment the way you use it is valuable to us! Only then can we be sure it will work for you when we release the final Nextcloud 19!
So who is up for some testing and issue reporting?
Version 19 ājust worksā. Canāt wait to see what version 20 brings to the table.
As far as bugs go most of them have been ironed outā¦ not sure if we need a RC3. Might be best just to move it straight to release.
Iām not sure whatās going on with the pull request for 13397. Iād really appreciate file checksums being integrated for data integrity but it seems to have dropped off the radar for NC19.
Iām also not sure what the status is with implementing a command to remove previews from a S3 backend. Especially orphaned previews which seemed to happen in my initial testing prior (which are reported).
But otherwise as far as Iām concerned NC19 is ready.
I donāt know how internal tests exactly look like and consequently the following idea might be irrelevant, however, remembering the major release of NC 17 and NC 18 they had some severe issues which were only triggered by apps.
So a clean NC server was running perfectly fine, but
upgrading NC with the app āgroupfoldersā enabled (for example) was resulted in a white web page after the update and manual interaction via SSH were necessary
due to another enabled app, sharing files to internal users was not possible
with an unavailable federated share users were unable to access their NC home directory and could access their files only via favorites (if they had set favorites)
In many cases the temporary solution for such issues was to disable specific apps.
Therefor I would like to ask, if not already the case: could you maybe perform updates and tests with the most important/ most used of all the available apps enabled?
In case specific apps trigger issues, this could maybe be fixed before release or the information about that issue could be provided together with the release announcements in a form like: please disable the following apps beforehand to avoid the following issues.
I understand if someone says: āwell, go ahead and do that yourself!ā, but I donāt have the capacity right now and just hope that other people, who have, like the idea and are willing to check for such issues.
[PHP] Error: session_start(): A session had already been started - ignoring at /var/www/nextcloud/lib/private/Session/Internal.php#209
GET /logout?requesttoken=ynDvLSi0Tpqy7PJfGoy2RfUunDtyo%2FaNT2qtLGq2pPE%3D%ā¦%3D
from xxx.xxx.Xx.xxx at 2020-05-15T08:57:09+00:100:
This error is new for me. It appeared after installing the RC2. After every logout I see this error in the logs.
Ubuntu 20.04
Nginx 1.18.0
PHP-fpm 7.4.6
And if I try to change the nickname of āUserā (for exemple, āuser_bisā instead of āuserā), I have to press enter key to edit the nickname. If I click on the , nothing change. (Same behavior for email adress)
yes you can install an other NextCloud on the same machineā¦ For exemple, install NextCloud 18 in /var/www/nextcloud18 and 19 in /var/www/nextcloud19.
I think that its better to install beta version of nextcloud on another machine on local. You should not install Beta version for production, so you dont need a public installation of NC19.
There are some apps missing. So for those that rely on self-installed apps not bundled with NC itself, make sure that they do work fine on NC19 prior to scheduling the update. For me (sorted by priority), these apps do work fine on NC19: two factorā¦, nextbackup, group folder, polls, bookmarks, preview generator, rainloop. These work fine but they are ānot compatibleā: Impersonate (marked āofficialā, yet ānot compatibleā?!, two factor e-mail. These donāt work yet or are not marked compatible yet: group quota, onlyoffice (marked official but incompatible!?) community document server(!), external user authentication, checksums, occ web, ransomwareā¦ . Of course there are more apps, I only listed those that seem relevant to a wider audience.
I think of all these, the team should ensure that these are available when NC 19 gets released: impersonate, community document server, onlyoffice, external user authentication.
I installed 19. Unfortunately the system did not create the right database entries for contacts. I was not able to add any. The error message I got was something with import of contacts disabled because there was no address book. I manually had to add the system and the admin user to the oc_addressbooks table (compared it to my production environment). From there it seemed to work fine.
I always have a /var/www/testcloud installation on my machine, where I install the beta version. Of course you also need a separate data directory, and a dedicated vhost like testcloud.mydomain.com to let it run separately.
Itās a pity that there is no more information about new features. This is kind of essential for good testing. Well we can look for ourselves, checkout github issues, but that takes more time we could spend in more specific testing.
Please donāt forget about the apps. Many are community driven and need support to get updated and tested.
, nothing change. (Same behavior for email adress)
