Product support

Get help in the plugin support forum.

  • Added on Sep 29, 2017
  • Current version: 1.1.1
  • Created by


Flat file storage that OctoberCMS provides by default is perfect, but sometimes you may want to store your content in a Database. It can be more convenient for scalable solutions or git deployment workflow and maintenance.

With this plugin you can store any content you want in a Database. The plugin uses standard October Models - that means it does support any DB that OctoberCMS supports by default. You can easily manage what type of content should be stored in a DB: layouts, pages, partials, content. You can choose all of them or the particular ones.

This is a lite version of the plugin that is currently in active development stage. At the moment the DB structure of content is simple and straightforward, reflecting the file structure that OctoberCMS provides out of the box. In further versions we will make DB structure more detailed to allow usage of relations and become more flexible for extension purposes.

Please note: While the plugin is on, OctoberCMS is looking for content in the DB, which is empty at the very beginning, so you will get PAGE ERROR message while trying to reach your existing pages. At the same time, the content is not removed or corrupted in any way (the files remain at their place untouched).

Settings page


Click Install plugins button in System / Updates & Plugins section in backend settings and search for DB Storage Lite or Axmit.Storage, then install the plugin. Once the plugin is installed, a new settings page called Storage Settings will appear within CMS settings category in backend settings.

Settings You can disable (by default) or enable DB storage and choose what kind of CMS content you want to be stored into DB.

Usage Create / Update / Delete all the CMS content just as you did it before. According to your settings the content will be stored in the DB or flat file structure automatically.


Hotfix: Empty directories settings crushed adapter is fixed now

Oct 02, 2017


CMS content DB table created

Sep 29, 2017


First version of Storage

Sep 29, 2017