Sitefinity 7.3 Beta is available for download on this link
We have also beta NuGet packages available on http://nuget.sitefinity.com
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.
Search in the Cloud and other improvements
Granular permissions in dynamic content
Connector for SharePoint Online
(github link, project page)
Allows developers to build mobile-ready sites using their favorite frameworks and includes MVC stock widgets, an AngularJS widget designer framework, Boostrap and Gumby support, and more.
As of Sitefinity 7.3, we have introduced the following:
Automatically generated MVC widgets for dynamic content types
Reusable Content Selectors based on AngularJS
As of Sitefinity 7.3, Feather will be shipped as standalone module, which needs to be installed from Modules and Services backend section. For more details, please visit the Feather Wiki on Github.
Sitefinity Digital Experience Cloud
External blob storage provider for media (images, videos, documents)
Network Load Balancing
Permissions don't seem to work...
I would expect as an anon user to not see Folder 2 in the list let alone be able to open and comment on it.
Am I missing something?
Don't suppose the permissions menu item could be hidden then if thats not enabled, because it's gonna cause confusion.
How much of a perf hit is it...noticable? Should be be concerned?
Thank you for your feedback!
About the overhead - it is equal to the additional calculations that have to be made when joining two permissions related tables to the result set when querying multiple items. The performance impact is limited by the fact that the columns used for those joins are indexed. So there is a linear dependency between the number of existing rows and the total calculation time needed to perform a specific fetch operation.
In other words this functionality is optimized as much as possible but is disabled by default since view permissions are allowed for everyone by default. We are working on UI improvements to better communicate this dependency.
I noticed a small problem with the RadEditor when creating a blog post with the Sitefinity 7.3 Beta. Below are the steps to repeat the issue. Also, I did this on Google Chrome 39.0.2171.71.
Please verify if you are also seeing this same issue. Thanks.
I created a new module, using Module Builder, and set an item to be view-able by administrators only. Added the widget to a page and logged out. Even with your additional setting turned on I still see this item.
@Steve Were you able to get your solution to work after enabling this setting?
on the problem with RadEditor - we were able to reproduce it, and it is logged for fixing.
Thanks a lot for taking the time to test and to provide such detailed explanation!
Let us know if you have more feedback,
Thank you for your feedback.
Regarding the issue with dynamic content items being visible on the frontend, we already have this fixed. It will be included in the official release of Sitefinity 7.3.
Kali and Ivan, thanks for getting this fixed!
I'm attempting to test this via the NuGet repository and I'm getting the following error:
Unable to resolve dependency 'Telerik.DataAccess.Core (= 2014.3.1128.1)'.
Should this be working with NuGet?
It got a little further but still failed with the following:
Updating 'Telerik.Sitefinity.Core 7.2.5300.0' to 'Telerik.Sitefinity.Core 7.3.5350.0-beta' failed. Unable to find a version of 'Telerik.Sitefinity.Feather' that is compatible with 'Telerik.Sitefinity.Core 7.3.5350.0-beta'.
We updated the beta with a new build that you can download from the original link or here. The build includes fixes and improvements and latest versions of dev tools - RadControls for ASP.NET AJAX, Kendo UI, Data Access and other. Feather is included in Sitefinity project manager installation as a Module. NuGet packages are available on http://nuget.sitefinity.com
Please share your feedback and questions on the coming 7.3 release!
It looks like removing the original Telerik.Sitefinity.Feather NuGet package and then re-adding it fixed the NuGet update issue. I was able to fully update all NuGet packages now.
Although, now that Feather is an integrated Module, I have some questions about the upgrade with with 7.3 and Feather. Not sure if I should I ask those here, or on the GitHub project site? I'll start here, but I can move it to a GitHub issue if you'd prefer...
After doing the NuGet update, I compared how it upgraded an existing project to a new project created with the Project Manager. It looks like a new project doesn't include any of the files in the ResourcePackages directory (since it doesn't use the Telerik.Sitefinity.Feather NuGet package), but a project using NuGet includes all the content in the ResourcePackages directory (Bootstrap/Foundation/SemanticUI).
Does this mean that if I'm upgrading an existing project using Feather from NuGet, that I could delete all of the non-custom content in the folder structure? Is the Telerik.Sitefinity.Feather NuGet package even needed anymore since it's a built in module?
And a general Feather upgrade question: What will be the recommended method upgrading an existing project using Feather NuGet packages?
When you make an upgrade or new installation:
- Telerik.Sitefinity.Feather.7.3.5351.0-beta.nupkg extracts all files from the package's content folder to ResourcePackages folder including Bootstrap, Foundation, SemanticUI etc.
- The Project Manager will do the same - add ResourcePackages folder including Bootstrap, Foundation, SemanticUI and all content inside them. The project manager uses System.IO instance methods for creating, moving, and enumerating through directories, so I suppose if something is not added there might be an read/write issue although I think that there is error handling.
But, if you have customized a file, say 'ResourcePackages\Bootstrap\csslint.json' it will be overridden from what we have in the ProjectManager as ResourcePackages .
I performed a simple test and didn't noticed missing files or folders when using the NuGet package or the PM for creating a new project or upgrading an existing project. Let me know if I'm missing something, so we can do further testing and see if we are able to replicate the issue with your help and apply a fix.
As for the usage of the NuGet package and PM - these are just different ways to keep your solution with specific versions. The project manager is our implementation for upgrades and managing Sitefinity projects easily. NuGet is wide popular web based gallery platform and has various integrations with other tools provided by different contributors / consumers.
The current plans are not to coupe Feather with the specific version of Sitefinity and allow users to use packages to get updates from the Feather repository on Git without changing their Sitefinity version or releasing a new version of Sitefinity when possible, so Telerik.Sitefinity.Feather NuGet will be needed for such cases.
Have to say, actually really impressed with this beta. Performance seems much better than the current release.
Is the Azure storage dlls (1.7) supported after Azure announced the retirement of the older dlls?
I see the beta is still using 1.7
Will this release upgrade to the current 2 version of the Azure storage client?
(I am asking after reading a post on the forums.
Using Just Decompile I can see that the references for WindowsAzure.Diagnostics and Service Runtime are 2.2 but StorageClient is 1.7
I have attached an screen shot
The Microsoft.WindowsAzure.StorageClient will remain 1.7 version in Sitefinity 7.3.
The other Azure assemblies use 2.2 version
Microsoft.WindowsAzure.ServiceRuntime, Version 18.104.22.168
Microsoft.WindowsAzure.Diagnostics, Version 22.214.171.124
Microsoft.WindowsAzure.Diagnostics.StorageUtility, Version 126.96.36.199
The planned removal of earlier versions of the Azure Storage Service APIs will happen in December 2015, so we will have a compatible version prior that. I cannot tell you the exact Sitefinity version right now. Once we started working on this we will make an announcement in the forum.