New Hotfix 4.1.6 Released

Bugs fixed in hotfix 4.1.6
· Documents – Insufficient permissions check on document Properties -> Versions tab.
· WYSIWYG editor - In "Insert image or media" dialog there were only user's running sites available for global administrator instead of all running sites.
· WYSIWYG editor - Selection of the multi-cultural document didn't work properly.
· Ecommerce - Shopping cart web part didn't work properly in update panel.
· Full page caching - The cache was not used when the client didn't have the cookies enabled
· Attachments - When using check-in/check-out updating image attachment didn't refresh the image in special cases.
· New site wizard didn't work correctly under windows authentication in special cases.

Bugs fixed in hotfix 4.1.5 (included 4.1.6):
· Newsletters – Editable region with “-“ (dash) in its name worked only when editing a newsletter issue, it did not worked on preview or sending.
· Image editor – Preview of the image wasn’t shown correctly after some action was performed in special cases.
· Webparts – Content before and content after was displayed when “Hide if no record found” was set and no records were found (applies to multiple webparts)
· Attachments – User was able to modify document attachments even if the account didn’t have permission to current document workflow step.
· Export – Source control folders (.svn) weren’t excluded correctly from the export package.
· Media library UI - 'Open in full size' link didn't work when URL contains port number.
· Documents – Insufficient permissions check on document Properties -> Versions tab.
· Custom tables - Actions disappeared after two postbacks in custom table data listing
· Blogs – Moderated trackback comments were not displayed in comment list.
· Content – Under specific circumstances (inconsistency in database) creating the new culture of the document could delete the document and its child documents entirely.
· WYSIWYG editor - Serialization error occurs in "Inser image or media" dialog when using <sessionState
mode="StateServer" /> in web.config file.

Bugs fixed in hotfix 4.1.4 (included in 4.1.5):
· Live site – Head element contained debug element CSS classes even if the debug mode was not set.
· Custom tables – If selected columns of a custom table contained column which didn’t exist anymore for the custom table, an exception was shown when user displayed the custom table data.
· Documents – Ad-hoc page template was deleted with document even if other language versions of the document used this page template.
· Smart search - Checking permissions for global administrator in some cases didn't work properly.
· E-mail engine - Impersonating problem in AsyncEmailSender class.
· Bizforms – Empty links occurred in notification and confirmation e-mails even though no files were uploaded.
· GetFile – In case of leaving the CMSDesk, the culture settings for GetFile script wasn’t applied correctly if the culture was changed on the live site.
· Reporting - Reporting controls required the stored procedure query to have all the context parameters instead of just the report parameters.
· Attachments - Content Before and Content After properties issue with DocumentAttachments and AttachmentLightboxGallery web parts.

Bugs fixed in hotfix 4.1.3 (included in 4.1.4):
· Universal document viewer - Paging didn't work properly and data were not displayed if site name and culture were not specified.
· WYSIWYG editor - In some cases an exception was thrown while saving the document.
· Media libraries - media library context macros didn't work properly.
· Paging of CMS server controls in some special cases didn't work properly.
· CMSViewer - XSLT transformation wasn't correctly displayed.
· Deletion of group pages could throw exception due to reference problems.
· Web analytics – “An entry with the same key already exists” error could have occurred when smart checking was used.
· Document attachments - Exception was thrown when workflow scope was set on an existing document.
· Document attachments - User wasn't able to edit image attachment when creating new language version of a document.
· Ecommerce - Custom code of the CustomOrderInfoProvider.GetInvoiceNumber(obj order) method wasn't applied while evaluating ##INVOICENUMBER## macro in e-mail templates.
· Import/Export - 'No license found' error message was displayed when user tried to import site on domain with some port even if the license for given domain existed.

Bugs fixed in hotfix 4.1.2 (included in 4.1.3):
· Content Staging - Media library files (database records) weren’t synchronized.
· Document attachments – New attachment link is not visible in some special cases (e.g. diacritics in resource strings).
· Deployment – Custom table transformations weren’t saved to disk during the deployment process.
· Attachments – Attachment web parts didn’t displayed the grouped attachments on ASPX templates.

Bugs fixed in hotfix 4.1.1 (included in 4.1.2):
· SmartSearch - Creation of new index ignored white space analyzer.
· SmartSearch - "No result text" message wasn't displayed properly.
· Custom tables – Exception was thrown in the custom table data list in CMS Desk UI when user selected fields to be displayed in the list of data.
· Tags – In some cases tag selection didn’t work properly when tag group was changed on Metadata tab in
document properties.
· WYSIWYG editor dialogs – In some cases page event validation exception was thrown.
· WYSIWYG editor - Wrong URL of the inserted images, media and links in e-mail templates
· Import/Export – Importing site into existing site in one instance broke integrity of the documents in special cases.
· Forums – In some cases community forum didn't display forum attachments properly.
· In some cases URL with trailing slash wasn't correctly generated.
· Web analytics - KeyNotFoundException occurs when smart checking is used in web analytics.
· If Windows authentication was enabled, form state helper didn't work properly
· Javascript error occurs while unloading the page with YouTube video player
· Newsletters - images were not displayed in incoming e-mails
· Macro resolver – Default values weren’t correctly resolved.
· Deployment - Web site couldn't be compiled to a single assembly due to class duplicity

Should you need any help with this hotfix or experience any other issues with it, please feel free to contact us at support@kentico.com.