July 21, 2014
SITEFINITY 7.1. RELEASE NOTES
This release addresses 24 issues from the Feedback Portal (FP), with a total of 330 votes. Included are some of the most popular requests for Recycle Bin, Content Items Duplication, Custom Page Templates, etc.
Enterprise license only
(Documentation), (FP, FP, FP)
Audit log creates a record for actions performed in Sitefinity backend such as log in, log out, content and pages creation, modification, deletion, etc. The collected data allows administrators to investigate content incidents promptly, and to take notice in cases of unauthorized access.
Users creating content can easily duplicate existing items thus reusing content which is already in place.
Duplicate option under the Actions menu of content item is available for: Events, News Items, List items, Blog posts, Dynamic Content Items, and Shared Content Blocks.
(Documentation, how to include content and pages in sitemap), (FP)
Sitemap generator creates an XML file containing the URLs for a Sitefinity site along with info on when they were last updated, how often they change, and how important they are, relative to other URLs. The sitemap is used by search engines crawling the site.
Content) are kept fully in the index (not truncated in any way).
Sitefinity Skin for ASP.NET AJAX Controls Depreciated
Sitefinity skin will be deprecated in Siteifnity 7.2 and onwards. All Telerik UI controls for ASP.NET AJAX that are part of Sitefinity will render with their default theme instead of the Sitefinity skin.
This means that if you use Sitefinity-skinned ASP.NET AJAX controls in Sitefinity v7.1 they will still work. However, newer Sitefinity versions (7.2 or later) will not support the Sitefinity skin. We recommend that you check any custom front- and/or back-end widgets that might use the Sitefinity skin and switch their skin to the default or another supported theme.This also applies to any custom modules (e.g. custom content modules, custom intra-site modules etc).
IFormEntryEventControlproperties are moved up the hierarchy into the newly introduced
IFormEntryEventControlBasebase interface, which is shared with the new
IFormEntryValidationEventControlinterfaces. This changes are source compatible, but as they are binary incompatible, a rebuild is required.
ILoginCompletedEventproperties are moved up the hierarchy into the newly introduced
ILoginEventBasebase interface, which is shared with the new
ILogoutCompletedEventinterfaces. This changes are source compatible, but as they are binary incompatible, a rebuild is required.
Telerik.Sitefinity.Localization.Data.RequiredLocalizablePropertyAttributeclass is removed. It was duplicated and the deleted one was not used anywhere.
With the current release the actual type of the properties of a Controller is retained during serialization. Prior to this change, the properties of a controller were always serialized as a string. This change is part of the effort for the alignment of the functionality available for WebForms and MVC since the data is serialized with keeping the actual type of a property for web forms widgets and we wanted to keep the same notation for MVC widgets. This way it is easier to port designers from one widget to another or reuse code with both approaches.
New overloads of the Html.BeginFormSitefinity helper method introduce the ability to specify whether the controller should be associated with the generated form tag. The controller is associated with a <form> tag by appending the controller Id to the query string of the form action url. This functionality is useful in case there exist two different MVC widgets that have action methods with the same signature, the two MVC widgets are placed on the same page and one would like to invoke only the action of one of the widgets. Prior to the current change, the Html.BeginFormSitefinity helper method had always associated the controller with the generated <form> tag (this was introduced in the 7.0 release), but as clients reported this is not optimal. With the current release of Sitefinity, the Html.BeginFormSitefinity helper method does not associate the controller with the <form> tag by default anymore and instead, one should use the newly introduced overloads of the helper method.