New Hotfix 5.5R2.44 (build no. 4311) Released

Bugs fixed in hotfix 5.5 R2.44 (build no. 4311 and the last for 5.5R2 version):
· BizForms - Sending a notification for a form with an empty file uploader field caused an exception.
· BizForms - Saving a 'File' type field in an alternative form changed the field type to 'Text'.

Bugs fixed in hotfix 5.5 R2.43 (build no. 4300):
· Form controls - The Community group selector wasn't visible on updatable precompiled sites.
· E-commerce - The SendOrderStatusNotificationToCustomer method logged an incorrect message into the event log (wrong event source text).
· Dialogs - The direct file uploader opened an uploader dialog instead of a file selector if the content culture was set to Turkish.
· Notifications - The e-mail notification gateway logged an exception if the notification control couldn't be found.
· On-line forms - File extension validation was skipped if the size of the file was 0 bytes.
· Web parts and controls - The content of the Editable text web part wasn't validated to reflect maximum length when the Check in action was used.
· Newsletters - The .aspx extension was automatically added to the unsubscription page URL, even if extensionless URLs were used.
· The MaxNodeNameLength property wasn't processed correctly for new documents.

Bugs fixed in hotfix 5.5 R2.42 (build no. 4281 - the same as previous hotfix):
· Users weren't able to edit resource strings if the database contained a record with an empty KeyName field.

Bugs fixed in hotfix 5.5 R2.41 (build no. 4281):
· Documents - The bulk Publish action in CMSDesk List mode handled incorrectly documents that had already been Published.

Bugs fixed in hotfix 5.5 R2.40 (build no. 4279):
· UI - Breadcrumbs were displayed incorrectly when the UI was switched to an Arabic culture.
· Smart search - The Smart search filter web part did not display special characters correctly.
· Import/Export - The Import and Export processes couldn't handle some special characters in the data.

Bugs fixed in hotfix 5.5 R2.39 (build no. 4268):
· URL rewriting - If extensionless URLs were enabled, URLs that contained a period character returned a page not found error.
· Documents - The Document selector form control didn't work correctly when used on linked documents.
· Media library - The media library selector dialog incorrectly used the live site design.

Bugs fixed in hotfix 5.5 R2.38 (build no. 4261):
· Tags - The tag selector added the '-' character as a prefix to selected tags.
· Documents - The Document selector form control didn't handle document selection correctly when the preferred culture was changed.
· Dialogs - If an editor (user) was removed from a site, the given site was incorrectly loaded for them in WYSIWYG dialogs.
· Updating the settings of a user caused duplicate records when performed under a heavy load with windows authentication enabled. You can set the appSetting key CMSUpdateLastLogonForExternalUsers to false to limit unwanted user updates.

Bugs fixed in hotfix 5.5 R2.37 (build no. 4255):
· Tags - Multiple tag selectors on a single page didn't work properly.
· E-commerce - The Company text box disappeared after validation failed in the Customer registration form in the shopping cart.
· Widgets - The widget selector didn't display widgets in sub-categories correctly in special cases.
· All media web parts threw a javascript error if the "Automatically activate the object" property was checked and the resource string "Media.NotSupported" contained an apostrophe.
· Debugging caused a null reference exception in special cases.

Bugs fixed in hotfix 5.5 R2.36 (build no. 4248):
· Web analytics - Statistics weren't logged for pages accessed via extentionless URLs.
· Documents - Switching to Live site mode in CMS Desk could change the current content culture when using the 'Combine with default culture' setting.
· Documents - The UI element of the Page tab was incorrectly required for users to be able to create new documents.
· Document - When creating a region through the Edit regions & web parts function, code names weren't validated correctly.
· Documents - If the image selector form control was used in a document field, the selected image wasn't displayed correctly on documents that were linked from another site.
· Blogs - The query used to load blog comments was too long if there was a very large number of blog posts.
· Staging - Deleting or synchronizing a single staging tasks didn't create an entry in the event log.
· The password retrieval feature in the Logon form web part didn't work correctly in special cases.
· The FolderTree.ascx control was generating a warning.

