Cloudron Forum

@necrevistonnezr Yes, I knew this, which is why I didn't understand your comment about a rollback from a major version since we're not talking about that case here. Moreover, the bug has been present since version 29.0.8, the second-to-last update, which evidently didn't include just bug fixes or security patches. This is perhaps what they should avoid.

In any case, the intention of my post was to warn others like myself who don't want to receive calls from customers complaining about a bug after the latest update, and to thank the Cloudron team for checking updates before releasing them.

@necrevistonnezr Why are you talking about a major release? The last update I have on Cloudron is version 29.0.8, am I mistaken? Is version 30.0.0 already available?

Anyway, I understand your point but there are some bugs that make life difficult for users during intensive activities. Like the recent one of automatic logout every 30 minutes and this one, with many folders containing many files that need to be updated in sequence, is practically inconvenient.

I tried version 29.0.8, but I encountered an issue that significantly slows down operations: when closing a file, the list view scrolls to the first file. With long file lists, this is very inconvenient, especially if you are making sequential changes to documents.

I have seen that this has already been reported as a bug, and some users are experiencing it even in version 30.0.1.

https://github.com/nextcloud/server/issues/48545

I had to roll back to version 29.0.6 and will have to wait until this issue is resolved, perhaps in version 30.0.2 or whenever.

I am very grateful to the Cloudron team for waiting and testing before releasing an update.

This isn't the first time we've been stuck on a version due to usability issues, unable to update until the bug is fixed. For those who don't notice and update anyway, having to live with a bug for a long time until it's fixed is frustrating.

This is just a reflection to inform others of this issue.

What @necrevistonnezr says is totally appropriate. There are bugs, like in this case, that cannot wait for an update to be released but should be released as a priority. The dental clinic secretaries have been doing the swing (logout/login) for 2 weeks to register appointments. In the end, with this bug it is possible to continue working but, what would have happened if it completely prevented an operation, we went back to pen and paper? Although updates can be scheduled over the weekend to have time to test and possibly restore the old version, the real problems occur with normal use and, after adding data, it is not possible to go back. I therefore hope that Nexcloud understands that, in some cases, it is important to release emergency fix releases.

As I opened this post, I already indicated that I had opened an issue on GitHub, the one mentioned in the previous comment.

https://github.com/nextcloud/server/issues/45132#issuecomment-2098151745

Now, whoever applied the fix, which is hoped to be released in the next release, encountered this problem:

"for us #45093 did fix the auto logout error but Nextcloud Office / Collabora Code could not access the files any more, so we had to choose what’s more important, NC Office or a reliable Talk App.

A general question: Does the Maintenance and Release Schedule, in this case for 28.0.6 (2024-05-23) and 29.0.1 (2024-05-23), also apply to critical issues like that or are hotfixes rolled out via the Updater earlier?".

I don’t know if this can also cause problems with OnlyOffice. I believe that must be very careful when performing the update, at least try the operation of the main applications.

It's not a matter of plugins or browsers. New installation and incognito browser.

@girish Thank you! It's not regular, in some cases it happens during use. For example, in the clinic where downtime is rare, it happened 3 or 4 times to accounts even just switching from file to calendar. I did a new installation and I noticed that if the browser window is minimized, if I reopen it after a while it requires login.

After the latest update from 28.0.4 to 28.0.5, there’s an auto logout problem with or without activity.

I also tried to add these parameters

‘session_lifetime’ => 86400, ‘session_keepalive’ => true, ‘auto_logout’ => false,

in the config.php but nothing, the problem persists.

I reported this bug:

https://github.com/nextcloud/server/issues/45132

the response:

Please try to apply #45093. it is for 29, but the changes can be done for 28 as well until the backport is done.

https://github.com/nextcloud/server/pull/45093

Has anyone else encountered this problem?

Thank you.

no I am referring the path in the browser when you open a file or folder mydomain.com/apps/files/files/?dir=/

Hi, After the latest update (28.0.2), the file path is now app/files/files/ instead of the previous app/files/. Can you confirm if this new path is correct or if there is a problem with the update? I don’t have any malfunctions but it seems strange to me. Can you confirm if the new address is normal? Thank you.

Would be great!

Traccar v4.14!
It is a real pity that the inclusion of this script among those available in cloudron has been abandoned because it would promote the cloudron solution in other fields. Seeing the regularity of the updates, the team seems very operational, it is a project that has existed for several years now and, from the 2018 version present in the cloudron repository, it has made so many improvements so as to rank it among the best of the open source GPS tracking system. I hope to see it soon in the Cloudron store.

Fast solution for manage content by API.

https://strapi.io/