wp-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 6114broken-link-checker
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 6114wp-extended-search
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 6114Come sempre, i rilasci minori includono miglioramenti alla stabilit\u00e0 e alla sicurezza e sono progettati per essere un aggiornamento sicuro e veloce.<\/p>\n\n
Purtroppo non abbiamo ancora il changelog<\/a>, in quanto ci stiamo divertendo con WordPress. Ci stiamo lavorando!<\/p>\n\n Nel frattempo, puoi consultare il changelog in questo post del forum.<\/a><\/p>\n\n Nota\u00b2:<\/strong> PHP 7.4 non \u00e8 pi\u00f9 ufficialmente supportato dalla comunit\u00e0 PHP.<\/em> Nextcloud supporta da tempo PHP 8.0 e versioni successive e ti consigliamo vivamente di passare a una versione pi\u00f9 recente di PHP. La versione 8.0 ha gi\u00e0 terminato il supporto attivo (!) e ha solo 11 mesi di aggiornamenti di sicurezza. Nextcloud Hub 3 (25.0.x) depreca PHP 7.4, ma funziona ancora con esso. Tuttavia, consigliamo di utilizzare PHP 8.1 e la nostra prossima release Hub 4 abbandoner\u00e0 il supporto 7.4. Questa release \u00e8 anche in grado di supportare PHP 8.2, che \u00e8 stato rilasciato oggi.<\/a><\/p>\n\n
Nota:<\/strong> non ci saranno pi\u00f9 rilasci di Nextcloud Hub 2 (23.0.x). Esegui l’aggiornamento a Nextcloud Enterprise per continuare a ricevere gli aggiornamenti di sicurezza e stabilit\u00e0 oppure passa a 24.0.x o Nextcloud Hub 3 (25.0.x). Non dimenticare che l’utilizzo di software web-facing senza aggiornamenti regolari \u00e8 rischioso. Ti invitiamo a rimanere aggiornato sui rilasci di Nextcloud sia del server che delle sue applicazioni, per la sicurezza dei tuoi dati! I clienti possono sempre contare sul nostro supporto per gli aggiornamenti, se necessario.<\/p>\n\n