IMPORTANT: This version of Sitefinity CMS is out of support and the respective product documentation is no longer maintained and can be outdated. Use the version selector to view a supported product version.
The following table summarizes the most common questions that may arise when you start working with the new content editing experience, along with answers.
The new content editing experience is switched by default. Thus, it is available for all Sitefinity CMS users.
You can always switch back to the classic interface. Any user can choose for themselves whether to switch back and forth.
NOTE: If the Administrator explicitly switched off the new interface, users cannot toggle between the interfaces.
For more information, see Toggle between new and classic experience.
In terms of content management experience, you can leverage most features of the classic interface. Generally, when you edit content in the new interface and you need to work with a specific content type, not yet supported in the new interface, for example Forums, the system automatically falls back to the classic interface. Thus, your work continues seamlessly and without interruption.
Another example is if you need to revert to a previous version of your content, you can still use the Revision history functionality but it will be rendered in the classic interface design. For a comparison between the interfaces, see Reference: New content editing experience and the classic interface.
Ideally, the new experience will meet the needs of users in your organization, dealing with content creation, editing, and management. In case someone needs access to a feature or tool back in the classic interface, they can switch back and forth whenever they need.
If a functionality, not related to content types, is not yet supported by the new interface, you can enable users to switch back to the old interface.
Customizations you made via the Module Builder or custom fields are supported in the new interface.
You can also easily customize the new Admin App interface via the Extensibility API. For details and examples, see GitHub, along with examples.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important