Sitefinity 7.1 Beta CancelThe title field is required!

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.

SITEFINITY 7.1. BETA RELEASE NOTES

What’s New

Audit Trail

Enterprise license only
(Documentation)
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. Notes: The recommended setup requires that Kibana and Elastic search are installed (instructions).

XML Sitemap generator

(Documentation, how to include content and pages in sitemap)
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.

XML Sitemap settings and generation can be done in section Settings> Sitemap.

Known Issues

XML Sitemap cannot be generated on projects created with Sitefinity Project Manager (Cassini)

Multiple Child Types per Level in Module Builder

(Documentation)
This implementation removes the current restriction where users can have only one child content type on a given level in Module Builder.

In Module builder, users can add more than one child content type under a parent content type

In Page Toolbox, a new section is added for each module, and a new widget is added for each content type

In pending items dialog only items from the default provider are filtered by taxonomy

Fixed creating two Default Calendars after migration

Pending Items Dialog Selective sync throws an exception randomly

Connectors

Marketo: Calls for jQuery and JSON2 are no longer made in the front-end pages if they are already loaded.
Note: This change might cause a JavaScript error if the used munchkin relies on jQuery. This can be avoided by switching to a different munchkin or loading jQuery in the front-end pages' head tag.

Sharepoint: Cannot create mapping for SharePoint list, which name contain only cyrillic letters

Sharepoint: SharePoint Error messages for duplicate items for documents is not shown

Sharepoint: Added validation to Connector for SharePoint when synchronizing dynamic module types. You can no longer select or synchronize a non-root level type

Address Field: Values are not persisted when you create dynamic item with address field

Forms: Issue preventing the user from editing the root level permissions for Forms

Choice field: Creating a choice field throws error when a choice value has "<" symbol in it

Dynamic Module: Old media field cannot be deleted

Search: Changing the identifier to a another field of a custom module, results in empty results when searching for the old field

Search: Documents appear in all site search indexes when working in Multisite mode

Ecommerce: Purchased downloads cannot be downloaded when file is replaced

Backward Compatibility

Note: 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 is the last release, in which the Sitefinity skin is available in the Telerik.Web.UI.Skins assembly.

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.

I've just taken a quick look at 7.1 to see how parent/child relationships will be handled and it doesn't look like they've been implemented at all. I see that you can now add the same content item to itself which is a step in the right direction but there's no way of enforcing parent child (so I can easily add a child to a parent and then the parent to the child). Also, there's no easy way of seeing what "children" you've added to the "parent" in the current implementation. Is this all stuff that might still make it into 7.1 or is there another ETA. I really think this is the biggest limitation to the module builder right now since most of the modules we build require some sort of hierarchical relationship. Please let me know.

Hi KMac,
Sitefinity 7.1 gives you option to have more than one child types as children of another content type. This can be achieved in Module Builder. In the Backend screen of the parent items, you see the child items as links under each parent item, like this: http://1bg32c.axshare.com/#p=parent_type_grid
What we are planning in some of the next releases is to add option to allow a content type to be in hierarchical relationship with it self (the so called "self referencing hierarchy"). In this case, the backend grid of the content type will look something like a tree view (very similar to the Backend of Pages). Let me know if this can work for you, or should you have more questions.

Tools

Sitefinity Professional Services

Progress, Telerik, Sitefinity and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries.