Export and import basics

In this release we continued working on moving features from the service code base to the public sensenet base package to give more users access to more scenarios.

Features

• We started working on a modernized export/import feature. The first steps - most importantly an import action - are available in this release.

Bug fixes

• A NodeQuery children query error has been fixed for nonexistent parents.

Testing and infrastructure

• In order to move the core package closer to what SNaaS users see, we moved a couple of default groups and permissions to the base package so that they are available for standalone users.
• The ClientStore feature has also been moved to the core package from the SNaaS code base.
• The allow all wildcard has been added to the list of default CORS domains to support automatic standalone install scenarios.

Installation

To get started please visit docs.sensenet.com.

Automatic data and index installation

In this release we started to work on enabling more scenarios for sensenet. In the last year or so we focused mainly on our service offering (sensenet as a service). Now it is time to let developers install a standalone version of sensenet, independently from our service infrastructure. To enable this we started to add features and enhancements to make the install process easier and more modern.

Features

• Automatic data install: this is a step toward a fully automatic self-contained install package inside a web application.
• Automatic index creation: if the index is not present when the repository starts, we automatically create it be re-indexing the database. This helps with installing sensenet more easily.

Bug fixes

• The install package compress PS script runs correctly in a Linux environment.

Testing and infrastructure

• In this release we updated the security infrastructure to use instances instead of a static API.
• We moved a couple of infratructure actions from the SNaaS code base to the core product to let our admin user interface access them.

Installation

To get started please visit docs.sensenet.com.

Statistics

This release contains a few new features and improvements to support the sensenet service infrastructure.

Features

• Introducing the new statistics feature: it lets us track the number of web requests, sent webhooks and a couple of similar events so that administrators have a better understanding of the behavior of the repository.

Testing and infrastructure

• We have updated Microsoft.Extensions and task management package references, you may need to do the same in your project to be compatible with this release.
• We also removed the Preview package dependency from core sensenet libraries.
• We continue to refactor our internal APIs to support a service infrastructure. This time we modernized the schema and node type system to work as instances.

Installation

To get started please visit docs.sensenet.com.

Richtext field

This release contains a few new features and bug fixes to support the sensenet service infrastructure.

Features

• You can use date and time templates (today, previous month, etc.) when defining the minimum or maximum values of a date field.
• A new field type, rich text field was added to let client-side editors work more freely. This lets us store richtext values in a more structured way. Frontend developers have the possibility to expand the value of a richtext field (or all of them) using the OData api to have access to the structured and the raw data in one round.

This version also contains a patch that will upgrade long text fields that were configured to be displayed as rich text to this new field type.

Bug fixes

• An incorrect timeout value caused the access token module to throw an ArgumentOutOfRangeException.

Testing and infrastructure

• We ported many unit and integration tests from the old infrastructure to have a better code coverage.

sensenet as a service improvements

• We refactored our data store API to work as an instance. This is part of our ongoing effort to make our apis more easy to test and work in a dependency injection environment.
• Now users will get explicit permission on their profile workspace to let them work more freely in that part of the repository.

Installation

To get started please visit docs.sensenet.com.

Deleted events and new configuration possibilities

This release contains a few new features and many bug fixes to support the sensenet service infrastructure.

Features

• We consolidated Deleted content events. Move is not fired anymore when deleting to the Trash, and Delete/DeletePhysical events are fired when appropriate.
• Added new field configuration for setting the minimum and maximum value for a DateTime field.

Bug fixes

• Several string resource identifiers appeared on the UI after creating a new resource content. We fixed this by restarting the string resource handler on the backend when necessary.
• There was an EntityNotFoundException when editing member list of a group containing nonexisting member ids.
• We hid the unnecessary field Owner when visitor from the UI to avoid confusion.
• There was a typo in the GetVersionInfo action response.
• We added a new identifier to OData operations so that the client can tell apart different actions that have the same name.
• OData expand works correctly for see-only content items and available head-only fields.
• Removed some old and unnecessary APIs related to NodeType creation.

Testing and infrastructure

• We moved many of our old MS SQL, AccessToken and FieldIndexHandler tests to the new test infrastructure.

sensenet as a service improvements

• Now it is possible to trigger a webhook manually for testing purposes.
• We are working on modernizing our backend classes to work with dependency injection. This time we added new ways to register the security data provider and to configure connection strings.

Installation

To get started please visit docs.sensenet.com.

WebHook payload and blob test infrastructure

This release contains a new WebHook feature and several internal features and bug fixes to support the sensenet service infrastructure.

Features

• Our WebHook module is now able to send a custom payload when a webhook is triggered. This lets developers connect to already existing 3rd party services.

Bug fixes

• We consolidated many of our built-in content type icon names so that the frontend can use a unified icon set.
• The Type field value was missing from the OData response in some cases.

Testing and infrastructure

• We are in the middle of moving our old tests to the new API that is able to handle integration tests in a unified way. In this release we moved our blob tests to the new test project.
• We improved reference property handling in our in-memory database so that tests can work in a unified way.
• Added caching for index documents so that the document is generated only once when needed.

sensenet as a service improvements

• To aid our admin UI dashboard, we added more information to the version info action result.
• We are working on modernizing our backend classes to work with dependency injection. This time we refactored our binary layer to work with instances instead of a static API.
• Added a new logger option during patching to let us collect more detailed messages during patching.

Installation

To get started please visit docs.sensenet.com.

sensenet WebHooks

This release contains bug fixes to support the upcoming service infrastructure and the new WebHooks feature.

Features

• The first version of WebHooks is released! You can start subscribing to events and receive them in a 3rd party service.

Bug fixes

• Predication engine is able to run on Delete events correctly.
• Removed http (non-secure) support from the WOPI feature. We support https-only connections from now on.
• Workspace name length was too restrictive, it is possible to create workspaces with names up to a 100 characters from now on.

sensenet as a service improvements

• We extended the DB usage informatin provided by the repository.
• We started to work on modernizing our data layers to use the .Net dependency injection infrastructure.
• Field ordering and visibility has been rearranged in several built-in CTDs to make the UI more straightforward.

Installation

To get started please visit docs.sensenet.com.

Event basics and infrastructure fixes

This release contains bug fixes and minor features to support the upcoming service infrastructure.

Bug fixes

• Importing in a Linux environment works correctly.
• Group membership editing works correctly in case the group contains identities that the modifier does not have permissions for.
• The GetVersionInfo action displayed an outdated version information after multiple patch executions.
• The Content Type system allowed the registration of incorrectly defined fields which led to a broken schema.

sensenet as a service improvements

• We started working on an event infrastructure that will provide the base of the upcoming WebHook feature.
• It is now possible to add custom middlewares before or after our conditional middlewares when registering sensenet pipeline elements during app start.
• We extended the Save query action with a new filter field to aid the UI with a structured query storage. It is also possible for saved queries to contain template elements (like @@CurrentDate@@).
• We renamed the Browse action to Details to clarify its meaning and defined a new field control for the file size field.

Installation

To get started please visit docs.sensenet.com.

Developer and content management improvements

This release contains bug fixes and minor features to support the upcoming service infrastructure.

Bug fixes

• Users with only preview permissions could not access preview images.
• Copy and Move operations have been fixed for cases when working in content lists.

sensenet as a service improvements

• We started to clean up and simplify the built-in default Content Type definition xml.
• Client developers will not see unnecessary OData system action parameters when using the command executor in admin UI.
• Backend developers are able to define strongly typed enumeration parameters for OData actions instead of having to parse strings manually.

Testing

• We started to work on a new integration test framework to be able to test our changes more quickly and reliably.

Installation

To get started please visit docs.sensenet.com.

Public admin and user registration improvements

This release contains bug fixes and minor features to support the upcoming service infrastructure.

Bug fixes

• Fixed a datetime minvalue issue by using the built-in .Net datetime minvalue instead of the old SQL value, which was too restrictive.
• From now on we save longtext values in unicode format to prevent loosing some characters.
• When an OData post contained certain special characters (the '=' or '&' sign for example), the server parsed it incorrectly.
• A protected group's initial import runs correctly, even if there are no real users in the group yet.

sensenet as a service improvements

• We added a new public admin user to let customers create different types of clients that work with the repository.
• When users register to SNaaS using their external accounts (Google or GitHub) and we already have the user in the system, we'll simply merge these accounts.

Installation

To get started please visit docs.sensenet.com.