This plugin helped me to deliver a multilingual setup with different domains (one domain per language). It does a l…
CURRENTLY THIS ADD-ON IS NOT COMPATIBLE WITH concrete5 v8!
The highly rated (5/5 stars as of August, 2015) Multiple Domains add-on is now available for 5.7!
NOTE: PHP 5.4 is required for this add-on to work properly. Make sure your server is running PHP 5.4 or newer prior to your purchase!
Currently this add-on is not compatible with concrete5 version 8.0+.
BEFORE YOUR PURCHASE, PLEASE READ THIS!
We will not refund your purchase in case you fail to read this guide PRIOR to your purchase.
This add-on lets you manage sites for multiple domains within one single concrete5 installation.
It provides the possibility to map different domains to different nodes within your site to specific domains you host. This allows you to easily run multiple sites within a single concrete5 installation.
Please note! This add-on requires you to know how to setup each domain to point to your site and also requires you to know something about setting up virtual server configurations on your web server. Please read the Before Your Purchase page along with the add-on documentation (Server Setup and Documentation) prior to your purchase to understand what is required from you and your server. It is not part of our support plan to help you with your server configuration, although we can provide that help for you for an additional fee.
You should note that the add-on is meant to be used only for simple cases. It is not a fully fledged granular configuration system that would allow you to built completely separated environments (including separating assets such as users, files, etc.) within a single concrete5 installation. If you need site specific assets (files, users, etc.), make multiple installations.
Some example use cases on in which situations this add-on might come handy:
With this add-on the output for each user who browses your site will look 100% like they were browsing these sites normally if each site was behind its own system.
The site paths written at the end of each domain will show from the level up which is marked as the "domain parent page". Therefore, a typical mapped domain would look like this: