Advanced Configuration Options
When installing concrete5, the file config/site.php is created. This contains certain settings that have to be set for the program to run. Additional constants can be defined in this file. Here are some of those options.
Enable Advanced Permissions
Concrete5's permissions out of the box allow basic website access control, but if you need more options, you should try out our advanced permissions. Advanced permissions allow any combination of users and groups to be assigned to the following:
- Page-specific Access
- Adding, editing, reading versions and deleting pages
- Being able to add only specific page types to specific sections of sites
- Area-specific control
- Block-specific control
To enable advanced permissions, add the following line to "config/site.php":
<?php define('PERMISSIONS_MODEL', 'advanced'); ?>
Specify Valid Files for Uploading
This is now done through the Dashboard UI. Goto Dashboard > File Manager > Settings
Disable Automatic URL Redirection
By default, Concrete5 will forward any requests to your site to the specific BASE_URL you define when installing. This is for cookie/session authentication purposes. If you'd like to disable this to ensure that your site is served at multiple URLs, add this line to your site/config.php:
<?php define('REDIRECT_TO_BASE_URL', false); ?>
Specify your site's language
Once you've followed the instructions on how to download and install a concrete5 language pack, you'll have to modify config/site.php to use this language. If "de_DE" (German) is your new language, add the following to config/site.php:
<?php define('LOCALE', 'de_DE'); ?>
Change where the Help link points
<?php define('MENU_HELP_URL', 'new url');?>
Cache Engine (5.2.0 and above)
By default concrete5 (v5.2+) uses a custom PHP cache to improve performance. This can be swapped out with different implementations of the cache. Currently, only an eAccelerator-based version of the cache is available, and it's support is experimental, but you can try it by defining:
<?php define('CACHE_LIBRARY', 'eaccelerator'); ?>
Comments:
[code]
if (!defined('SITE')) {
Config::getOrDefine('SITE', 'concrete5');
}
[/code]
Anyone?
Thanks in advance.
p.s.: The block is the main nav, and is part of the theme template -- don't know if that makes a difference or not...
Do you have an example or documentation on how to perform this task?
"Is it possible to restrict a Group's access right down to not even being able to see the dashboard, to only editing pages, not even being able to add a page?"
goto sitemap.
check the box in the lower right " Show System Pages"
set permissions on the new pages that show up in the sitemap.
enjoy.
Do you have an example or documentation on how to perform this task?
"Is it possible to restrict a Group's access right down to not even being able to see the dashboard, to only editing pages, not even being able to add a page?"
Do you have an example or documentation on how to perform this task?
"Is it possible to restrict a Group's access right down to not even being able to see the dashboard, to only editing pages, not even being able to add a page?"
