ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114simple-custom-post-order domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Today we’ve released the first update to Nextcloud 10 and a 3rd update to Nextcloud 9. These releases bring a large number of improvements, most notably an improved updater. We strongly recommend upgrading. Read on for a taste of what is new.
The new updates add some minor functionality to Nextcloud 9, allowing user quota retrieval via the provisioning API and supporting the files drop capability for clients. Clients will also be able to retrieve theming information so they can adjust colors or icons as well and the theming tool will modify the browser page titles to match the setting by the Admin. The Nextcloud installation process will warn users that Nextcloud 9 does not support PHP 7.1 and will refuse to continue the installation.
Nextcloud 10 received most of the same enhancements as 9, adding the ability for admins to specify the configuration directory in an environment variable and applying the password policy upon user creation.
Besides the introduction of these enhancements over 40 bugs were squashed in both 9 and 10.
A complete changelog can be found on our website.
With 10.0.1 and 9.0.54 we include a more reliable updater which has been in testing for several weeks. We had disabled the update notifications in current versions due to issues with the updater. We decided to spend time on additional testing and improvements to make sure no admin would be left with a broken instance. The new updater replaces the files of the existing installation with those of the new release, doing extensive checks in between to ensure the platform, permissions and other requirements are all as they need to be. Once the upgrade of the files is done, the normal update process can be started from either the command line or the browser. To upgrade to 10.0.1 and 9.0.54 you still need to do this manually via our tarballs. For future updates (from 9.0.54/10.0.1 to a release afterwards) instances can more easily be updated via the new web based updater which shows up in the admin settings once there is an update available. In the upcoming releases we also plan to bring this feature back to the command line tool.
If you’re eager to test the new updater with an old version of Nextcloud you can find the steps in the forums, but they should only be used by experienced users. Only updating the URL in config.php to the new server (via updater.server.url) is strongly discouraged because then the old updater will break your setup.
Another update done!
“When we have welcoming communities of contributors, open source software gets better and more useful to everyone.” Limor Fried, Electrical Engineer, Inventor and Founder of open-source hardware company Adafruit We believe in this ideal and love to work with our community. We are always looking to involve more people in Nextcloud, bringing in their ideas, […]
Ver más
When cables are cut, sanctions are put in place or privacy legislation prohibits the use of the service your entire organization depends on, what can you do? Amidst geo-political changes, organizations face dependencies on large, centralized communication platforms. A major example of this is the SaaS-only communication platform Microsoft Teams. It is the only solution […]
Ver más
Nextcloud, a leading provider of open-source collaboration software has partnered with epiKshare to deliver Nextcloud One — a fully managed, secure and compliant cloud solution hosted in Germany.
Ver más
The Nextcloud Conference is not your average event - it's a community meetup that brings together Nextcloud enthusiasts, contributors, developers, users and industry experts from all over the world.
Ver más
