Print

Some of the issues described on this page contain internal reference numbers. You can use these reference numbers when communicating with Sitecore about a particular issue or feature.

July 19, 2010

Released Sitecore CMS 6.3.0 rev.100716.

Please visit the appropriate Sitecore CMS 6 downloads page for instructions describing how to download and install this release.

Change log.

New Features:

• Scaling and multi-instance setups:
  • Important: Please read the Sitecore Scaling Guide in its entirety before you configure a group of CMS and/or content delivery instances or before you configure Web Deploy.
  • Support for sharing the Master database between multiple load-balanced CM instances.
  • Possibility to set up two or more Sitecore installations to operate in a group, functioning as a single content authoring or content delivery environment.
  • Possibility to designate a specific instance to be a Publishing Server. This ensures that publish jobs are not run in parallel and makes it possible to have a dedicated Publishing Server.
  • New facility for deploying file-based media to content delivery servers during publishing, based on Microsoft Web Deploy.
  • Ability to forward security events from the CMS instance(s) to the Content Delivery instances, including the ability to filter which events that should be forwarded. This is useful for clearing the cache on the CD servers when they share the same security database as the CMS instance(s).
• Timed expiration of security caches:
  • A new Caching.SecurityCacheExpiration setting has been introduced in the web.config file to periodically clear the security cache. This can be useful in multi-instance setups. (324144)
• Possibility to disable file based media entirely:
  • A new Media.DisableFileMedia setting has been introduced in the web.config file to allow customers to disable file based media. (327602)
  • When setting this setting to "true", Sitecore will always store media in the database and will not allow users to upload media to Sitecore that are larger than the Media.MaxSizeInDatabase value. Also, the UI will hide options to select that media should be stored as files. Any existing file based media items will continue to work. Notice that this setting takes precedence over the Media.UploadAsFiles setting.

Improvements:

• Setup.exe installation program:
  • The installation program supports localization. (328808)
  • The installation program was translated to Japanese. (330920, 330479)
  • The installation program was translated to Danish. (330920)
  • The installation program is now signed with a Sitecore certificate. (320292)
  • IIS7: the application pool can now be created in Integrated Mode, user’s choice (329934)
  • The installation wizard UI has been enhanced in several areas. (318647, 318668, 318669, 322734, 323562, 323564)
• Publishing:
  • The performance of publish operations have been improved, especially for Smart Publish and Full Publish. (328476)
• Development:
  • Some complex ASP.NET controls may fail to work properly when their Controls collection is accessed on the early steps of the page cycle and the following controls has therefore been added to the <typesThatShouldNotBeExpanded> section of the web.config file (in addition to Repeater and DataList which were already present):
    • System.Web.UI.WebControls.GridView
    • System.Web.UI.WebControls.ListView
    • System.Web.UI.WebControls.FormView
    • Microsoft.Reporting.WebForms.ReportViewer
    • Telerik.Web.UI.RadGrid
  • A new API method called Template.InheritsFrom() has been introduced to make it easier to check if a template inherits from a specific base template. The method takes one parameter which can either be a template name or a template ID. (321610)
• Update packages:
  • Sitecore update packages now support a format where files are stored as "real" files in the zip-file rather than being stored as encoded text. (300529)
    • This allows developers to copy files from an update package into their solution without installing the package.
    • Also, it allows developers to remove files from update packages before installing the update package.
    • Manually adding files to a package is not supported since Sitecore requires special metadata to be present in the update package for files.

Important changes:

• SQLite:
  • The SQLite database provider is no longer supported, and all related DLLs and configuration files have been removed. (322769, 322936)
• Client languages:
  • The clean distribution of Sitecore CMS now contains the following client languages: (326523)
    • English
    • Danish
    • Japanese
  • The Danish and Japanese client translations have been updated to fix a number of missing and incorrect strings compared to the 6.2 translations.
  • Additional client languages can be downloaded from the 6.3 Client Translations  page on SDN, as well as future updates to the Danish and Japanese translations.
• Client RSS Feeds:
  • When you subscribe to one of the Sitecore Client Feeds for a workflow or workflow state, the feed will now only display feed entries for the items currently in that workflow/workflow state. Previously, workflow feeds would contain entries for all workflow actions that had been executed on items in the workflow/workflow state, giving a complete history of workflow actions. (322212)
  • A new ClientFeeds.Enabled setting has been introduced which allows customers to disable all item and workflow feeds. (322210)
• Analytics:
  • The file /sitecore/shell/Applications/Analytics/visitor.css.aspx has been renamed and moved to /layouts/System/VisitorIdentification.aspx. The previous location of the file caused the sc:VisitorIdentification control to fail on Content Delivery servers where the /sitecore folder had been removed. (319573)
  • The Sitecore.Analytics.TransactionHandle class was defined in both the Sitecore.Client.dll and Sitecore.Analytics.dll, resulting in a compiler error if a project referenced both DLLs. The class has been removed from the Sitecore.Client.dll. (320939)
• Media API:
  • The default value of the Media.MaxSizeInDatabase setting has been increased from 15MB to 500MB to allow most media files to be stored in the database by default. (323169)
• ConfigWatcher:
  • The ConfigWatcher HttpModule which listens for changes to files in the App_Config directory has been changed so that it will now restart the ASP.NET worker process whenever a configuration file is changed (except from the domains.config file which is dynamically reloaded when changed). This ensures that all configuration changes are applied correctly, including changes to pipeline processors and event subscriptions done using include files. (323450)
• Lucene:
  • When EnableEventQueues is set to "true", the value of Indexing.ServerSpecificProperties will be forced to "true" to avoid misconfiguration of multi-instance solutions. (331056)
  • When Indexing.ServerSpecificProperties is set to "true", the IndexingManager will now use the new InstanceName setting instead of the machine name when generating the property key that is used for storing information in the Properties table about when the search index was last updated. (330289)
• PublishManager.Publish():
  • When the EnableEventQueues setting is true, PublishManager.Publish() will return a handle to a distributed publishing task instead of a job handle, and existing code that expects a job handle may fail. You can use PublishingManager.GetStatus() with both types of handles get the status and result of the publishing operation. (325033)
• Performance counters:
  • The default value for Counters.InstanceName has been changed from "Default" to "". (329812)
  • When Counters.InstanceName is set to an empty string in the web.config file, the setting will now resolve to the value of the new InstanceName setting. This will help to ensure that different Sitecore instances on the same server will use unique instance names for their performance counters. (329812)
• A number of 3rd party DLLs have been updated to a newer version. You might have to update and recompile your code if you are referencing these DLLs from your code:
  • The ComponentArt.Web.UI.dll has been updated from 2007.1.1617 to 2010.1.2637. (323480)
  • The Newtonsoft.Json.dll has been updated from 1.3.0 to 3.5.0. (327916)
  • The Stimulsoft DLLs that are used for Analytics reporting have been updated from version 2009.1.400 to 2009.3.600. (321179)

Issues resolved:

• Setup.exe installation program:
  • The installation process now consumes significantly less memory. (319423)
  • Another installation should not start if one is in progress (320776)
  • Oracle: The "Database only" mode would present the user with steps to set up the website. (328906, 329953)
  • Oracle: When uninstalling "Database only" instances, an error message would be displayed. (329117)
  • A number of minor improvements and bug fixes. (328808)
• Editing content:
  • The "Delete Subitems" button in the ribbon will now be disabled when the currently selected item does not have any children. (322768)
  • When inserting a Sitecore link in the Rich Text editor at the end of the text and without having any text selected, the link would sometimes be inserted with "_" as the name. (327043)
• Content Editor:
  • When a user tries to save an item or execute an action on an item which has been deleted by a different user, the Content Editor will now display a message informing the user that the item could not be found. Previously, the action would have been executed on the Home item. (323558, 323561)
  • When using Internet Explorer 8 in non-compatibility mode, rich text fields would display a vertical scrollbar in the Content Editor even when the content did not extend beyond the bottom of the rich text control. (315137)
• Events:
  • Since Sitecore 6.1, the second parameter for the item:renamed event would incorrectly contain the new name for the item instead of the old name. (318458)
  • Since Sitecore 6.1, the second parameter for the item:sortorderchanged event would incorrectly contain the new sort order instead of the old sort order. (324421)
• Publishing:
  • The PublishingAgent task only published the content tree root node when set to perform a smart or full publish instead of publishing the entire database. (321354)
  • Publish operations would sometimes perform unnecessary republishing of items and fields. (328476)
  • Publish operations cleared the data caches too frequently, including the item and template caches. (328476)
• Security applications:
  • If a user directly or indirectly denied read access for himself to an item in the Security Editor, a message would be displayed stating that "An instance of Sitecore.Data.Items.Item was null". Now, a message will be displayed informing the user that the item may have been deleted by a different user or that he might not have permissions to access the item. (325034).
  • When a user created multiple domains in the Domain Manager in quick succession, Sitecore would sometimes fail with an IOException stating that the process could not access the domains.config file because it was being used by another process. (326727)
  • When editing user profile information in the User Manager, a NullReferenceException would sometimes be displayed when saving if no profile item ID was defined for the user or the domain. (330996)
  • Reverting users from serialization in the User Manager would sometimes leave old properties or role assignments intact. (330006, 330007, 330211)
• Media requests:
  • If an error occurred during the execution of the getMediaStream pipeline, for example due to high server load causing the server to throw an Out Of Memory exception during image scaling, the resulting media stream would still be cached. This would typically mean that the full-size image would be cached and returned for subsequent requests, even if a scaled version of the image had been requested. (320851)
• Lucene search:
  • The _template field in the Sitecore.Search engine was storing GUIDs in a format which breaks CombinedQuery in Lucene, causing searches to fail. The field is now storing GUIDs as short IDs. The search syntax in the quick search is now "_template:76036F5ECBCE46D1AF0A4143F9B557AA" (327705)
  • Several methods in the DatabaseCrawler class have been made virtual to make it easier to override the functionality of the class. The methods are: AddItem, IndexVersion, DeleteItem and DeleteVersion. (330270)
  • Several fields in the DatabaseCrawler class have been made protected instead of private to make it easier to override the functionality of the class. The fields are: _hasIncludes, _hasExcludes, _templateFilter. (327706)
• RSS Feeds:
  • The performance when rendering workflow feeds and content item feeds has been improved. (326691)
  • When clicking a workflow action such as "Submit" in a workflow feed, the action would be executed, but the action page would sometimes trigger one or more JavaScript errors due to a missing reference to the jQuery library. (324273, 329021)
  • RSS feeds could fail with a NullReferenceException if one or more items were referencing an invalid workflow state, for example a deleted workflow state. (322270)
• Package Designer:
  • The Package Designer no longer use double packaging (i.e. generating a zip-file which contains the package.zip file) when that would make the resulting zip-file significantly larger than the "package.zip" file that is stored inside. (316707)
  • When adding items statically or dynamically, the Select Item control in the wizards would not align the information in the Description column correctly until one or more items were expanded. The Description column has been removed from the control. (330057)
• Development:
  • The "Field Editor Button" template has been added to the default insert options for the "Edit Frame Button Folder" template, making it easier for developers to create an Edit Frame and make it open a Field Editor window. (317041)
  • When a user created a new template by right-clicking a template folder and selecting "New template" in the context menu, the new template was created below the currently selected item in the content tree rather than the template folder that the user right-clicked. (321124)
  • When running in Debug mode, the rendering information windows would occasionally display an "Unknown rendering" error message when the user moved the cursor over the green arrows. (325342)
  • When using content dots in the Debugger (by setting WebEdit.Classic to "true"), a JavaScript error would occur when moving the cursor over the green arrows that shows rendering information. (326531)
• Additional system information in the log files:
  • Sitecore will now log the OS version when Sitecore is started to help in troubleshooting. (315517)
  • Sitecore will now log the Windows identity used by the process, including information about process impersonation. (329210)
  • The ShowVersion processor in the <initialize> pipeline will now output the version number of each assembly to help in troubleshooting. (313942)
  • The ShowVersion processor will now by default also show information about the Nexus DLL. (330860)
• Fast Query:
  • Using Fast Query in the Source for template fields would fail with a Sitecore.Data.Query.ParseException. Field sources using the "fast:" prefix will now be parsed and executed correctly. (322845)
  • The Sitecore.Data.Database.SelectSingleItem() method would fail with an exception when using a Fast Query expression. Such queries are now parsed and executed correctly. (322844)
  • Fast Query could return incorrect results if you were using a special attribute (such as @@templatename) as the first condition and a field name attribute as the second condition. (323302)
• Localization:
  • The "Click" field on the /sitecore/system/template/System/Ribbon/Chunk template has been changed from versioned to shared. This fixes a problem with several of the client languages where the Click command had been translated, which would cause the corresponding dialog not to open when clicking the name of the group in the ribbon. (323139)
  • The Section names in the Content Editor are now displayed in the client language, not the content language. (331210)
  • The "Do you want to save changes" dialog in the Content Editor displayed non-English characters incorrectly. (331072)
  • A number of phrases could not be translated in the following areas:
    • The Publish Wizard. (309463)
    • The "Insert" panel in the Content Editor ribbon. (315393)
    • Content Editor field validations. (325674)
    • The Properties dialog that can be opened by clicking the Sitecore logo in the Content Editor. (330985)
    • The WebDAV Drag & Drop window. (330990)
    • The "Nothing found" message that is displayed above the search box in the Sitecore Desktop task bar when no results are found. (331004)
    • The grouping notification in the grid control that is used by several applications, such as the User Manager, the Role Manager, the Locked Items dialog, and the Recycle Bin. (322992)
    • The Access Viewer. (330983)
    • The Control Panel, including some strings in the About dialog. (3209464, 323698)
    • The Analytics Status application. (331002)
    • The Rule Set Editor. (331001)
    • The Installation Wizard. (330993, 331005, 330991, 330991)
    • The Package Designer. (315403, 330984, 330997, 331005)
    • The Developer Center. (330970, 330972, 330976)
• Update Package Installation Wizard:
  • The Update Package Installation Wizard always displayed the package version as 1.0 instead of displaying the version information from the update package. (325797)
  • It has been made easier to select item IDs and item paths in the Analysis Result view. The relevant information will now be selected when clicking an ID or path. (325051)
  • The Update Package Installation Wizard now supports outputting information from post steps. The recommended way to do this is to implement the IUpdatePostStep interface and use the ILog object to output messages. (307858)
  • The Update Package Installation Wizard now supports installing update packages in a new format where files are stored as "real" files in the zip-file rather than being stored as encoded text. (300529)
  • The Update Package Installation Wizard no longer fails when a user tries to install an update package that has been manually unzipped and rezipped: (327262)
    • This allows developers to remove data from an update package or to change item data.
    • Manually adding files to a package is not supported since Sitecore requires special metadata to be present in the update package for files.
  • When installing a package that deletes an item and also removes links to this item from other items, you would get a warning incorrectly stating that the item would not be deleted due to links to other items. (305714)
  • If an update package changed a template field from versioned to shared and also tried to update the field value, the field would sometimes end up with an incorrectly value. (325769)
  • If an update package changed a template field from shared to versioned, you would sometimes not get any warnings or you would get incorrect warnings about the value of the field being different than expected. (318700)
  • If an update package changed a media item template from unversioned to versioned and the media was stored in the database, the media stream would be lost. (302098)
• Miscellaneous:
  • After changing one or more files in the App_Config folder, a number of database events would no longer be processed correctly. This could lead to a number of problems, such as items no longer being added to the PublishQueue or History table and standard values no longer being updated. (323450)
  • Changes to the Sitecore configuration done using include files were not always applied immediately, for example when adding or modifying processors to the initialize pipeline. Now the ASP.NET worker process is automatically restarted when configuration files are changed, ensuring that all configuration changes are applied. (323450)
  • Sitecore would not execute scheduled tasks with the default configuration of the system. This would cause scheduled Email Reminders not to be sent out and items scheduled for automatic archiving would fail to be archived. (318221, 316840)
  • When using IIS7 Integrated pipeline mode, the Sitecore.IntegratedSessionFix.Module would make ASP.NET load the session state for every request, including unmanaged requests for static images and files:
    • The IntegratedSessionFix module is no longer used and should be removed from the web.config file to avoid the overhead of loading session state for unmanaged requests. (326553)
    • To ensure that session state is still loaded for media requests when the media item has OMS tracking information, a new Sitecore.Resources.Media.MediaRequestSessionModule has been added to the web.config. (328238)
  • When using the IIS7 URL Rewrite Module or using performing redirects in custom HttpModules in IIS7 Integrated pipeline mode, a NullReferenceException would occur in the Sitecore.Nexus assembly. (326522)
  • When trying to log in, users could occasionally encounter an error message saying "Guid should contain 32 digits with 4 dashes". This could for example happen when a user that doesn’t use the "Remember me" feature opens a link in a RSS workflow feed. (321258, 321999)
  • Some of the Sitecore DLLs had missing or inconsistent assembly metadata, including information such as company name, copyright, and assembly version number. (320858, 320859, 320857, 320598, 321039)
  • The Interop.Shell32.dll was not used by Sitecore and is no longer distributed with the clean installation. (322811)
  • The /sitecore/admin/cache.aspx page was showing an incorrect delta for the AccessResultCache. The delta would always be equal to the current size of the cache. (317615)
  • A number of SQL statements related to Fast Query and maintaining the Descendants table were changed in the SQL data provider to make the system perform better when using SQL Server replication. (329922)
  • The Sitecore.Todo class has been marked as obsolete. (323278)
• The clean installation:
  • The clean SQL Server databases contained several fragmented indexes. (321296)
  • A number of items in the core and master databases were locked by sitecore\Admin. (321108)
  • The icons in the description fields on the Sample Rendering item and the "content" Placeholder Setting item would display as broken images. (321238)
  • The SitecoreClientTranslation tool (previously located in the /sitecore/shell/Applications/Globalization/SitecoreClientTranslation folder) is an internal tool and is no longer distributed with Sitecore. (325129)

 

July 07, 2010

Released Sitecore CMS 6.2.0 rev.100701 (Also known as 6.2.0 Update-3).

Please visit the appropriate Sitecore CMS 6 downloads page for instructions describing how to download and install this release.

Change log.

New Features:

• It is now possible to use a custom ribbon when loading the Content Editor application. This makes it easier to reuse the application for other purposes.
  • Custom ribbons should be located in the core database, just like the standard Content Editor ribbon. (326732)
  • Custom ribbons are loaded by specifying a "ri" query string parameter with the item ID of the custom ribbon.
  • A quick way to reuse the Content Editor application is to make a copy of /sitecore/shell/Applications/Media/MediaShop/default.aspx and add the following line (replacing the sample ID with the item ID of the custom ribbon). The second line hides the navigation bar in the bottom of the window so that the user cannot switch to the Content Editor or Workbox:
    url.Add("ri", "{13AD7186-49E8-4605-9286-2059AF2E9A79}");
    url.Add("pager", "0");

Issues resolved:

• Page Editor
  • When creating multiple items in the Page Editor, all items would be created under the same parent. For example when creating an item called "Company" under Home and then trying to create an item called "About" under Company, the item "About" would be created as a child of Home. (322094)
  • The Field Editor escaped single quotes incorrectly. When entering a single quote character in a field in a Field Editor window, the value would be saved back into the field as "-scSQuote,-" instead of the correct character.(320930)
• Security API
  • The system did not check for cyclic role assignments, which could cause the ASP.NET worker process to crash. The system will no longer crash if there are cyclic role assignments. (309080)
  • The system issued duplicate requests to the RolesInRoles provider while resolving access rights to Sitecore items. This may have resulted in unnecessary load on the database containing Sitecore security data. (322685)
• Media requests
  • When the Web client disconnects in process of streaming media data (e.g. the client was disconnected by closing the browser window), Sitecore will no longer write a "Response.Flush attempt failed" error message to the log file. (323138)
• Layouts and renderings
  • Some of the standard Sitecore web controls did not pass parameters (such as Parameters="default-text=No text") to the FieldRenderer. This was a problem in the following controls (328250):
  • sc:Text
  • sc:Link
  • sc:Image
  • sc:Date
• Proxy items
  • When publishVirtualItems was set to "true", the sort order for the virtual items in the web database would be reset during publishing, thus leading to wrong sort order of the items on the web site. (320946)
• Localization
  • A number of phrases could not be translated in the following areas:
    • The Edit User dialog (323013, 323007, 323035)
    • The validation results report. (325016)
    • Field validator messages. (325071)
    • The "Edit" button on the Workflow group of the Content Editor ribbon. (315391)
    • Some strings in the grid control that is used in several applications, such as the User Manager, the Role Manager, the Locked Items dialog, and the Recycle Bin. (330021, 322992, 322993)
  • It is now possible to localize the placeholder names that are displayed in the left pane of the Page Designer by creating a Placeholder Settings item and setting a display name for it.(327801)
• Miscellaneous
  • JavaScript errors would sometimes occur when using the Package Designer, the Device Editor, or the Create Template wizard. (329361, 329950, 329481)
  • When receiving an invalid authentication cookie (which may occur when switching between Sitecore instances in the IIS or when running a load balanced setup where each web application uses different machine keys), Sitecore would sometimes throw a "CryptographicException: Padding is invalid and cannot be removed" error and return a "500 Server Error" response to all requests hitting the web server. The CryptographicException will still be written to the log file to inform about improper configuration, while all requests passing invalid cookies are processed under the context of Anonymous user. (320777)
  • The web.config file contained an obsolete reference to a "sc:feedItem" XSL control. This would cause an error message to be written to the log file whenever Sitecore started. (322896)
  • The /xsl/system/RssRenderer.xslt file was not used by Sitecore and has therefore been deleted. (322896)
  • The Update Package Installation Wizard was failing to install packages with versioned media items correctly. After installation, the media items would be present, but the actual media would be missing for all language versions. (327643)

May 26, 2010

Released Sitecore CMS 6.2.0 rev.100507 (Also known as 6.2.0 Update-2).
This is the current recommended release of Sitecore CMS 6.

Please visit the appropriate Sitecore CMS 6 downloads page for instructions describing how to download and install this release.

Change log.

New Features:

• Analytics:
  • The system is now configured to automatically discard requests that come from robots, based on the user agent strings (the list of user agent strings has been collected from http://iplists.com). Additional user agent strings and/or IP addresses can be configured by modifying the "/App_Config/Include/Sitecore.Analytics.ExcludeRobots.config" file. Custom logic for excluding robots can be implemented by adding additional processors to the new <excludeRobots> pipeline in the Sitecore.Analytics.config file.

Important changes

• The list of recently edited items in the Content Editor is no longer persisted between sessions. This improves the performance of the client when using security providers such as the Active Directory or CRM provider.

Issues resolved

• Analytics
  • The OMS global session cookie which is used to keep track of returning visitors was using an absolute expiration date instead of sliding expiration.
  • When trying to use "SQLServer" session state mode, you would get an exception with the following message: "Unable to serialize the session state".
  • Conditional renderings that were using profile keys in the conditions were not behaving as expect if the profile keys had been updated during the current request.
  • When using the scheduler to automatically sending reports as e-mails, the "Classify" and "Subscribe"/"Unsubscribe" links in the report e-mails did not work correctly.
  • When opening any Analytics report, the navigation controls would sometimes indicate that several pages were available, even if the full report was rendered to the client as one document.
  • The data in the Latest Sessions report did not change after applying a "where" filter, such as "where specific pages was visited".
  • Applying any of the following filters to a report would cause the report to fail with an error message:
    • "where the visitor used browser"
    • "where visitor is from specific city"
    • "where longitude/latitude of the visitor compares to specific value"
    • "where user is from specific region" filter
    • "where visitor is from specific area code"
    • "where the visitor uses specific ISP"
    • "where the visitor came fro referring site"
  • If the Analytics.EMailFromAddress did not contain a valid email address, the system would fail with an error when trying to subscribe to reports. Now, a message will be displayed to the user and an error message will be written to the log file.
• Potential security vulnerabilities
  • If an XSLT error occurred on the site, the error control would reveal stack trace and server paths to any user. The error control will now use the value of the standard .NET customErrors web.config setting:
    • On: Never display XSLT exceptions
    • Off: Always display XSLT exceptions
    • RemoteOnly: Don't display XSLT exceptions for remote requests, only for local request or if the user is a member of the Sitecore Client Developing role
  • The /sitecore/admin/unlock_admin.aspx page is now disabled by default. The page can be enabled by changing the value of a variable in the aspx file, thereby ensuring that only people who have access to modify files on the server can enable the page.
  • The Sitecore login page now uses encryption when storing and retrieving the most recently used user name from the "sitecore_username" cookie.
  • A new "Login.RememberLastLoggedInUserName" setting has been added to the web.config file, since some customers consider it a security vulnerability that we store the user name of the previous logged in user in the "sitecore_username" cookie. If you set this to false, the system will not create a "sitecore_username" cookie during login and the user name field on the login page and change password page will always be blank.
  • A number of Sitecore's XAML controls contained potential cross-site scripting vulnerabilities.
  • The following aspx pages below /sitecore/shell did not require the user to log in: "Validator.aspx" and "SitecoreClientTranslation.aspx".
  • A couple of pages in the /sitecore/admin folder did not require login (ShowConfig.aspx, SizeStatus.aspx, Restore.aspx).
  • Unprivileged authors could get access to a number of applications and dialogs in Sitecore if they knew the URL of the applications. 
  • A number of additional, non-critical security vulnerabilities have been fixed. The customers and partners that have reported these problems have been informed. 
• Editing content
  • The toolbar below inline fields in the Page Editor would sometimes have one or more buttons missing from the toolbar when two nested controls both were adding commands to the toolbar.
  • When using the spell checker button on the Review tab, any changes to the content of rich text fields would be discarded when the item was saved. 
  • The "Remove version" button on the Versions tab in the Content Editor will now be disabled if the user does not have delete permissions to the item.
• Rich Text Editor
  • The upload button in the Insert Sitecore Media dialog box will now be disabled if the user does not have create permissions to the selected media folder.
    Note: This issue was only partially fixed. The upload button is not disabled for the Media Library root item, even if the user does not have write permissions. [Updated June 09, 2010].
  • HTML entities such as "®" entered into the "Edit HTML" view of the rich text editor would incorrectly be converted to "®" if the user saved before switching back "Design". 
  • When a rich text field contained a html entity such as "®", the validation reports would report that the field contains invalid XHTML, although the entity is valid.
• Word Document field
  • Previously edited text from a different item would sometimes be loaded into Word instead of the field value of the current item when editing a Word Document field. 
  • After changing the field type from "Word Document" to "Rich Text", the affected field values would be rendered incorrectly on the website until each item had been edited and saved. The field values are now output correctly as rich text in this situation. 
• Media API
  • A new setting called "Media.MediaLinkPrefix" has been added to the web.config file (together with a related <mediaPrefixes> section below the <mediaLibrary> section. This makes it possible to make Sitecore use different media prefixes than "~/media". 
    • Using a different media prefix such as "-/media" can improve performance when handling media requests. The performance increase might not be significant in all server setups, since it is related to the internal way that IIS and Windows checks security for paths to physical files.
  • When the LinkProvider's languageEmbedding property was set to "always" or "asNeeded", the media API would throw exceptions internally when URLs started with "/~", for example "/~/media". The exceptions would not show up in the Sitecore log file, but could be traced by using tools such as WinDbg.
  • It was not possible to use IIS7 Output Caching for Sitecore media requests due to the media streams being flushed during streaming.
  • Requesting a media item using a non-existing database name in the "db" query string parameter will now redirect to the Not Found page instead of showing an error message.
• Development
  • When specifying key-value pairs in "Additional Parameters" for a rendering or a sublayout in the Control Properties window, the parameter values would be encoded instead of being saved as-is, thus preventing developers from specifying HTML tags or text containing HTML special characters in parameter values.
• Security API and security applications
  • The performance of the Security Editor and Access Viewer has been improved in IE8.
  • The load time for the User and Role Manager has been improved by avoiding a redundant call to the security provider when loading the grid.
  • Domain names were treated as case sensitive when logging in to Sitecore.
  • The login page will no longer transfer the webroot path to Sitecore as a query string parameter when loading the SDN page with browser information.
  • When creating a new user, a misleading error message would be displayed in the dialog box if no email address was provided.
  • After creating a new user, the User Manager would sometimes display an incorrect total number of users in the footer. This problem was reintroduced in 6.2.0 rev. 091012 and has now been fixed in a different way.
  • Searching in the User Manager would sometimes display an error message when using the Active Directory provider or custom security providers.
  • The number of calls to the security providers has been reduced by no longer persisting the list of recently edited items in the Content Editor between sessions. This improves the performance of the client when using security providers such as the Active Directory or CRM provider.
  • The performance of the User Manager has been improved for non-Administrator users. The API is now using paging when retrieving the list of users that non-Administrators have access to work with.
  • Trying to create or edit users from domains that are handled by the Active Directory provider or custom security providers would sometimes cause the User Editor to fail with an error message.
  • The SwitchingProfileProvider was distributing calls to GetPropertyValues and SetPropertyValues to all security providers, which would sometimes result in wrong properties being returned or set. The provider will now only distribute calls to the provider that handles the user's domain.
  • Custom user properties were always being serialized and saved into the SerializedData property, resulting in unnecessary calls to the security provider when none of the custom properties had been modified.
  • The API was sending unnecessary requests to membership providers when searching for users. The API will now check if the membership provider handles a specific domain before asking the membership provider for users in that domain.
• Miscellaneous
  • The Settings class contains a "DataProviderTimeout" property which can be changed by adding a "DataProviderTimeout" setting to the web.config file (it is not present by default). Adding this setting would, however, cause the ASP.NET worker process to crash due to infinite recursion. 
  • Some of the background jobs that update links in Sitecore would be run with Thread.CurrentPrinicipal set to "sitecore\Anonymous" instead of the user that initiated the background job. This could result in the "Update by" field being set to the anonymous user instead of the user who for example moved or renamed an item. 

January 20, 2010

Released Sitecore CMS 6.2.0 rev.100104 (Also known as 6.2.0 Update-1).

This is an old update. We advise to use the recommended release.

Please visit the appropriate Sitecore CMS 6 downloads page for instructions describing how to download and install this release.

Change log.

New Features:

• A new <filterItem> pipeline has been added.
  • This pipeline can be used to override how item filtering works when running in Live Mode.
    Notice that the pipeline is only meant for site-level and/or language-level filtering and cannot be used for situations where you for example want to return different results based on the current user (due to the way the results are being cached in the FilteredItemsCache)

Improvements:

• The performance of the Content Editor has been improved. This is most notable for editors who have low bandwidth.
• The Health Monitor now outputs the instance name for each counter in the Sitecore log file to make it easier to correlate the log files with the output from Performance Monitor.
• The Health Monitor now supports monitoring the Sitecore-specific performance counters in addition to the Windows and CLR performance counters.
  • When adding Sitecore performance counters to the HealthMonitor, you must specify instanceType="Sitecore". For example:
    
    <counter category="Sitecore.Caching" name="CacheMisses" instanceType="Sitecore"/>
• When reverting serialized users, the password will no longer be reset to the default password for exisiting user account. The user account will simply be updated with the serialized information instead of being deleted first.

Important changes:

• API changes
  • The PublicFeed.GetRssDevice() method was not used and has been removed.
• The Health Monitor now requires you to specify an instanceType when defining which performance counters that should be monitored in order to differentiate between different types of performance counters.
  • The possible values for the instanceType parameter are "Windows", "CLR", "Sitecore". Examples:
    
    <counter category="Process" name="Private Bytes" instanceType="Windows" />
    <counter category=".net CLR Memory" name="# Bytes in all Heaps" instanceType="CLR" />
    <counter category="Sitecore.Caching" name="CacheMisses" instanceType="Sitecore"/>

Issues Resolved:

• Analytics
  • The session report would show a blank histogram for profiles that were using the "Average" type.
  • A number of reports have been updated to escape HTML in URLs. This has been changed in order to avoid potential cross-site scripting vulnerabilities.
  • After duplicating a campaign, an exception would sometimes occur the first time the user saved any changes to the duplicated campaign events.
  • The Analytics Reports were compiled every time they were rendered, which would slowly use up more and more memory since compiled reports are newer released from memory. Now, reports are only recompiled after they have been changed.
  • Timestamps in the PageEvent table were saved in UTC instead of using the server's time zone.
  • The SubmitTestVariables.SubmitTestVariable() method called the InsertMultiVarianceTestVariableCampaignEvent with the parameters in the wrong order.
  • Campaign events and Multivariate test variables were not registered in the Analytics database – even if the definitions existed in the Sitecore database. Now, Sitecore will copy the definitions to the Analytics database in such cases and correctly register the events.
• Editing content
  • Line feeds were lost from Multi-Line Text fields if the item were saved when showing raw values in the Content Editor.
• IE8
  • IE8 (with the latest Microsoft updates installed) would sometimes crash when accessing various types of fields when the item was protected or if the user did not have write access to the field. This applied to security fields, iframe fields, and rich text fields.
  • When using IE8, you would sometimes experience slow performance and high CPU load when using the Security Editor and Access Viewer.
• RSS Feeds
  • The RSS Feed Design dialog would present the user with an error message if the item had presentation details assigned and a __Standard Values item already existed for the associated template.
  • If you specify a source on a feed definition item which is not a path or an item ID, the PublicFeed.GetSourceItems() method will try use Sitecore query instead. In such cases, a warning message is now output to the log file. To avoid the warning, you should prefix such sources with the "query:" prefix.
• Security API and related applications
  • The Select Account dialog box now uses server-side paging, making the dialog faster to open even when the system contains large amounts of users or when using the AD or CRM security providers.
  • With read-only databases, you would sometime experience an InvalidCastException when the system tried to access the IsAdministrator property for the current user.
• Development
  • XSLT renderings would work with the latest version of the current item, even when Sitecore.Context.Item had been set to a previous version.
  • Programmatically changing the Context.Device in the HttpRequestPipeline did not work as expected. The assigned Context.Device would be ignored when Sitecore later resolved the layout.
  • The following methods in the WorkboxForm class has been made "protected virtual" to make the class easier to override: DisplayWorkflow(), DisplayStates() and DisplayState().
  • The RenderField pipeline did not process rendering parameters such as “default-text” and “show-title-when-blank” correctly, causing such parameters to be ignored when specifying them in the Parameters attribute of a FieldRenderer web control. [Added May 11, 2010]
• Installation
  • The setup.exe registered the Sitecore performance counter categories incorrectly.
• Oracle support
  • When using the setup.exe to install on Oracle, the installation would fail if the Oracle client selected in Sitecore did not correspond to the one in the path.
  • The setup.exe would always use "Data Source=XE" in the ConnectionStringsOracle.config file, even when a different Oracle instance name was specified as part of the installation.
  • The setup.exe no longer fails if SQLPlus is not present on the target system.
• Miscellaneous
  • The Favorites and Links buttons in the ribbon did not work.
  • The Health Monitor would sometimes throw an exception when trying to update the system's performance counters after one or more running sites on the server had been restarted or stopped.
  • The MemoryMonitorHook would sometimes report an InvalidOperationException and fail to load on content delivery servers without a 'core' database.
  • The dialog box workflow comment dialog box will now display a warning to the user if the maximum comment length of 2.000 characters is exceeded.
  • The login page no longer transfers an "iisname" query string parameter to the iframe that displays "Browser Notes" from SDN.
  • A potential cross-site scripting vulnerability has been fixed on the notfound.aspx page.
    Sitecore Corp. wants to give credit to SEC Consult for the discovery of this vulnerability and for their cooperation.
• Changes to the web.config and other configuration files
  • A new <filterItem> pipeline has been added.
  • An instance type is now specified for each performance counter that the Health Monitor watches.

 

November 10, 2009

Released Sitecore CMS 6.1.0 rev.091029 (Also known as 6.1.0 Update-3).

This is an old update. We advise to use the recommended release.

Please visit the appropriate Sitecore CMS 6 downloads page for instructions describing how to download and install this release.

Change log.

New Features:

• Analytics:
  • It is now possible to retrieve the global session record for a specific user from the Analytics database using the newly introduced AnalyticsManager.GetGlobalSessionIdByCookieValue(string cookieValue) method which returns a GlobalSession object.
  • It is now possible to update the global session record in the Analytics database using the newly introduced AnalytcisManager.UpdateGlobalSession(GlobalSession globalSession) method which returns the number of database records affected.

October 21, 2009

Released Sitecore CMS 6.2.0 rev.091012 (Initial release).

This is an old update. We advise to use the recommended release. 

Please visit the appropriate Sitecore CMS 6 downloads page for instructions describing how to download and install this release.

Change log.

New Features:

• Sitecore client RSS feeds for items in workflows
  • Content item feeds allow editors to subscribe to any changes that are made to an item in Sitecore, as long as the item is subject to a workflow.
  • Workflow feeds allow editors and managers to subscribe any changes that are made to items in a specific workflow or workflow state.
  • For more information, see the "Content Author's Cookbook", the "Client Configuration Reference" and the "Content API Cookbook".
• Built-in support for syndicating items using the RSS format.
  • This feature is described in the "Content Author's Cookbook", "Presentation Component Cookbook", and the "Content API Cookbook".
• WebDAV support in the media library
  • When WebDAV is configured, editors can take advantage of Drag and Drop media management in the media library, as well as editing files directly on the server. (Internet Explorer only)
  • Editors will typically need to change their browser's configuration to be able to use the WebDAV feature, as described in the "Configuring Internet Explorer Reference" which contains mandatory client configuration instructions.
  • It is strongly recommended to read the documentation, before deciding whether to use WebDAV or not. WebDAV support has some limitations, such as IE8 not supporting WebDAV for localhost and WebDAV requiring the application to use <authentication mode="None"> in the web.config file.
  • WebDAV requires the IIS to be configured according to the IIS version and operating system, as described in the WebDAV documentation.
  • For more information, see the "WebDAV Configuration" and the "Content Author's Cookbook" documents
• A new File Drop Area field type has been introduced
  • File Drop Area fields can be used to attachment media and files to the current item using Drag and Drop (requires WebDAV to be configured).
  • Sitecore will release a shared source component for rendering File Drop Areas on the website.
• A new Word Field has been introduced
  • Word Fields allow editors to edit content using Microsoft Word. The typical use case is to use Word Fields as an alternative for rich text fields when editing content on intranet solutions.
  • You must have Microsoft Word 2007 installed on your computer to edit Word Fields in Sitecore.
  • Word Fields are only supported on Internet Explorer 7 and later and requires installation of an ActiveX the first time a Word Field is edited. Please refer to the "Internet Explorer Configuration Reference" which contains mandatory client configuration instructions.
  • Notice that the HTML is generated by Word and will not be valid XHTML. Cleaning the HTML can be done by adding custom processors to the <word.parseDocx> pipeline.
  • Limitations: Some advanced features in Word are not supported or the resulting output might differ from the Word document, such as using columns, text boxes, cross references, page background colors, etc.
  • For more information, see the "Content Author's Cookbook".
• Analytics
  • Support for OMS on Oracle.
  • A new sampling feature makes it possible to configure the system to only collect data for a percentage of visitors. This can be useful on sites with huge amounts of visitors. The feature is configured with the new "Analytics.Sampling.Percentage" setting in the Sitecore.Analytics.config file.
• Improved IIS7 support
  • Sitecore can now run in IIS7 application pools that are using the "Integrated" pipeline mode without applying any workarounds. At the same time, most of the known issues related to "Integrated" pipeline mode have been resolved (except from one related to using custom login pages).
• Sitecore's theme icons are now stored in zip-files.
  • To reduce the number of files in a Sitecore installation, Sitecore's theme icons are now stored in zip-files (one zip-file for each top-level folder). Only the icons in use will be extracted and cached in the /temp folder.
  • The result of this change is faster installation and less time spent on file operations when copying or moving Sitecore installations. However, starting the Sitecore client and applications for the first time will take slightly more time while the icons used by Sitecore are extracted and cached to disk.
  • If you have hard-coded references to icons in your code or CSS, you must update these references to use the new ~/icon prefix (for example "/~/icon/Applications/16x16/businessmen.png") or extract these icon files to disk.
• Sitecore is now distributed with a number of icons that are having a Windows 7-look instead of an XP-look.
  • The icons are located in the zip-files that use a "V2" suffix (such as "ApplicationsV2.zip"). Icons that are similar to the existing icons use the same file names as the existing icons (such as "businessmen.png").

Improvements:

• Installation
  • A new "Simple" installation mode is available for making an installation with the typical settings, using Microsoft SQL Server as the database provider.
  • A number of issues in the setup.exe installation program have been resolved.
• Analytics
  • Clicking subscribe/unsubscribe in reports no longer work as a toggle. Instead, If you click subscribe multiple times for the same company in the same report, you will now get the option of unsubscribing or staying subscribed.
• The configuration of the SQL Server databases in the clean distribution has been changed to follow best practices
  • The default compatibility level is now set to SQL Server 2005 instead of 2000.
  • Some of the databases contained consistency errors related to table usage.
  • Auto Close and Auto Shrink are now set to "False" for all databases by default. Notice however that SQL Server Express editions have their default value for Auto Close set to "True" and will set this value for newly attached databases which requires you to manually set it back to "False".
  • ALLOW_PAGE_LOCK is now set to ON for all indexes in all databases, making it possible to rebuild indexes using maintenance plans.
  • The databases no longer contain two users called 'sdn' and 'sitecore'.
• Development
  • The Template Builder no longer resets the sort order of fields and fields sections. It only assigns a new sort order to fields and field sections that have been moved, all other fields and field sections maintain their original sort order.
  • The ChildList class now implements IEnumerable<Item>, making it possible to iterate over ChildLists using LINQ.
  • The IDTable class has a new GetKeys(string prefix) method which allows you to retrieve all IDTable entries associated with a prefix. This is useful for cleaning up obsolete or unused entries.

Important Changes:

• Installation
  • For now, the setup.exe does not support configuring the system to use SQLite. If you want to use SQLite, you must perform a manual installation using the zip-archive or install using SQL Server and then reconfigure the solution to use SQLite.
• Renamed files
  • The /App_Config/Security/Domains.config.xml file has been renamed to Domains.config to prevent the files from being accessed in clear text.
  • The /App_Config/Security/GlobalRoles.config.xml file has been renamed to GlobalRoles.config to prevent the files from being accessed in clear text. 
• The /indexes folder has been moved
  • The /indexes folder is now by default located below the /data folder instead of the webroot. This is recommended to avoid potential security issues, but also solves a problem where IIS7 might restart during package installation or index rebuilding.
• Breaking API changes
  • The data layer of the Analytics API has been changed to support OMS on Oracle and is now using providers to access the database. This has introduced a number of breaking API changes, including removing the built-in support for LINQ, since LINQ to SQL is not supported for Oracle database.
  • Also, a number of smaller breaking changes have been introduced into the Analytics API to make it more consistent, such as renaming AnalyticsManager.GetSession(aspNetSessionId) to AnalyticsManager.GetSessionByAspNetSessionId(aspNetSessionId).
  • The Sitecore.Kernel.dll contained a Sitecore.Linq namespace and a Sitecore.SitecoreDataContext class which have now been removed. The LINQ support was experimental and could not be used in CMS 6, since it referred to non-existing schemas and tables.
  • The Authentication.TicketTimeout setting has been deprecated. Use Authentication.ClientPersistentLoginDuration instead.
• Important changes to the default web.config settings
  • By default, Sitecore is now configured to use <authentication mode="None"> in the web.config file. This is required for WebDAV to work correctly. The WebDAV functionality will not work if using the "Forms" authentication mode.
  • The default ItemNameValidation has been changed to enforce item names that are valid when using WebDAV.
• Analytics: Campaign reports
  • The campaign reports have been changed so that campaigns and related goals are only counted/listed when triggered on the first page request in a session. Subsequent visits in the same session to pages that have associated campaigns will not be counted as a campaign visit.
• User Manager
  • The performance of the User Manager has been improved again after 6.1 Update-1 had removed a previous optimization.  This fix will, however, re-introduce the problem that the User Manager in certain situations, for example after creating a new user, will display an incorrect total number of users in the footer.

Issues resolved: 

• Analytics
  • Most of the templates related to Analytics now use a $name token so that the "Name" or "Header" field automatically will be filled out when creating a new item.
  • Most of the reports would have broken data sources inside the report after saving them, due to an error in the Report Designer which strips line breaks instead of converting them to whitespace.
  • The various reports that have a "Classify" link or which filter by classification was only taking classification by Business into account, not classification by IP Address, DNS, User Agent or This Visitor.
  • The campaign-related reports would sometimes give an incorrect count of campaigns and subsequently triggered goals. Now, campaigns are only counted/listed when triggered on the first page request in a session. 
  • The subscription task background job would sometimes fail after one or more users had subscribed to any sessions.
  • Events, goals and profile key values were not inserted into the Analytics database if the database had been reset – even if the definitions existed in the Sitecore database. Now, Sitecore will copy the definitions to the Analytics database in such cases and correctly register the events.
  • In the Marketing Center, the insert options for "/Marketing Center/Personalization/Predefined Conditions" now contain the "Conditional Rendering Rule" template instead of the "Rule" template.
• Editing content
  • All Sitecore client users had access to change the insert options for items and templates by clicking the name of the "Insert" chunk in the ribbon. This link is now only available for users who has access to the Assign Insert Options dialog from the "Configure" tab.
  • The Sitecore Client Authoring role was allowed to insert from template. Now, only Administrators and members of the Sitecore Client Maintaining role will have access to this option.
  • After deleting an image in the media library and choosing to update all references to point to a different image, any references to the deleted image inside rich text fields would not be replaced with the new image.
• Page Editor
  • You no longer need to save the page after inserting an image into an image field before you can open the Image Properties dialog.
  • Trying to open the Image Properties dialog when working in a non-English content language would sometimes display an error message stating that the item could not be found, even when the field referenced a valid image. 
  • The Image Properties dialog displayed the Default Alternate Text in English, even when using a different content language.
  • When inserting images into the rich text fields, the ALT text from the Media Library was taken from the client language, not the content language.
• Preview
  • When opening Preview from the Presentation tab in the ribbon, the preview window would sometimes not reflect the most recent changes to the item.
  • Trying to switch the preview device could result in an error message being displayed at the top of the page instead of the ribbon.
  • After logging out of the Preview client and from the login page manually typing an item URL such as http://localhost, you would sometimes be redirected back to the login page again.
• Publishing
  • When executing Publish Single Item on an item that had not yet been published, the item's subitems would be published as well.
• Media Library and media requests
  • Handling media requests using the 404 handler did not work as expected due to the target media item not being resolved correctly.
  • Sitecore was sending unnecessary requests to the database in relation to media items and blobs, leading to unnecessary database roundtrips and a small performance overhead even on a fully cached site. Calls to SqlServerDataProvider.BlobStreamExists() are now cached.
• Localization
  • Some of the Content Editor warnings could not be translated.
  • A couple of typos have been fixed.
• Security API and related applications
  • Roles assigned to a virtual user were persisted between sessions. This has been fixed, but roles will still be persisted for the same session, even when creating a new virtual user.
  • Roles assigned to a virtual user could not be removed again.
• Development
  • The "Links" panel in the ribbon did not show referenced and referred items for templates.
  • Changing the field type of a template field would not take effect until Sitecore was restarted.
  • A JavaScript error would occur in the Debugger when trying to show or hide the ribbon. 
  • When using Integrated pipeline mode with IIS7, the Debugger would sometimes not start. Instead, the website was opened and an error message written to the log file. Now Debug works correctly.
• Miscellaneous
  • After deleting an item, the item information was not removed from the Lucene search index.
  • The usage count for templates was not decremented when deleting items based on the template.
  • The insert options for "/sitecore/system/Settings/Rules/Item Deleted/Rules" and "/sitecore/system/Settings/Rules/Version Removed/Rules" now contain the "Rule" template instead of the "Insert Options Rule" template.
• Changes to the web.config and other configuration files
  • A number of pipelines have been added in relation to the new features in this release.
  • A number of pipeline processors have been added to existing pipelines to resolve issues and to support new features.
  • A new customHandler has been added for serving RSS feeds.
  • A number of httpModules and httpHandlers have been added to support WebDAV and RSS feeds.
  • An httpAuthentication section has been added for use with the WebDAV feature.
  • Several new web.config settings have been added.
  • A number of new commands have been added to the Commands.config file.
  • Two new field types have been added: Word Document and File Drop Area.
  • For the full list of configuration file changes, please refer to the "web.config changes" page on SDN.
• The clean installation
  • The Sample Item template now use a $name token, so that the Title automatically will be filled out when creating a new item based on the template.
  • The default "Sample Rendering.xslt" file contained a for-each loop outputting the names of the subitems. This for-each loop has been removed.
  • The "/sitecore/shell/Security templates.xml" file is obsolete and has been removed from the clean installation.
  • The /sitecore/admin folder contained a number of files for internal Sitecore usage. These files are no longer present in the clean installation: CompareSubtrees.aspx, DumpIndex.aspx, Reflect.aspx, SizeTester.aspx, UnitTestLogin.aspx, UnitTestCacheClear.aspx.

September 4, 2009

Released Sitecore CMS 6.1.0 rev.090821 (also known as 6.1.0 Update-2).

This release is no longer recommended. Please upgrade to the recommended release.

Please visit the appropriate Sitecore CMS 6 downloads page for instructions describing how to download and install this release.

Change log.

New Features:

• Analytics
  • Added support for specifying a custom sort order for Page Events when registering them using the API. If you intend to use custom sorting, you should generally provide a custom sort order for all relevant events (on a page request basis) to make them show up in the correct order. 

Improvements:

• The performance of the DatabaseCrawler which updates the search index in the background has been improved. This is most notable for solutions with many languages and/or many versions in each language.  

Issues resolved: 

• Analytics
  • Some of the reports, such as the "Latest Human Sessions" report would open as a blank report in the Report Designer.
  • Profiles and profile keys were not registered properly until the .NET worker process was restarted.
  • The Analytics reports would display error messages when using the "Random" multivariate test strategy.
  • The Campaign summary report would sometimes show a horizontal scrollbar, but scrolling to the right would not bring the toolbar buttons into view.
  • The names for the Marketing Center and Sitecore Analytics applications were wrong in several client languages, except Danish and English. 
• Editing content
  • Users that were logged in to the stand-alone Content Editor interface and who were inactive for long periods of time would sometimes not be able to log off from the Content Editor interface or use the Publish Site/Publish Item buttons.
• Page Editor and Preview
  • After renaming an item in the Page Editor, you would sometimes get a “The requested document was not found” error message.
  • After logging out of the Page Editor, you would sometimes get a “The requested document was not found” error message.
  • Sometimes changes to text fields would not be saved in the Page Editor when the user had started to edit the field by making a text selection and then starting to type.
  • Switching from Preview to the Page Editor could result in various problems, including inline editing not being available, green content dots disappearing and the Design pane throwing an exception. The problems were related to the user context being reset to extranet\Anonymous.
  • A JavaScript exception could occur in the Page Editor when nesting editable fields inside a link in XSTL, for example when using a construct like <sc:link field="Link"><sc:text field="Title"/></sc:link>.
• Security API
  • AccessResultCache was not cleared automatically after changing the ownership of an item.
  • IsUserInRoleCache was not cleared automatically after removing a role from a user.
• Media requests
  • An exception might appear in the Sitecore log files for media requests when the Web client disconnected in process of streaming media data or during high server load.
    Notice: This issue was not completely resolved, and is still reproduced under certain circumstances. See the known issue for more information. [Added March 12, 2010]
  • Media requests would sometimes fail due to the browser sending an invalid "If-Modified-Since" header.
• Search
  • An error could occur when using the Quick Search and the search string contained escape characters.
  • Using Index.Search(searchString, database) to perform Lucene queries no longer worked as intended because the Search method incorrectly closed the searcher. Notice that using Index.Search is not recommended in solutions that might experience heavy load. Instead, it is recommended to instantiate your own IndexSearcher and to close it when done).
• Update Installation Wizard
  • The Update Installation Wizard no longer requires .NET 3.5 SP1 to be installed.
  • Analyzing an update package would sometimes show different messages than when installing the package.
  • In certain circumstances, not all files and subfolders would be backed up when an update package contains instructions for removing a folder.
  • When installing packages that change a field from "versioned" to "shared" into a solution where the field is already "shared" could cause the contents of the field to be removed.
• Localization
  • The "Rules" field will now display the defined rules in English as a fallback if the rule names have not been translated to the current client language.
  • The "Create a New User" and delete confirmation dialogs contained phrases that could not be translated.
• Miscellaneous
  • An error would sometimes occur on the login page if Sitecore was running in an application pool that is configured to use IIS7 Integrated pipeline mode.
  • The Factory.GetDatabase(string) method returned null when an invalid database name was supplied, despite the method having a [NotNull] signature.
  • Custom code inserted into sublayouts using <% %> would no longer work after saving the sublayout in the Developer Center.
  • Duplicate instances of Sitecore caches would sometimes be created after changing files in the /App_Config folder. This would in certain circumstances lead to out of date field values being returned from the API.
  • During high server load, the Content Editor may sometimes receive the error message "Multiple controls with the same ID were found".
    Notice: This issue was not completely resolved and may still occur in some circumstances. See the known issue for more information. [Added May 25, 2010].
  • Out of memory issues could occur during heavy load due to Sitecore’s file watchers creating redundant threads each time a new HttpModule was being initialized.
  • Sitecore's file watchers did not increment the ThreadingCounters.BackgroundThreadsStarted performance counter.

August 6, 2009

Released Sitecore CMS 6.1.0 rev.090722 (also known as 6.1.0 Update-1).

This release is no longer recommended. Please upgrade to the recommended release.

Please visit the appropriate Sitecore CMS 6 downloads page for instructions describing how to download and install this release.

Change log.

Improvements:

• Analytics
  • The session report has been modified so that if a page event text is available, the event name will no longer be appended in the output, giving more control over the text displayed in reports.
  • It is be possible to use the <sc:VisitorIdentification runat="server" /> web control without having to manually register it in each layout file.
  • Newly created layouts will now contain a <sc:VisitorIdentification runat="server" /> web control by default.
  • Profile values associated with a goal will now be used to update the user's profile when the goal is triggered.
  • Two new method overloads are available in the AnalyticsPageExtension namespace for registering events for form fields changes and form submissions.

Issues resolved:

• Editing content
  • The DatePicker would sometimes throw an exception when the user's regional settings were set to "en-US".
  • When editing an internal link, the Insert Link dialog box would open with the Home item selected instead of the item currently being linked to.
  • After executing a workflow action on an item, the security permissions for that item would sometimes be resolved incorrectly.
• Page Editor and Preview
  • Publishing restrictions would not be taken into account when using the Preview client in a multisite solution.
  • When creating items using the Page Editor, a version would be created in the client language instead of the current content language.
  • The Page Editor did not save modifications to a field if the new field value in the content language was equal to the current field value in the client language.
  • When deleting an item with subitems in the Page Editor, a "Do you want to refresh the page" dialog would be displayed multiple times.
  • Switching to Preview or Debug from the Page Editor would sometimes lead to a "Requested document not found" error in the iframe containing the Page Editor ribbon.
  • When editing Multi-Line Text fields in the Page Editor, embedded newlines would be removed when saving the page.
• Analytics
  • Newly added goals would not be tracked until the ASP.NET process had been restarted.
  • The session report did not sort events by timestamp.
  • When multiple events were triggered for the same request, they would sometimes be registered with the same timestamps.
  • The names for the Marketing Center and Sitecore Analytics applications were wrong in the Danish language.
  • A sample connection string has been removed from the "AuthoringFeedback.mrt" report file.
  • When clicking "Save" on a report, some of the file format names were truncated.
• User Manager
  • The Edit User dialog could not be closed if the User template contained one or more read-only properties, even if nothing was changed in the dialog.
  • Read-only properties in the Edit User dialog were not disabled for editing.
  • After creating a new user, the User Manager would sometimes display an incorrect total number of users in the footer.
  • Restoring serialized users would not restore all the roles assignments.
• Development
  • When creating a new template, a version would be created in the client language instead of the currently selected content language.
  • When using the Developer Center to insert web control on a layout or sublayout, duplicate "xmlns:sk" (or similar) attributes would sometimes be added for the control.
• Media
  • An error would occur when uploading a file if the filename contained dashes and had the same length as a GUID.
  • An error would occur if requesting a media item if the filename contained dashes and had the same length as a GUID.
• Miscellaneous
  • Virtual users would not retain their properties and roles between requests.
  • The system would sometimes try to parse normal dates as iso dates, leading to error messages such as " Error in 'IsoDateToDateTime'. Input: 4/7/2008" in the log file.
  • When filterItems was set to "false" for a site definition, code executed in that site context would sometimes return items from the master database instead of the database associated with the site.
  • The HealthMonitor would sometimes throw an exception when trying to update the system's performance counters after one or more running sites on the server had been restarted or stopped.
    Notice: This issue was not completely resolved, and is still reproduced under certain circumstances [Added October 7, 2009].
  • The Update Installation Wizard no longer hides the "Existing packages" field when the file upload field is non-empty.

June 30, 2009

Released Sitecore CMS 6.1.0 rev.090630 (also known as the initial 6.1.0 release).

This release is no longer recommended. Please upgrade to the recommended release.

Please visit the appropriate Sitecore CMS 6 downloads page for instructions describing how to download and install this release.

Change log.

New features:

• Online Marketing Suite support
  • Sitecore 6.1 adds support for the Sitecore Online Marketing Suite. Notice that some of the application icons like "Marketing Center" and "Sitecore Analytics" will be visible for Administrators, even when Analytics is not installed or enabled.
• Page Editor
  • The Page Editor now supports inline editing when using Firefox 3.
  • A new Field Editor application is available as a part of the Page Editor, allowing developers to make one or more fields editable in a pop-up window using the familiar Content Editor interface.
  • A new Edit Frame control is available for use in the Page Editor. Edit Frames allow developers to create actions related to a region of the page and can also (when used with the Field Editor) be used to make complex field types such as Multilists and Droplist editable in the Page Editor.
• Development and extensibility
  • A new Rules engine has been introduced. By default, the engine is used by Sitecore for conditional renderings, conditional insert options and some conditional item event handlers.
  • It is now possible to create templates that are used when editing parameters for renderings and sublayouts. All the standard Content Editor controls can be used.
  • It is now possible for the developer to specify on a rendering or sublayout that the "Control Properties" window should be opened after a user adds the control using the Page Designer or Presentation Details.
  • A new <getQueryState> pipeline allows developers to programmatically disable or hide any button or panel in the Content Editor ribbons without having to override the individual commands.
  • A new <getPlaceholderRenderings> pipeline allows developers to filter the renderings to be shown in the "Associated Renderings" dialog. Also, it is possible to change the application used for selecting renderings.
  • The <sc:date> xsl control and the associated DateRenderer class now supports a "culture" parameter to render dates using a specific culture, such as "en-US".
• Serialization
  • It is now possible to serialize and revert users, roles and domains.
  • The serialization API now raises events when creating or deleting files and folders on disk. The events are named "serialization:filecreated" and "serialization:filedeleted".
• Miscellaneous
  • A new Update Installation Wizard is included in Sitecore 6.1 for installing future product updates.
  • The Sitecore login page now has a "Remember me" checkbox.

Improvements:

• The Sitecore login screen has been redesigned to make it easier to use.
• The visual style of the /sitecore/admin/serialization.aspx and /sitecore/admin/login.aspx page has been updated.
• Performance of security providers has been improved by caching profile properties and the results of User.IsUserInRole() calls.
• The client has been updated with Danish translations.
• If the MailServer web.config setting is blank, Sitecore will now use the standard ASP.NET settings (typically specified using the <mailSettings> element in the web.config file).   

Issues resolved:

• Security API and related applications
  • Restricting access to the Desktop application was only enforced on the login page, not when the user typed /sitecore after being logged in.
  • Users in locally managed domains can no longer configure or delete global roles.
  • Users in locally managed domains can no longer see users from other locally managed domains.
  • Field permissions could not be denied by denying inheritance for one or more roles.
  • The Security Editor would sometimes show an error message when applying security to virtual items or their source.
  • The SwitchingMembershipProvider would sometimes wrap a user twice, making it more challenging to write custom membership providers.
• Page Editor
  • Improved flow for creating new content. An "Insert" button is now available in the Page Editor toolbar for all users, both when browsing the site and when editing pages.
  • The Page Editor no longer locks items that are being edited by members of the "sitecore\Sitecore Minimal Page Editor" role. If one or more items are locked when the user attempts to save, a warning message will be displayed.
  • The Calendar pop-up used will now display time in AM/PM format (depending on the editor's regional settings in Sitecore).
  • The Page Editor would sometimes save the default text "[No text in field]" into the field value when editing items with empty fields.
  • The default text "[No text in field]" will be displayed in the page language, not the client language.
  • The <sc:link> xsl control will now display "[No text in field]" if the link field is empty. This is only supported when using the <sc:link … /> syntax, not when embedding text or tags inside a <sc:link></sc:link> tag.
  • The Description field on sublayouts and renderings is now versioned, making it possible to translate the text that is displayed when adding renderings and sublayouts.
  • Command Templates were not executed when using the Insert dialog in the Page Editor.
  • It is no longer required to add a definition for a custom field type to /App_Config/FieldTypes.config for the associated WebEditButtons to be displayed in the Page Editor.
  • The QueryState method is now called for edit frame buttons, making it possible to hide such buttons programmatically.
  • Clicking the text of date field when in edit mode would sometimes result in a JavaScript error on the page.
• Page Designer
  • The Page Designer would display some buttons and controls in the site language, not the client language.
  • If a placeholder contained a single presentation control, it was not always possible to remove the control.
  • If a rendering was associated with a placeholder using the "Placeholder" field on the rendering definition item, it would not show up in "Associated Controls" for that placeholder in the Page Designer.
• Media Library and media links
  • The hostname was not included in media links, even when alwaysIncludeServerUrl was set to "true" on the linkProvider definition in the web.config file.
  • The "Media.UploadAsVersionableByDefault" web.config setting was not always enforced when uploading files to the media library.
  • Image fields which pointed to an invalid media path were not always reported as broken links.
  • The Media Manager no longer show hidden folders and hidden media items.
  • When downloading or detaching the file associated with a media item, the media associated with the latest version would always be downloaded or detached.
  • Cancelling media uploads by calling args.AbortPipeline() in the uiUpload pipeline was not working.
  • Setting the "Media.MaxSizeInDatabase" web.config setting to a non-integer value resulted did not work. Such values are now parsed correctly, but the fractional part will be ignored.
• Preview
  • Publishing restrictions would sometimes be ignored when using Preview in a multisite solution.
• Publishing
  • In certain circumstances, the descendants of items in workflows would not be published when using incremental publish.
• Oracle Data Provider
  • Calling Item.Duplicate() could result in an error message when using the Oracle Data Provider.
• Extensibility
  • Several methods in the WebEditRibbonForm class have been made protected virtual to make it easier to override the class.
  • It is now possible to inherit from and override the following classes in the Sitecore.Xml.Xsl namespace: DateRenderer, ImageRenderer, InternalLinkRenderer, LinkRenderer, LinkUrl, MediaUrlParameters.
• Dependencies on the "website" site
  • After deleting an item in the Page Editor, a "Page not found" error would be displayed if no "website" site existed.
  • The Preview and Page Editor buttons would not be available in the Page Editor if no "website" site existed.
  • The treecrumb in the Page Editor would not work correctly if no "website" site existed.
  • Trying to preview an item from the Content Editor would result in a "Document not found" error if no "website" site existed.
• Miscellaneous
  • Log files would sometimes be reused after the ASP.NET process had been restarted, making it difficult to examine log files. Now a new log file with a timestamp will always be created when an old log file exists.
  • A "License not found" error would occasionally be displayed to the first requests after the ASP.NET process had been restarted.
  • Updating the Lucene index would sometimes fail during high server load, with an error message about the index files being used by a different process.
  • Package installation would sometimes fail on the first attempt without logging any errors in the log file.
  • The performance counters used by Sitecore would display aggregated values for all running Sitecore instances, making it difficult to correctly monitor values like memory usage.
    Notice: This issue was not completely resolved, and is still reproduced under certain circumstances [Added October 7, 2009].
  • The debugger did not work for extranet users, even if they were member of the appropriate Sitecore Client roles.
  • The <sc:image> xsl control would sometimes output parameters in the image URL (href) that were not explicitly specified on the <sc:image> tag.
  • Developer Center: When using the "Code" view, CTRL+S didn't save the changes.
  • Missing templates would not always be reported in the log file.
  • When creating items from the "Insert" drop-down menu (not the panel itself), an empty Context.Items collection would be passed to the Execute method of the command.
  • Commands associated with Command Templates would sometimes be executed twice when inserting items based on such a branch.
  • The WebUtil.ParseUrlParameters method has been corrected to parse URL encoded strings like "First&Second=1" into two entries "First" and "Second=1" instead of a single entry.
  • The Page Editor and Developer Center were referring to an non-existent JavaScript file, causing "File does not exist" application error messages to be reported in the log file when running Sitecore using Visual Studio's built-in web server.
  • IE6:Exporting a language and downloading it could result in an invalid language file being downloaded.
  • In the core database, navigating to /sitecore/template/System and other template folders would result in an error message being displayed.
  • The Package Designer no longer saves a "debug.txt" file in the /temp folder when the application is opened.
• Changes to the web.config file
  • Event handlers and pipeline processors related to the Rules engine and Field Editor have been added.
  • Pipeline processors related to item locking and clearing caches have been added.
  • The clean web.config now contains a description of the following attributes, which can be used for <site> definitions:
    • loginPage
    • defaultDevice
    • enableAnalytics
  • An enableAnalytics="false" attribute have been added to the following site definitions:
    • "shell", "login", "testing", "admin", "modules_shell", "scheduler", "system", "publisher"
  • A new "Authentication.ClientPersistentLoginDuration" setting has been added ("Remember me" feature).
  • A new "Caching.IsUserInRoleCacheSize" setting has been added (security caching).
  • A new "Caching.UserProfileCacheSize" setting has been added (security caching).
  • A new "WebEdit.DefaultButtonPath" setting has been added (Edit Frame feature).
  • A new "Preview.DefaultSite" setting has been added (used by the Preview  application).
  • The default value for the "MailServer" web.config setting is now an empty string.  

May 22, 2009

Released Sitecore CMS 6.0.2 rev.090507 (also known as 6.0.2 Update-1).

This release is no longer recommended. Please upgrade to the recommended one.

Please visit the appropriate Sitecore CMS 6 Updates section for instructions describing how to download and install this release.

Change log.

Issues resolved:

• In some circumstances, site visitors who were not members of the "sitecore\Sitecore Client Users" role were able to view unpublished content.
• In some circumstances, security would be ignored for the first request after an ASP.NET restart, meaning that a site visitor without appropriate access rights could be able to view secured pages.

IE8 Cosmetic Issues:

• The username and password fields were not properly positioned on the Sitecore Login page.
• The Desktop, Workbox and Preview options on the Advanced Login page were not properly aligned with the other User Interface buttons.
• Unnecessary scrollbars were present in Rich Text Editor fields when IE8’s Compatibility Mode was enabled.

April 28, 2009

Released Sitecore CMS 6.0.2 rev.090416.

This release is no longer recommended. Please upgrade to the recommended release.

Please visit the appropriate Sitecore CMS 6 Updates section for instructions describing how to download and install this release.

Change log.

New features:

• Support for Oracle Databases added. To install Sitecore with Oracle, follow instructions in the Sitecore CMS Installation Guide, Chapter 5: Oracle Database Storage Setup.

Improvements:

• The clean installation now comes with a number of sample "include files". The examples are located in the /App_Config/Include folder.

Issues resolved:

• The profile provider would sometimes return null instead of string.Empty for empty profile properties. This could lead to a error in various applications, for example when opening the "Regional and Language Options" in the Control Panel or when creating or opening renderings in the Developer Center.

March 24, 2009

Released Sitecore CMS 6.0.1 rev.090317 (also known as "6.0.1 Update-1").

This release is no longer recommended. Please upgrade to the recommended release.

Please visit the appropriate Sitecore CMS 6 Updates section for instructions describing how to download and install this release.

Change log.

New features:

1. A new 'defaultProfileItemId' attribute has been added for <domain> definitions in the domains.config.xml. DefaultProfileItemId is typically used when using external security providers where the users in the domain do not automatically have a Profile associated with them.
2. A new MaxItemNameLength web.config setting was introduced, making it possible to change the maximum length of item names. The default value is 100 characters.

Issues resolved:

1. Fixed: When using dynamic image scaling, the right and bottom edge of the image would sometimes appear cropped.
2. Fixed: Improved performance in the User Manager when switching between pages.
3. Fixed: Links created by using the DropTree fields type were not added to the link database. As a result, such links were not shown in the "Links" pane on the "Navigate" tab in the Content Editor.
4. Fixed: Virtual items from external databases could not be opened in the Content Editor if the template they were based on did not exist in target database. An unhandled exception would appear.
5. Fixed: When setting publishVirtualItems to 'true', the virtual items would be published without any versions.
6. Fixed: When setting publishVirtualItems to 'true', the virtual media items would be published with an empty value in the Media (Blob) field.
7. Fixed: An exception might appear in the Sitecore log files when the Web client disconnected in process of streaming the media data (e.g. the client was disconnected by closing the browser window).
   Notice: This issue was not completely resolved, and is still reproduced under certain circumstances. See the known issue for more information. [Added March 12, 2010]
8. Fixed: When the IIS application pool was configured to run using a non-standard user account Identity, a System.Security.Cryptography.CryptographicException might occur, preventing Sitecore from working.
9. Fixed: Creating items with Danish symbols "æøå" or other unicode characters in the item name was not possible, even if the unicode characters had been added to the ItemNameValidation setting.
10. Fixed: Publish worked incorrectly when proxiesEnabled = false, publishVirtualItems = false for master database and proxiesEnabled = true for web database. The virtual items would be removed from the web database during publishing, thereby deleting them from the source database.
11. Fixed: The SwitchingProfileProvider no longer throws an error when editing users where different user profile properties are stored by several different profile providers.
12. Fixed: Profile properties from custom profile provider could end up being saved as core profile provider properties, not as custom profile provider properties.
13. Fixed: Sitecore Packager could silently fail when experiencing an error during installation, only reporting the error in the log file, not in the Installation Wizard.

February 13, 2009

Released Sitecore CMS 6.0.1 rev.090212 (also known as "Service Release-1").

This release is no longer recommended. Please upgrade to the recommended release.

Please visit the appropriate Sitecore CMS 6 Updates section for instructions describing how to download and install this release.

Change log.

New features:

1. It is now possible to organize layouts, sublayouts and renderings into folders, using the new Layout Folder, Rendering Folder and Sublayout Folder branches.
2. Danish translations are added into Sitecore 6.0.0.

Improvements:

1. Packager performance is improved when installing packages.
2. Increased performance when executing Assert statements in the core DLLs.
3. New XSLT renderings no longer define a $home variable which can result in a slight performance increase. Instead, comments are included in the file with examples of different syntax for defining a $home variable.
4. SQL Server databases: An index has been added to the Blobs table for the 'master' database to increase performance of retrieving media.

Issues resolved:

1. Page Editor
   • Lock/Unlock functionality in the Page Editor: The Page Editor now takes the AutomaticLockOnSave setting from the web.config file into account when saving. Automatic unlocking in the Page Editor is controlled by setting security on the /sitecore/system/Settings/Security/Policies/Page Editor/Keep Lock After Save item in the core database.
   • By default, the Page Editor will no longer keep items locked when an Administrator user saves an item. To keep items locked after saving for Admin users, set the KeepLockAfterSaveForAdminUsers setting in the web.config to "true".
   • Switching from Preview to the Page Editor could result in various problems, including inline editing not being available, green content dots disappearing and the Design pane throwing an exception. The problems were related to the user context being reset to extranet\Anonymous.
   • If the user navigated away from a page where he did some changes in an image field in inline editing mode, he would not be asked to save the changes and the changes would be discarded.
   • When starting the Page Editor from the login page, it would be opened for the default site even when the host name of another site was specified in URL.
   • The Page Editor and Preview client would start on the Home item from the current site definition instead of the StartItem. This could in some cases lead to a "document not found" page when a user tried to start the Page Editor or Preview from the login page.
   • The treecrumb in the Page Editor showed hidden items.
   • The Page Editor did not work correctly with extensionless URLs when a 404 error handler such as "/sitecore/404.aspx" was configured in the IIS Manager.
   • Changes to renderings in the Design pane would not always be saved if a layout only had renderings assigned to a single device.
2. Security API and related applications
   • Editing users in the User Manager no longer remove roles from the user and assign them again.
   • Nobody could login to Sitecore after user with ^ or | in his password tried to login. Application restart was necessary.
   • Calling sc:UserInfo(string) in an XSLT rendering would return no information or throw an exception for certain user property fields.
   • The password could not be changed for users converted from Sitecore CMS V5.3.
   • An "intranet\Anonymous" user was present even though there was no "intranet" domain defined.
   • The "Full name" column in the User Manager did not show the full name when using the Active Directory security provider.
   • The legend in the Access Viewer has been changed to say "Not specified" instead "Inherited".
   • In the clean installation, the Client Language and Regional ISO Code is now set to "Default" for the "sitecore\Admin" user.
3. SQLite
   • The SQLite security provider did not allow users from other security providers to be added as members of the default roles.
   • Nested roles were not shown on the "Member Of" tab in the User Manager.
   • Archive and Recycle Bin application would fail.
   • Uploading media items did not work correctly if the ASP.NET account did not have access to the c:\temp folder.
4. Developer Center
   • When closing a layout with unsaved changes in the Developer Center, an exception could occur if answering "Yes" in the confirmation window about saving changes.
   • The Grid Designer would not always save changes when used from the Content Editor.
   • The Grid Designer now shows a warning if the Path field of the layout is empty instead of throwing an exception.
   • An error could occur when in the Grid Designer when splitting a table vertically.
   • An error could occur when saving a layout after switching between Design and Grid view.
   • When starting the Page Editor inside the Developer Center, the window tab no longer says "WebEdit".
5. Item Serialization
   • After template with __Standard Values filled with some field values was serialized and removed the Update tree command in the Content Editor might throw an exception.
   • The Serialize Item command in the Content Editor did not work for Media (Blob) field of media items. As a result of this, this field could not be deserialized.
   • Serializing a tree with many levels or very long item names might throw an exception.
6. Cosmetic Issues
   • The validator bars in the Content Editor were not visible if "Prefetch collapsed sections" was disabled in Application Options and "Standard Fields" was turned off. Also, borders would be missing around fields in with this configuration.
   • Minor UI fixes for the Package Designer. The "New" menu was not closed after creating a new package and some of the date pickers displayed two combobox arrows.
   • Minor UI fixes for Firefox.
   • Various minor UI fixes, such as missing or unnecessary scrollbars.
7. Changes to the web.config file
   • The default value for the MemoryMonitorHook Threshold setting in the web.config file has been increased to 800MB.
   • The default settings for the MemoryMonitorHook in the web.config file has been changed to avoid decreasing performance on servers where Sitecore reaches the MemoryMonitor.Threshold limit.
   • The LayoutNotFoundUrl setting in the web.config file had an incorrect value.
   • The DictionaryFolder key in the web.config file had an incorrect value.
   • An obsolete fastCache section has been removed from the web.config file.
8. XSLT Renderings and Sublayouts
   • sc:image control sometimes threw an error if the image field was empty.
   • asp:login control did not work when placed on a sublayout.
   • Controls which do post back would not work correctly when placed on a sublayout with cache settings applied.
   • Paths starting with "~" in ASCX were output literally instead of being transformed relative to the webroot.
   • Using XSLT variables as parameters for Sitecore's XSL Controls did not work.
   • XSL Rendering Caching section was available only when Standard Fields was enabled.
9. Link Database
   • TreelistEx fields were not included into link database.
   • The "Sample Item" template could not be deleted due to dead links in the link database.
   • Dead links are now removed when running the "Clean up databases" application.
10. Publishing
    • Publishing items with empty fields would incorrectly use the standard value for the published item if the "Reset blank" checkbox was checked for the field definition.
    • For items containing multiple versions, changes to unversioned and shared fields would not always be published.
    • If an item contained any broken links it could not be published.
11. Miscellaneous
    • The Database.GetItem() and ItemManager.GetItem() functions may occasionally return null when the site is under heavy load. This can cause problems when searching for existing Sitecore items. [Added July 21, 2009]
    • Using query in field sources did not work.
    • The item cache could return wrong results for sites where filterItems="true".
    • Item count in the Media Library included hidden items.
    • Hidden items were displayed in the right-hand pane of the Media Browser.
    • Setting a background color for the Sitecore Desktop did not work.
    • Changes to the current user's icon in the control panel would not be reflected in User Manager.
    • Decimal values entered into number fields were reported as being invalid when using a culture that does not use "." as decimal symbol.
    • When copying an item without any English versions to another location, an English version would be added.
    • The login page would sometimes show a misleading message on failed logins.
    • The wrong folder would be opened in the File Explorer after clicking the Up button and then double clicking any folder to open it.
    • The Installation Wizard would sometimes skip items when the items to install already existed in the solution.
    • Right clicking the ribbon in the Content Editor no longer show tabs that are restricted using security.
    • The Device Editor did not show folders created from the Node template.
    • An obsolete "Image has validation path" validation rule has been removed from the 'master' database.
    • The Media.StreamPartiallyCachedFiles setting in the web.config file did not work.
    • Specifying an invalid type for "Subitem sorting" would not always log an error in the log file.
    • The log file contained warnings about the 'Logging.AuditsLogged' performance counter not existing on the server.
    • The log file would sometimes contain unnecessary BrokenLinkValidator errors related to TemplateSection.GetField().
    • SqlException "transaction was deadlocked" would sometimes occur when copying or changing a large amount of items.

 

January 30, 2009

Released Sitecore CMS 6.0.0 Update rev.090120 (also known as “Update-9”).

This release is no longer recommended. Please upgrade to the recommended release.

Please visit the appropriate Sitecore CMS 6 Updates section for instructions describing how to download and install this update.

Change log.

Issues resolved: 

1. Fixed: Web sites which leverage AJAX features could receive JavaScript errors.

December 29, 2008

Released Sitecore CMS 6.0.0 Update rev.081222 (also known as “Update-8”).

This release is no longer recommended. Please upgrade to the recommended release.

This version is no longer available.

Change log.

Issues resolved: 

1. Fixed: XSL renderings occasionally failed under high load with many concurrent users and reported “A rendering error occurred: Xsl file could not be processed” in the Sitecore log file.

2. Fixed: Media items could not be stored in a content infrastructure that was more than three folders deep, because item IDs were used as folder names for media storage on disk, which resulted in file paths that exceeded the maximum allowed by Windows.

3. Fixed: When switching from Preview to Page Editor, inline editing would no longer be available (and Green Dots would disappear if showing content dots). This is still an issue if Sitecore is running on Vista and the editors use IE7 & IE8.

December 09, 2008

Released Sitecore CMS 6.0.0 Update rev.081203 (also known as “Update-7”).   

This release is no longer recommended. Please upgrade to the recommended release.

This version is no longer available.

Change log.

Issues resolved: 

1. Fixed: Installation wizard didn’t install files marked to skip if exists.

2. Fixed: XSL renderings might fail occasionally under high server load.

3. Fixed: Creator-Owner role might be ignored when resolving access rights.

October 29, 2008

Released Sitecore CMS 6.0.0 Update rev.081022 (also known as “Update-6”).   

This release is no longer recommended. Please upgrade to the recommended release.

This version is no longer available.

Change log.

Issues resolved: 

1. Fixed: Uploading files did not work if the Flash 10 player was installed.

October 17, 2008

Released Sitecore CMS 6.0.0 Update rev.081009 (also known as “Update-5”).   

This release is no longer recommended. Please upgrade to the recommended release.

This version is no longer available.

Change log.

Issues resolved: 

1. Fixed: Cross site links were not working as expected. Such links now include the hostname of the target site and are generated relative to the start item of the target site. This functionality can be disabled by setting Rendering.SiteResolving to “false” in the web.config file.

2. Fixed: a selected Publishing Target of an item was not taken into account when performing Publish operations.

3. Fixed: The performance of item creation has been significantly improved.

New features:

1. The FastQueryDescendantsDisabled setting has been added to the web.config file. It may be set to true to disable the ability to use fast query to select items through Ancestors/Descendants axes. This will give a small performance increase of item creation/moving/deletion.

October 9, 2008

Released Sitecore CMS 6.0.0 Update rev.081002 (also known as “Update-4”).

This release is no longer recommended. Please upgrade to the recommended release. 

This version is no longer available.

Change log.

Issues resolved: 

1. Fixed: When running Sitecore in virtual environment, the .NET worker process might stop working due to a problem in Microsoft’s .NET implementation.

2. Fixed: Sitecore required Flash for upload to work. The old upload dialog box will be used if Flash is not installed.

3. Fixed: Sitecore would display an error message when an Administrator tried to save changes to an item that was locked by another user.

4. Fixed: Despite setting <setting name="AutomaticLockOnSave" value="true" /> in web.config, items were not locked on edit if Standard Fields were displayed.

5. Fixed: Despite setting <setting name="AutomaticLockOnSave" value="false" /> in web.config, items were locked after editing if Standard Fields were not displayed.

September 18, 2008

Released Sitecore CMS 6.0.0 Update rev.080912 (also known as “Update-3”).

This release is no longer recommended. Please upgrade to the recommended release.

This version is no longer available.

Change log.

Issues resolved: 

1. Fixed: The Sitecore Client Authoring role had been assigned all access rights for the /sitecore/content item, which gave all content authors more access rights than intended.

2. Fixed: A runtime error could occur when a user attempted to select a workflow command to move an item from one state to another.

3. Fixed: Despite restricting access to an item in a specific workflow state, the “Edit” button was still enabled and allowed users to edit the item.

4. Fixed: The AccessResultCache was not always cleared after an item was moved to another workflow state, which could result in inappropriate access rights assigned to the item.

5. Fixed: The Page Editor Edit mode attempted to open the contentStartItem of the Shell Web site, rather than the startItem of associated Web site, which caused editing issues in multi-site installations.

6. Fixed: The ComponentArt grid control used in the User Manager initialized itself multiple times, causing slower than necessary startup performance in sites with many thousands of users.

August 29, 2008

Released Sitecore CMS 6.0.0 Update rev. 080820 (also known as “Update-2”).

This release is no longer recommended. Please upgrade to the recommended release. 

This version is no longer available.

Change log.

Issues resolved: 

1. Fixed: stability issues occurred with .NET 3.5 SP1 installed.

2. Fixed: items in a workflow were not automatically versioned when users edited them in the Page Editor mode.

3. Fixed: the media cache grew even when the link to a media library entry had the same query string parameters as the previous one.

4. Fixed: in some cases, deadlocks could occur during the recycling/restoring of items.

5. Fixed: Sitecore CMS could hang if the ‘Subitems Sorting’ definition in the Type field referred to a non-existent class or .dll file.

6. The performance of the ItemSerializer was increased.

7. Fixed: The SQL generated for fast query could not be customized when implementing new data providers.

July 14, 2008

Released Sitecore CMS 6.0.0 Update rev. 080701 (also known as “Update-1”). 

This release is no longer recommended. Please upgrade to the recommended release.

This version is no longer available.

Change log.

Issues resolved:

• Fixed: if the back-end was accessed using the http://[hostname]/sitecore/shell URL, running the Sitecore desktop applications could result in errors. 

June 30, 2008

Sitecore CMS 6.0.0 rev.080627 is released.

This release is no longer recommended. Please upgrade to the recommended release.

This version is no longer available.