← Back to Multiple Websites Manager Lite Support
I want a Multi-site environment, where using one installation of OctoberCMS, I will be able to manage different Websites with the same set of Plugins but completely different Theme/Contents.
- Different Top-Level Domains like a.com (Parent Site), b.com (Child Site), c.com(Child Site), d.com (Child Site) and so on....
- One OctoberCMS Filebase.
- Different Databases for each Child Sites
- Different Themes for each Child Sites.
- Same Plugins can be shared for all Child Sites.
- Different Contents for each Child Sites.
- Different User Account for each Child Sites
Possible to do using this plugin?
Last updated
Hi shivaji36041,
Thank you for your interest in my plugin. This plugin targets businesses that have multiple simple websites that are managed by the same users (e.g. niche sites). It exists for convenience purposes only.
With this plugin you are able to have:
- Different Top-Level Domains like a.com (Parent Site), b.com (Child Site), c.com(Child Site), d.com (Child Site) and so on....
- One OctoberCMS Filebase.
- Different Themes for each Child Sites.
- Same Plugins can be shared for all Child Sites. - please beware of the legal restrictions for paid plugins!
- Different Contents for each Child Sites - static (file-based) content only.
Please beware of the legal restrictions for paid plugins! You need either a Regular license for each site or an Extended license.
With this plugin you are NOT able to have:
- Different Databases for each Child Sites and for this reason no...
- Different User Account for each Child Sites ...and no...
- Different database for your plugins for each Child Site
This plugin is not intended to be used in any SaaS-like construction and all October CMS licenses specifically forbid this. You need either a Regular license for each site or an Extended license.
Last updated
Hi shivaji36041,
Please note that it is possible to specify different databases:
If you decide to follow this route, October CMS also stores things like plugin data and plugin version info in the database. The question thus becomes: in what database? For this reason you are likely to run into multiple issues even if you start with a copy of your existing database for different sites.
Example
Site "A" might update a plugin: this changes the source files for all domains but it only changes the database for site "A". So all other domains (sites "B" - "Z") may automagically share the new source files but they still use their own (old) database: issues will result.... many issues.
I would strongly advise you to keep a separate codebase for sites that belong to different users
Last updated
1-4 of 4