Releases: SenseNet/sensenet
sensenet Services 7.1.3
New features
- New actions
- To let client-side devs build dynamic forms, we added the GetSchema custom action that will serve the available content types (including field metadata) to the client.
- New SnAdmin steps
- To aid the migration process from sensenet 6 to sensenet 7, we created a Move config SnAdmin step that will be able to update configuration files. This is a generic step so you'll be able to use it in similar scenarios.
- We extended the ForEach SnAdmin step to work with an explicit file list (e.g. well-known config files) in a loop.
Installation
To get started please follow the instructions in the Install sensenet from NuGet article.
Upgrade from previous version
If you already have sensenet installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.
The patch above is a cumulative package that you may execute on any previous version. This means you do not have to upgrade to previous interim versions before executing this one.
Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version. Please check your connection strings (web.config and Tools\SnAdminRuntime.exe.config) after updating the packages, because NuGet may change those values based on the package contents.
sensenet Services 7.1.2
New features
- Component version compatibility is not checked when using debug dlls to speed up the development process.
- Delete content type step is added to serve cleanup scenarios in the future.
- Improved in-memory db installation in tests.
- We opened a virtual method in the ClusterChannel base class so that 3rd party developers can create their own messaging providers. We use this API to create the initial implementation of the RabbitMQ messaging provider.
Bug fixes
- An unknown field in a query caused a null reference exception.
- LINQ to SN First, FirstOrDefault and a couple of similar methods work correctly. If a LINQ method is not supported, we throw a meaningful exception to inform the developer what to do.
- Fixed a wildcard query bug in LINQ to SN that broke StartsWith expressions.
- When the user Profiles container is created, we set container permissions correctly so that new users can access their profiles.
Installation
To get started please follow the instructions in the Install sensenet from NuGet article.
Upgrade from previous version
If you already have sensenet installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.
The patch above is a cumulative package that you may execute on any previous version. This means you do not have to upgrade to previous interim versions before executing this one.
Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version. Please check your connection strings (web.config and Tools\SnAdminRuntime.exe.config) after updating the packages, because NuGet may change those values based on the package contents.
sensenet Services 7.1.1
New features
- Some classes in the Search component became serializable to aid the upcoming Search Service feature.
- Open the PermissionFilter API to let other apis call its methods.
- Test projects were updated to the latest test project type.
Bug fixes
- Query count fix: in some cases the count of a query result was 0 even if the query returned the actual content items. This bug broke the Windows authentication feature.
- Duplicated documents
- Webdav fix for paths starting with /Root and for Versioning GUI in Word.
- Open permission added for logged in user on the DWS (Edit in Office) web root folder to let them edit Office files.
- The central activity queue became more robust and thread safe.
Installation
To get started please follow the instructions in the Install sensenet from NuGet article.
Upgrade from previous version
If you already have sensenet installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.
The patch above is a cumulative package that you may execute on versions from 7.0.0 to 7.1. This means you do not have to upgrade to previous interim versions before executing this one.
Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version. Please check your connection strings (web.config and Tools\SnAdminRuntime.exe.config) after updating the packages, because NuGet may change those values based on the package contents.
sensenet ECM Services 7.1
New features
Search module
This is a major update of the platform: we generalized indexing and querying so that the Lucene search engine can be refactored later to work as a service instead of as a local index. In this first phase nothing will actually change architecturally: the index folders will remain in the local web directory as before. But under the hood we decoupled the search module from the repository, which means we will be able to create and deploy a separate search service in the future, without changing the code in the main application.
Breaking changes
This version contains API changes that may break low-level search-related calls. We had to move a few classes to a different namespace (e.g. the base TextExecutor class) and a few enumerations too. If you encounter build or type load errors during or after the upgrade, please follow the suggestions in Visual Studio to update those calls or base classes. We do not expect to have many of these, but if you stuck with the upgrade please contact us for help.
Bug fixes
- SmtpClient instances are created in a using block so that they got desposed properly to prevent connection leak.
- Logout action can be called without providing the ultimateLogout optional parameter.
- Add initial See permission for the Identified Users group to the Folder content type so that users see the folder creator action on the UI.
Installation
To get started please follow the instructions in the Install sensenet ECM from NuGet article.
Upgrade from previous version
If you already have sensenet ECM installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.
This is a major upgrade, please check out this article for details about performing a complex upgrade.
The patch above is a cumulative package that you may execute on versions from 7.0.0 to 7.0.2. This means you do not have to upgrade to 7.0.1 or 7.0.2 before executing this one.
Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version. Please check your connection strings (web.config and Tools\SnAdminRuntime.exe.config) after updating the packages, because NuGet may change those values based on the package contents.
sensenet ECM Services 7.0.2
New features
- Ultimate logout: we improved the logout feature by letting operators and client developers decide what should happen when the user logs out of the system: from now on it is possible to log out from all clients (meaning all devices and browsers). This will make the system even more secure as it will invalidate security tokens on all clients. This is related only to the JWT authentication mechanism, it does not affect the old webforms authentication chain.
Installation
To get started please follow the instructions in the Install sensenet ECM from NuGet article.
Upgrade from previous version
If you already have sensenet ECM installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.
The patch above is a cumulative package that you may execute either on version 7.0.0 or 7.0.1. This means you do not have to upgrade to 7.0.1 before executing this one.
Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version. Please check your connection strings (web.config and Tools\SnAdminRuntime.exe.config) after updating the packages, because nuget may change those values based on the package contents.
sensenet ECM Services 7.0.1
The new version of sensenet ECM Services' main component has arrived!
New features
- ISnComponent interface for defining components. Currently this contains an API for checking component versions to make sure that the dlls and the database remain consistent across NuGet packages (see previous link).
Bug fixes
- fix WebDAV issues:
- Skip preflight response in case of webdav and office protocol.
- Take into account the explicit port in the url.
- "Open in Office" works even if the workspace name contains a
spacecharacter.
- fix for the add action and others to make the correct backurl response
- fix for Windows authentication
- fix for case sensitive database collations (Changed stored procedures: proc_LogWrite, proc_LogAddCategory)
- fix for JWT session identifier randomness issue
Installation
To get started please follow the instructions in the Install sensenet ECM from NuGet article.
Upgrade from previous versions
If you already have sensenet ECM installed and want an in-place upgrade instead of re-creating the database, please run the upgrade patch (you'll find it above in the Assets list) in your dev, test and live environments to be up to date. The patch is an SnAdmin package.
Note that after executing the patch, you will have to update your sensenet Services NuGet packages to the same version.
sensenet ECM Services 7.0.0 Stable
The stable version of the sensenet ECM Services main component has finally arrived!
New features
- OAuth providers let developers integrate 3rd party services (e.g. Google) for authenticatig users (aka Google sign-in).
Type handling
- Provider store gives developers a simple API for managing replaceable runtime instances for providers (e.g. using a memory db provider instead of a real one).
Packaging
- SetUrl step lets you add a new url to a site declaratively (useful in case of automatic builds)
- MoveXmlElement snadmin step for moving xml elements inside a file or content binary.
- SnAdmin runtime displays a human readable info when a type load exception occurs.
OData
- Extend batch copy, delete and move OData action responses with information about the changed content and the errors that occured during the operation.
Bug fixes
- load types at startup and during runtime without throwing an error if there are ones that are not installed
- Notification class name fixed in source code and config
- Suppress field errors when serving a content through OData.
- close output file stream after editing it in xml editor snadmin step
- binary download is supported with JWT authentication
- sorting has been fixed for batch node load
- we allowed the Everyone group to access several applications by default so that administrators do not have to give permission one by one
- OData REST api returns all the actions in a scenario, not just html ones
- a token authentication control flow bug has been fixed
- give startup user a real id that will let us save content during request startup
- added the necessary http headers for chunked upload
Known issues
In the current release the following features may not work, depending on your environment:
- Windows authentication
- WebDAV
- Open in Office
Installation
To get started please follow the instructions in the Install sensenet ECM from NuGet article.
Upgrade from previous versions
Please export your custom content and perform a clean install, there is no upgrade patch for previous versions for this release.
sensenet ECM Services 7.0.0 beta4
New features
TypeScript 2.4 updates
- generated TypeScript classes take advantage of string-based enums
New packaging steps for SnAdmin
- SetField, AddReference, RemoveReference: new steps for setting or modifying field values during a patch or installation, without importing.
New SnAdmin tool
- delete: it is possible to delete a content from the repository by its path from the command line, you do not have to use the REST or C# api for that.
Bug fixes
- added a missing package reference for the OpenPop library
- added a few missing string resources
Installation
To get started please follow the instructions in the Install sensenet ECM from NuGet article.
Upgrade from previous versions
Please export your custom content and perform a clean install, there is no upgrade patch for previous versions for this release.
sensenet ECM Services 7.0.0 beta3
New features
- Add CORS header and preflight response in case of a JWT token auth request, so that JWT authentication works with CORS.
Packaging
- Allow SnAdmin install packages to be executed multiple times (depends on the decision of the package creator).
- It is possible to create and execute packages that contain the hyphen (-) character in their name.
Bug fixes
- The Open in Office feature works regardless of the file extension casing (e.g. .xlsx/.XLSX).
- Content type header is added correctly to the response, even if the content path casing is incorrect in the request.
- OData parameter inlinecount=allpages results in executing a Lucene query (compile to SQL is not allowed in this case so that a correct full count is served to the client).
- Add missing fieldsetting content types to aid list field management on content lists.
- Allowed child type logic works even if there is a missing content type in the list.
Installation
To get started please follow the instructions in the Install sensenet ECM from NuGet article.
Upgrade from previous versions
If you installed a previous version, please export your custom content before you get the new version:
- export your custom content from the Content Repository (using the export SnAdmin tool)
- upgrade the NuGet package in Visual Studio (from v7.0.0 beta2 to beta3). Make sure you let nuget overwrite your local files with the new ones from the package.
- please remove/cleanup generated package folder(s) from your web\Admin\tools folder: most importantly install-services, so that the new package zip is extracted when you install the component again.
- reinstall the whole Services component. This is a clean install that creates a new db. If you want to use the same db name, use the ForcedReinstall:true switch when installing.
- import your custom data
There is no in-place upgrade for this version, the new dlls would not work with the old database.
sensenet ECM Services 7.0.0 beta2
New features
JWT authentication
JSON Web Token authentication will help client developers connect to sensenet ECM and work with the content repository in a more secure and flexible way.
Packaging improvements
- SQL authentication is supported during installation
- SnAdmin packages support phase-level custom assemblies that are loaded only for the phase that they are defined for.
- New steps:
- Edit allowed child types (on a content or content type)
- IfComponentExists for checking component existence (soft dependency check)
NuGet install improvements
We modularized our NuGet packages to be more flexible: now we have two packages for our components:
- one for web applications, containing content files and web folder material
- a simple, dll-only package for other project types
Bug fixes
- Variable resolution fix in various steps (Export, Index).
- Warning is logged on unknown action instead of throwing an error. This makes OData responses more robust.
- Eliminated several null reference errors when there was no Site content in the system.
- Install logic can deal with existing databases.
- Service action generates a correct url even if the service name starts with a slash.
- Saving the Root content is possible.
- Removed unnecessary custom workspace type references from the User ctd that prevented saving users.
Breaking changes
Packaging
Package manifest structure had to be changed to support the new component model of sensenet ECM.
- Every manifest should contain a component Id and optionally a list of dependent components.
- Package type definition has been simplified.
- Old package structure is not supported anymore, manifest files have to be upgraded.
See the new manifest structure in this article: SnAdmin
Known issues
- Open in Office feature is currently not available (issue #10).
- Windows authentication is currently not available (issue #69).
Installation
To get started please follow the instructions in the Install sensenet ECM from NuGet article.
Upgrade from previous versions
If you installed a previous version, please export your custom content before you get the new version:
- export your custom content from the Content Repository (using the export SnAdmin tool)
- uninstall the previous NuGet package (v7.0.0 beta)
- install the new package (v7.0.0 beta2)
- reinstall the whole Services component. This is a clean install that creates a new db. If you want to use the same db name, use the ForcedReinstall:true switch when installing.
- import your custom data
There is no in-place upgrade for these versions, the new dlls would not work with the old database.