Auto-storage mode of configurations
This is the default. It is a hybrid mode that stores configuration files on both the file system and the database in table
- Environment configurations that are part of the system setup are stored in the file system.
They are part of the deployment process of the web application and you distribute them as files between different environments.
Such configurations are the following:
- Advanced settings
- Basic settings: Connector for Telerik BaaS, Connector for SharePoint, Connector for Marketo, Connector for SalesForce, Connector for Digital Experience Cloud, Timezone, Social sharing, User authentication, Google maps, Search, Thumbnails, Storage providers, Twitter, Text editor, Languages, Email campaigns, Responsive design, Recycle bin, Translations, Analytics, Sitemap.
- Startup wizard
- Application settings that are part of the Sitefinity CMS website and are modified runtime are stored in the database.
Turn on Auto-storage mode of configurations
To turn on Auto-storage mode on your project, perform the following:
- Open you
- Make the following transformations:
- Save and close the
web.config and restart the application.
The storage of some of the configuration files is moved to the database in table
[sf_xml_config_items]. The existing configurations are taken as default. The files in ~/App_Data/Sitefinity/Configuration folder whose configurations are moved to the database are made read-only and any future changes to the .config files are written to the database where each server can access them.
IMPORTANT: You must not remove existing configuration files from the project's ~/App_Data/Sitefinity/Configuration folder, because Sitefinity CMS continues to use them to read the default values. Only new changes are written to the database.
Explicitly save configurations on the file system in Auto mode
When the system is in Auto storage mode, if you want to save a configuration intentionally on the file system, you can use one of the following methods:
FileSystemModeRegion in the following way:
SaveSection overload method: