Latest updates for Hub 6 and 7, end of life for Hub 4

Originally published at: Latest updates for Hub 6 and 7, end of life for Hub 4 - Nextcloud

Please update to a new version to keep your data safe!

We strongly recommend you to update your Hub to version : 28.0.4, 27.1.8 or 26.0.13. The maintenance updates include important bug fixes, stability and security upgrades. It is a quick and safe process, as always!

What’s new

The updates bring several fixes and performance improvements in all supported versions of Nextcloud Hub. Version 26 meets its end of life and will no longer receive the updates. The Nextcloud desktop client has also been updated to version 3.12.3, and we highly recommend updating to this version due to important bug fixes.

Find the full changelog on our website, or read the update summaries below.

Version 26.0.13

This is the final update before the end of life of version 26. The update involves a mixture of enhancements and fixes across various components. Notable enhancements include:

  • Collaboration, MailPlugin: Protect access to a potentially missing array component by ??
  • Docs(config.sample.php): Warn that updatedirectory will break updates if set to a value within the installation folder
  • Feat(share): save date and time for expiration
  • Fix: Avoid clear cache with prefix
  • Fix(api): Ignore “parsed” link and icon URLs when deleting
  • Fix(caldav): add EXDATE and EXRULE to confidential object
  • Fix(config): Make sure user keys are strings
  • Fix(mail): Use parsed action label in email notification
  • Fix(settings): posix_getpwuid can return false which should not be accessed like an array
  • Fix(UpdateNotifications): Handle numeric user IDs

Note: There will be no more releases of Nextcloud Hub 4 (26.x.x and older). Upgrade to Nextcloud Enterprise to continue to get security and stability updates or move to Nextcloud Hub 6 or Hub 7. Don’t forget that running web-facing software without regular updates is risky. Please stay up to date with Nextcloud releases of both the server and its apps, for the safety of your data! Customers can always count on our upgrade support if needed.

Version 27.1.8

Recent updates encompass various improvements and fixes across different modules. Key enhancements affecting security, data integrity, user experience and overall performance include:

  • Add recursive detection/prevention
  • Docs(config.sample.php): Warn that updatedirectory will break updates if set to a value within the installation folder
  • Fix: Avoid race condition that may initialize a document twice on the clients
  • Fix: No password set for new mail shares
  • Use the proper path to check if a file needs to be copied/moved to the actual target storage
  • Fix: Allow to disable multipart copy on external s3 storage
  • Fix: Avoid clear cache with prefix
  • Fix: Fetch custom app store URL without internet connection
  • Fix: Don’t return null for SharedStorage::getWrapperStorage with share recursion
  • Fix: Ensure nested mount points are handled in the correct order

Version 28.0.4

The update includes multiple enhancements. Among those, the following focus on fixing issues related to security, data integrity, and functionality, ensuring smooth operation and improved user experience:

  • Add recursive detection/prevention
  • Fix: Avoid clear cache with prefix
  • Fix: Avoid race condition that may initialize a document twice on the clients
  • Fix: Catch exception from LogIteratorFactory, throw a clean error when log_type is not file
  • Fix: No password set for new mail shares
  • Fix(admin role): fix old and wrong way to determine whether user is admin
  • Fix(backend): Accept pushes with only step1 messages by read-only clients
  • Fix(config): Make sure user keys are strings
  • Fix(settings): posix_getpwuid can return false which should not be accessed like an array
  • Fix(UpdateNotifications): Handle numeric user ids
  • Fix(user_ldap): Early failure for empty password login attempt
  • Fix(user_status): Fix status update request not being sent
  • Improve files version listing
  • Use the proper path to check if a file needs to be copied/moved to the actual target storage

Desktop client 3.12.3

Update is highly recommended

Due to important bug fixes released in this update, we highly recommend the users of version 3.12 to upgrade to the latest version.

Recent updates 3.12.1 and 3.12.3 include several important bug fixes to tackle issues reported by customers.

In version 3.12.1, there are multiple improvements in end-to-end encryption functionality and a fix to a data loss issue that affects the users when group folders and files are moved from one location to another. Find the full changelog on GitHub.

The biggest part of version 3.12.3 is improvements for Windows users with a crash issue fixed and a much faster contextual menu performance. The crash could happen depending on the user workflow with the Windows file manager and its Nextcloud client integration. It also includes an important fix for users of group folders. Find the full changelog on GitHub.

Stay tuned for Nextcloud Hub 8! 🔔

Sign up for the Nextcloud Hub 8 launch event on April 24. Register now to participate in the live online presentation and be among the first to experience the next big update!

Register

Always keep your server up to date!

Nextcloud’s minor releases primarily focus on addressing security vulnerabilities and functionality bugs, avoiding major system overhauls that could jeopardize user data. Keeping your server up to date is vital, and our approach to testing and validation ensures that upgrading to minor releases is generally smooth and reliable.

For mission-critical Nextcloud systems in enterprise settings, consider switching to Nextcloud Enterprise. The tier provides you with ultimate deployment confidence: direct access to the Nextcloud engineering team, full assistance throughout deployment and integration, and peace of mind for system administrators. If you’re responsible for maintaining Nextcloud in your setting, this option may be the ideal solution for you.

1 Like

I guess the version numbers in the first sentence are wrong? And maybe there is an “r” missing in the same sentence?

2 Likes

Well same problem again

  • Verifying integrity

Parsing response failed.
Show detailed response

The detailed response is empty


if you have announced your problems at the right place - that’s good,

since nobody would read it over here, probably.

This is a bot-(auto)generated thread

Hi! Thank you for noticing the issue, all fixed now both here and in the article.

1 Like

Please open a dedicated thread for your matter. And check your updater.log file, located in your data directory, for details that might help. Or use the command line Updater, as described in the Admin Manual.

1 Like

…“functionality, ensuring smooth operation and improved user experience:…”

Yet, this old bug has not been fixed. Please fix. Thank you.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.