This is the documentation for concrete5 version 5.6 and earlier. View Current Documentation

All paths listed in this document depend on how you’ve build up your server. All paths listed will be the ones I used on my server.

Setting up. The setup is done as follows. Get a single virtual environment on your server which is accessible through FTP.

In that environment place the directories needed for whatever you wish to centralize. In my case: themes, languages & blocks

What else do you need? A single development environment where you design your themes, test your blocks and test the language files.

How to make it work on new sites? Go to the environment you wish to use it on by using a command line interface. Unpack the concrete installation package and remove for example the folder themes. After you removed it you need to make a symlink to the central themes folder. (ln –s themes)

By doing this you can access all themes in the central environment. Of course this is only useful if you reuse you designs.

This option however is useful for placing blocks which you use more then once or even on all websites and for placing language files on a central spot. This way when you update a language file it updates for all sites which use it.

For the language files you do need to add a line to your site.php to get it working. The next line needs to be added for it to work: define("LOCALE", 'nl_NL'); In the above example it uses a Dutch language file, replace the nl_NL by the language you wish to use.

Warning Do not use this on the packages folder since then you won't be able to download from the market place. I also suggest keeping the packages folder normal to use it for your purchased packages with licences

Loading Conversation