Bugs fixed in hotfix 5.5 R2.35 (build no. 4237):
· Community - The 'My invitations' web part didn't work correctly when placed on an ASPX template.
· Documents - A document had to be checked in twice in special cases.

Bugs fixed in hotfix 5.5 R2.34 (build no. 4237):
· Forums - Forum breadcrumb links incorrectly included the paging query string parameter.
· Web analytics - Invalid log files prevented other log files from being processed.
· URL rewriting - Language selection didn't work if permanent redirects were cached in the browser.
· Media library - The GetMediaFile page returned a 404 error instead of the access denied page if a file was accessed by an unauthorized user.
· Media library - The media library file uploader generated javascript errors if none of the existing files were imported.
· Staging - The 'Run complete synchronization' function always synchronized all servers, even if a specific server was selected.
· Certain modules incorrectly used system tables instead of catalog views in their SQL queries.

Bugs fixed in hotfix 5.5 R2.33 (build no. 4223):
· Document library - The Library path property didn't support path expressions (wildcards).

Bugs fixed in hotfix 5.5 R2.32 (build no. 4223):
· File Import - The import process failed if the FileName or FileAttachment fields of the CMS.File document type were renamed.
· E-mail templates - The Insert button of the macro selector didn't work when adding macros into e-mail templates in the IE9 browser.
· Page templates - When selecting document content inheritance levels, incorrect items were displayed in special cases if the path contained linked documents.
· Documents - The paths of linked product documents weren't displayed correctly on the Product tab.
· Newsletters - The "No data found" information label was displayed twice on the newsletter Subscribers page.

Bugs fixed in hotfix 5.5 R2.31 (build no. 4216):
· Form engine - The User control selector didn't work correctly when creating a new web part in IE9.
· BizForms - Notification e-mails always used the default form definition, even when an alternative form was specified.
· File import - The import process failed if the name of the FileDescription field of the CMS.File document type was changed.
· Newsletters - If a dynamic newsletter loaded its subject from a page title containing special characters, the results were incorrectly encoded.

Bugs fixed in hotfix 5.5 R2.30 (build no. 4206):
· Page templates - Templates containing certain special characters in their name caused an exception when loading the page layout.
· WYSIWYG editor - UI personalization didn't work correctly for the editor toolbar while using the Turkish culture.
· Notifications - The notification sender wasn't thread safe.

Bugs fixed in hotfix 5.5 R2.29 (build no. 4202):
· Two different controls used the same prefix and tag name, which caused issues when converting to a web application project.
· Form engine - The Department roles selector didn't work correctly when used in a document type form if the Allow empty value flag was disabled.
· Form engine - The Document stylesheet selector returned an error when used to directly edit the selected stylesheet.
· Controls and web parts - The DataPager.GetItemPage method of the CMSRepeater control didn't work correctly if the page size was greater than 1.
· The role and user selectors in the document properties security panel didn't work correctly in special cases.
· Dialogs - The Insert link WYSIWYG editor dialog was opened with an incorrect size in the IE9 browser.
· Blogs - The GetDocumentTags transformation blog function didn't return the correct tag group ID for inherited tag groups.
· Mobile support - PDF files weren't opened correctly in the Android mobile browser.

Bugs fixed in hotfix 5.5 R2.28 (build no. 4191):
· Smart search - Index rebuilding didn't work with specific environment settings.
· Transformations - The 'Check out to file' button was visible and didn't work correctly when creating a new transformation.

Bugs fixed in hotfix 5.5 R2.27 (build no. 4188):
· BizForms - The 'After the form is submitted' configuration of a form behaved incorrectly if the 'Display text' option was selected with an empty string value.
· Forums - The performance of post insertion/update was improved.
· Blogs - The Blog posts RSS feed web part didn't work correctly when special characters were entered into the Feed name property.
· Departments - If the 'Intranet portal department' document type wasn't available in the CMS, department widgets displayed an unhandled error message.
· Cultures - The insert link dialog didn't generate a correct URL if multiple culture versions of the selected document existed in the content tree and one of them had a custom URL path.
· Document attachments - Attachments inserted into an editable region of a document weren't accessible after the document alias was changed.
· Dialogs - Selected documents weren't highlighted correctly in the Insert link dialog under special circumstances.

Bugs fixed in hotfix 5.5 R2.26 (build no. 4181):
· Forums - Extended forum search didn't work correctly together with custom querystring parameters.
· E-commerce - Some selectors didn't work correctly when assigned to a custom field in the SKU system table.
· Membership - The button for sharing content on Twitter provided by the Social bookmarking web part didn't work properly.
· Smart search - Special characters entered into the search keywords could cause a parsing exception in special cases.
· Page templates - Template inheritance levels weren't displayed correctly for linked documents.
· Form engine - Some of the properties of the HTML Area field type weren't saved properly in the field editor.
· Message boards - Original and linked documents didn't share the same message board data.

Bugs fixed in hotfix 5.5 R2.25 (build no. 4175):
· Membership - The CMSRoleProvider.GetRolesForUser method didn't return any roles if the current site was unavailable.
· Membership - Updating the settings of a user could cause duplicate records when performed under a heavy load.
· Macros - The macro resolver threw an exception if the (substring) parameter was used with a greater specified length than the value of the macro.
· List mode - Duplicate messages were displayed when a node with no child documents was selected.
· Blogs - Localization macros weren't resolved correctly when used in e-mail templates for blog notifications.
· Page templates - Document inheritance was ignored for templates set as master templates.
· Page templates - The GetPageTemplateCategoryInfoByGUID method caused an error when called.
· Page templates - Changing the code name of a page template category didn't change the path of its sub categories.
· Smart search - The maximum search field size was set to a default value without the possibility of changing it. If you wish to change this value, you can now set the CMSSearchMaxFieldLength appSettings key in the web.config file.
· It was impossible to delete a site while using .NET 4.0 in a medium trust environment.
· Linked documents - Document name path of linked documents wasn't handled correctly in special cases.

Bugs fixed in hotfix 5.5 R2.24 (build no. 4164):
· Caching - Output caching didn't work correctly for rewritten URLs.
· Caching - Output (full page) caching didn't properly distinguish between the compressed and plain text version of the returned html.
· Dialogs - The Media selector modal dialog didn't open correctly in the IE9 browser.
· URL rewriting - The percentage symbol (%) was incorrectly allowed in the URL path of documents.
· Media library - The selected file wasn't displayed correctly after the deletion of another file.
· Media library - Web farm tasks for creating new media files didn't check the value of the 'CMSWebFarmMaxFileSize' web.config key.
· Web farms - Clearing cached items didn't work correctly on web farm servers.
· Form engine - The field editor for alternative forms displayed an exception when the field type was changed.
· The "Go to live site" and "Switch to CMS Desk/Site manager" links were in some cases not accessible in Gecko and Webkit-based browsers.

Bugs fixed in hotfix 5.5 R2.23 (build no. 4160):
·  Membership - Roles couldn't be deleted if they were used in BizForm security settings.
· Geo mapping - Map web parts weren't loaded correctly if their tooltip contained quotation marks.
· Licensing - OpenID authentication wasn't included with the Social networking package.
· File import - Files weren't imported correctly if the target path was under workflow with automatic publishing.
· Blogs - The creation of a new blog post caused an error if the Trackbacks - pinged URLs form control was used.
· Media library - Uploading media file thumbnails didn't work correctly when using the Chrome browser.
· The UniSelector control displayed the zero rows text twice in some cases.

Bugs fixed in hotfix 5.5 R2.22 (build no. 4150):

· Content staging - Manual synchronization of a document's subtree didn't work correctly if there were no child documents.
· Web parts - The Mobile redirection web part didn't identify BlackBerry devices correctly.
· Documents - Documents owned by groups couldn't be linked in special cases.

Bugs fixed in hotfix 5.5 R2.21 (build no. 4147):
· Documents - The document name path wasn't updated correctly when a user created a new culture version of a linked document.
· Documents - Cross-site linked documents displayed a page not found error in special cases. If you encounter this problem, you have to add the following appSettings key to the web.config file: <add key="CMSUseLinkedDocumentsForUrlPath" value="true" />.

Bugs fixed in hotfix 5.5 R2.20 (build no. 4136):
· Media library - The GetMediaFile system page returned empty html instead of a 404 error if the requested file didn't exist.
· Media library - Custom fields weren't cleared for new files inserted into a media library.
· Controls and web parts - The My account web part didn't save the avatar image of the user when it was used inside an update panel.
· Dialogs - The design of the vertical frame resizer in dialogs was incorrect when minimized.
· E-mail engine - Added support for custom regular expression strings applied to e-mail addresses. This is done using the 'CMSEmailValidationRegex' app key in the web.config file.
· Membership - CMSRoleProvider didn't work correctly with allowed roles specified in the authorization section of the web.config file.
· Blogs - Pinged URLs weren't displayed immediately after a blog post was saved.
· Form engine - The field editor didn't allow the "Allow empty" value to be changed for alternative forms when it was set to TRUE.
· Form engine - The field editor displayed an unhandled exception when the creation of a column failed.
· The media selection form control caused a javascript error when the preview image was clicked.

Bugs fixed in hotfix 5.5 R2.19 (build no. 4129):
· Media library - Permanent links weren't working correctly for media file thumbnails.
· Newsletters - Role subscribers received multiple copies of the same newsletter issue if e-mail archiving was enabled.
· Documents with special characters in their name were assigned incorrect node IDs in special cases.

Bugs fixed in hotfix 5.5 R2.18 (build no. 4125):
· Smart search - User indexes didn't process data from the user settings table.
· Macros - The (handlesqlinjection) parameter was nullary. It wasn't possible to turn this setting off in web part properties.
· Permissions - The drop-down list for site selection didn't refresh the permission matrix when used via a modal dialog.
· Caching - Full page cache (output cache) selected the wrong item to return in special cases.
· Controls and web parts - The TreeView web part didn't allow the setting of a separate location for line images for RTL cultures.
· Controls and web parts - Multiple logon forms on a single page didn't work correctly.
· Media library - The design of the media library folder tree wasn't changed correctly for RTL cultures.
· Dialogs - The Media library tab of dialogs caused an error if all sites in the system were stopped.
· Project management - Export and import of project tasks and ad-hoc tasks wasn't working correctly.
· The WYSIWYG editor didn't work properly when it was placed in an update panel.
· The advanced user filter didn't work correctly with large amounts of filtering data.
· The border of the WYSIWYG editor wasn't displayed properly in Firefox 4.

Bugs fixed in hotfix 5.5 R2.17 (build no. 4115):
· Import/Export - Module folders weren't imported correctly in special cases.
· Categories - Repeatedly saving a document containing a Multiple categories selector caused an error.
· The user interface had minor design issues when opened in Firefox 4.
· The Ctrl+S shortcut wasn't handled correctly in IE9.

Bugs fixed in hotfix 5.5 R2.16 (build no. 4108):
· Controls and web parts - The combination of a data source, filter and repeater web part didn't work correctly if the repeater used the "Hide if no record found" setting.

Bugs fixed in hotfix 5.5 R2.15 (build no. 4104):
· URL rewriting - Document aliases containing the underscore character and wildcards weren't processed correctly and displayed a page not found error.
· Certain modal dialogs couldn't be opened in the IE9 browser.
· Groups - The 'Owned by group' selector on the properties tab of documents didn't work correctly in special cases.
· Web farms - Unsuccessful synchronization between web farm servers wasn't logged in the event log.

Bugs fixed in hotfix 5.5 R2.14 (build no. 4097):
· Controls and web parts - The internal pager didn't render the html code for previous and next buttons correctly.
· SharePoint integration - Web parts didn't display columns with special characters in their name.
·  Membership - It was possible to attempt to remove a user/role permission inherited from the parent document in Document -> Properties -> Security and an exception was thrown into the Event log.
· Import - Document permissions weren't imported correctly in special cases.
· Smart search - The rebuilding of an index failed if the indexing of a single document was unsuccessful.
· Custom tables - The Custom table data grid web part didn't convert DateTime columns correctly in special cases.
·  Booking system - The Event calendar web part was only able to display details for the Booking event document type.
· Documents - The TreeProvider incorrectly used the LIKE operator if the node alias path contained the underscore character.
·  When changing the code name of a custom table or document type, the original name stayed reserved until the cache was cleared.
· Several parts of the user interface were displayed incorrectly in Internet Explorer 9.

Bugs fixed in hotfix 5.5 R2.13 (build no. 4090):
· BizForms - Forms with no records weren't displayed properly on the Data tab.
· Macros - The (notrecursive) macro parameter was propagated to all macros following after the first occurrence of a macro with this parameter.
· Macros - The (handlessqlinjection) macro parameter wasn't automatically added to the web part properties resolver.
· Attachments - Unsorted attachments weren't displayed correctly in the Properties section of CMS Desk in special cases.
· Custom tables - The custom table datasource retrieved data from the database too often.
· Custom tables - The building of WHERE conditions was inefficient in specific cases.
· Workflow - The root node of a site had its Form tab content disabled when under workflow.

Bugs fixed in hotfix 5.5 R2.12 (build no. 4083):
· Field editor - The creation of fields with the same name as fields in View_CMS_Tree_Joined wasn't allowed.
· Workflow - Having the root node under workflow without check-in/check-out caused an error during the saving process.
· Workflow - The Versions tab in CMS Desk wasn't refreshed properly after destroying the version history.
· URL rewriting - The Default alias path property of Domain aliases wasn't correctly applied to URLs containing the "www" prefix.
· Dialogs - The Image inline control wasn't working correctly if a custom jQuery framework was loaded.
· Membership - The CMS.SiteProvider.UserInfoProvider.ForgottenEmailPassword() method threw an exception when HttpContext was null.
· Documents - Non-published documents with defined permissions weren't displayed correctly in some cases.
· Documents - The Check-in action didn't save document content if the "Prompt to save changes on exit" setting was enabled.

Bugs fixed in hotfix 5.5 R2.11 (build no. 4073):
· Tags - The Tag cloud web part generated a redundant space before tag separators.
· Macros - The (handlesinjection) macro parameter was propagated to all macros following after the first occurrence of a macro with this parameter set.
· Web parts - The XML Data source web part didn't work correctly with feeds using additional namespaces.
· Friends - In special cases, web parts of the Friends module (Friends data source, My friends, Friends viewer) weren't initialized properly and therefore didn't display any data.
· Form engine - It was possible to change the value of the 'Allow empty' field setting when managing alternative forms in the field editor, which could have resulted in an exception.

Bugs fixed in hotfix 5.5 R2.10 (build no. 4070):
· Windows authentication caused a redirection loop when a site was accessed by a user disabled in the system.
· Newsletters - A newsletter issue template was incorrectly required to create a new dynamic newsletter.
· Smart search - The performance of custom table search indexes wasn't optimal.
· Workflow - When a document under workflow was restored from the recycle bin, it was incorrectly published.
· BizForms - Deleting a record on the Data tab caused default sorting to be used for the remaining records.
· Web parts and widgets - Localization macros weren't resolved in the titles of web parts and widgets.

Bugs fixed in hotfix 5.5 R2.9 (build no. 4059):
· E-commerce - The check to determine whether a customer has sufficient credit was incorrect when the credit was equal to the price of the order.
· Form controls - Custom web part properties of the Date and time type weren't working correctly when a non-default UI culture was set.
· Newsletters - The newsletter subscriber selector didn't work correctly with .Net versions prior to 4.0 and a system culture different than English.
· Controls and web parts - The CMSDocumentValue control incorrectly generated an empty span tag before its content.
· Controls and web parts - The QueryRepeater and QueryDataList controls didn't work correctly in combination with postback paging mode.
· Controls and web parts - Web part layout wasn't processed correctly if the code name of the web part contained the dot character.
· Documents - Document check-out didn't work correctly with the Turkish culture in special cases.

Bugs fixed in hotfix 5.5 R2.8 (build no. 4051):
· Wildcard URLs didn't work correctly if they contained special characters.
· The DocumentNamePath field wasn't trimmed properly after a document was updated.

Bugs fixed in hotfix 5.5 R2.7 (build no. 4045):
· Intranet Portal - Role permissions weren't set correctly in special cases for Forum and Media library objects created as part of a department.
· When copying a document to the first position under the same parent, the move operation was performed instead.
· Web parts - Shortcuts web part didn't work properly if two instances of the web part with different property settings were placed on the same page.
· Project management - Personal tasks had their "Assigned to" field set incorrectly when imported in special cases.

Bugs fixed in hotfix 5.5 R2.6 (build no. 4041):
· Web parts - Calendar web parts didn't filter data via custom filters.
· Project management - Ad-hoc (personal) tasks were causing an error during the import procedure.
· Intranet portal - The RSS Forum posts page template incorrectly also displayed department forum posts. To fix this issue, please see the instructions at the end of the document included in the hotfix package.
· BizForms - Macros in field captions weren't resolved when exported to Excel.
· Documents - Documents couldn't be moved to the first position under the same parent using drag & drop.

Bugs fixed in hotfix 5.5 R2.5 (build no. 4031):
·  Media library - Certain stylesheets were loaded incorrectly in special cases.
·  Media library - The Media gallery, Media gallery - file list and Media gallery - folder tree web parts floated out of their web part container in special cases.
·  Media library - Image data wasn't refreshed correctly in special cases after changing the file name or extension via the image editor.
·  Membership - Facebook Connect, OpenID Authentication, Windows LiveID - a new role with an empty name was created for registered users if there were no roles specified for newly registered users.
·  Staging - When a user copied a document with multiple culture versions, staging tasks weren't logged for all culture versions.
·  Spell checker - FCKeditor fields were incorrectly checked twice.
·  Spell checker - The spell checker didn't check BBcode editor type fields.

Bugs fixed in hotfix 5.5 R2.4 (build no. 4027):
· Dialogs - Flash objects inserted through the WYSIWYG editor weren't generated correctly in the Google Chrome browser.
·  Staging - Custom data of document relationships weren't synchronized.
·  Media library - An incorrect method was called in the ValidateForm method of the MediaLibraryEdit control.
·  Yahoo Map - The "Show scale control" and "Show navigation control" properties of the web part didn't work correctly.
·  Project Management - Roles couldn't be deleted in special cases due to project dependencies.
·  Document library - Links to documents were incorrectly displayed even if the document had no file attached.
·  Relationships - Relationships not assigned to the current site were displayed in CMS Desk -> Properties.
·  Relationships - The path to the related document wasn't stored in a textbox field if the related document was on the right side.
·  Web parts - The Silverlight application web part wasn't working correctly with the silverlight navigation application.
·  Workflow - The check-in operation on the Versions tab of documents didn't work correctly in special cases.
·  WebDAV - rebuilding of the source code caused an assembly version conflict.
·  Reporting - Line graphs caused an exception when displaying data with only one record.
·  Media library - Media file mime type wasn't set correctly in special cases.

Bugs fixed in hotfix 5.5 R2.3 (build no. 4020):
· Page templates - New template wasn't created correctly in special cases.

Bugs fixed in hotfix 5.5 R2.2 (build no. 4014):
· Messaging - Actions were not hidden properly when an error occurred during sending a message.
· E-commerce - Product filter did not work correctly.
· Text - Editable image web part did not work correctly when application ran internally on a different port.
· Dialogs - WYSIWYG dialogs did not work properly when media library folder name contained special characters.

Bugs fixed in hotfix 5.5 R2.1 (build no. 4006):
· Project management - Users and roles couldn't be deleted in special cases due to project or task dependencies.
· Documents - Linking to child documents wasn't working correctly when they were translated into multiple cultures.
· Workgroups - New forum groups created under a workgroup from the live site didn't have their base URL set correctly.
· The Field editor didn't allow macros to be inserted into the Default value textbox for non-text fields.
· Security - Moving the position of a document was allowed in special case even if the user didn't have the Modify permission.
· Workflow - Workflow e-mails were incorrectly sent to disabled users.
· Form controls - GUID type columns created in the Field editor were causing exceptions.
· Web analytics - The context help for the Registered users section was missing.
· Messaging - It was incorrectly possible to reply/forward a message with an empty message body.