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.
Audit Trail = Enterprise license only.
That is not so fun. Please, if you talk new features, let us know before if it is limited to a particular license.
Another useful feature that is only for enterprise...
It's been no secret that Audit is enterprise only... www.sitefinity.com/timeline . It is a bummer, but would a std or sbe really have an elasticsearch instance anyway?
Notes on the beta: https://docs.google.com/spreadsheets/d/13DbV_9fmuu631Ef4dBjNgzSuFyBep7kRAlP7SVZFEOM/edit?usp=sharing
Sitefinity 7.1 Beta is available for download on this link
(Download link updated on 1July, include fixes in Sitemap, upgrade in Service Stack).
We have also NuGet packages available on http://nuget.sitefinity.com
This version contains: Audit Trail, Recycle Bin, XML Sitemap generator, and more.
We’d be happy to hear your feedback and questions on the coming release!
Please, upgrade your projects and let us know if you encounter any issues.
Notes: This release is for testing and evaluation purposes. Upgrades from it will not be supported.
Enterprise license only
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).
Recycle Bin stores deleted items for a period of time, thus allowing for the easy recovery in case of incidental deletion.
Users creating content can easily duplicate existing items thus reusing content which is already in place.
Duplicate option on 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)
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.
This implementation removes the current restriction where users can have only one child content type on a given level in Module Builder.
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.
This also applies to any custom modules (e.g. custom content modules, custom intra-site modules etc).
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: 1bg32c.axshare.com/
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.
I understand your frustration. We'll try to announce such limitations sooner.
Thanks for the list, we are working on it, and will let you know when we have something to report.
Just to let you know that we updated the Beta download link - please refer to the original announcement.
This build contains: Fixes in Sitemap not able to start, and upgraded Service Stack to 4.0.22.
We look forward to receiving your feedback!
Thank you for feedback and notes.
We have logged couple of bugs, related to the typo on the login message and the blank delete message, when removing pages.
We appreciate your feedback! Let us know of your latest findings about the beta!
Has this bug be fixed in 7.1? At the moment Related Data fields do not work in a multi-site environment except for the primary site
We updated the beta build with a new one - 7.1.5143. The build includes
I've already found an issue.
If you delete all pages you can't open the recycle bin.
Hi, thank you