DotNetNuke 5.6.0 verfügbar

Eine Neue Version von DotNetNuke ist seit Gestern verfügbar.

Die neue Version 5.6.0 (Community Edition) kann wie gewohnt auf Codeplex heruntergeladen werden.

Etwas wirklich neues gibt es nicht in dieser Version.
Wie aus Nachfolgender Übersicht der Neuerungen zu erkennen ist, beginnen fast alle Änderungen mit “Fixed”, also beseitigte Fehler.

  • Added automatic portal alias creation for single portal installs
  • Updated the file manager upload page to allow user to upload multiple files without returning to the file manager page.
  • Fixed issue with Event Log Email Notifications.
  • Fixed issue where Telerik HTML Editor was unable to upload files to secure or database folder.
  • Fixed issue where registration page is not set correctly during an upgrade.
  • Fixed issue where Sendmail stripped HTML and Links from emails.
  • Fixed issue where Ribbon Bar CSS was included on the page even when Ribbon Bar was not visible.
  • Fixed issue where „My Folder“ was not available in the URL control and the Telerik HTML Editor
  • Fixed issue where the language skinobject dropdown does not maintain state between postbacks
  • Fixed issue where the UserProfile PhotoURL property not set properly
  • Fixed issue where Data Caching code could result in race condition
  • Fixed issue where a portalalias with a trailing „/“ would cause a 404 error
  • Fixed issue where reference copies of modules are not copied from the primary to secondary language pages.
  • Fixed issue where a disabled language can result in orphaned pages which are not localized with Content Localization
  • Fixed issue where content item wasn’t being assigned to host tabs resulting in error when changing the host page title
  • Fixed issue where localized grid header columns did not sort
  • Fixed issue where the ribbonbar control panel was not properly moving pages when localization was enabled.

Allerdings ist durch eine Optimierung der Datenstruktur eine leichte Verbesserung der Performance zu erkennen, insofern die Datenbankzugriffe und nicht der Webserver das bisherige Nadelöhr ist.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.