General Drake CMS and server settings
On some servers it is possible to enable gzip compression of all HTTP responses served by Drake CMS
This setting is enabled by default as it will save bandwidth. You should disable it if not allowed by your server or if the server has a very limited CPU power and a lot of small requests (there is a minor overhead in response compression, usually compensated by the lower bandwidth usage).
You can specify here the limit for any uploads retrieved by Drake CMS. The default value is the one retrieved from the PHP configuration at install time; a bigger value will cause errors unless you also update your PHP configuration.
Note 1: if you specify 0 the PHP configuration setting upload_max_filesize will be read and saved into this Drake CMS setting
Note 2: this setting also affects uploads sent through the administration backend
Drake CMS does not tolerate by design any PHP error, warning or notice. Software is not perfect and when these problems happen, they should be addressed by the Drake Team; Drake CMS has an embedded error description mechanism which allows it to properly handle the error conditions. There are three error reporting options available:
- Simple, the picture of buggie
will be displayed and the specific error message will be shown on its right; you should use this setting on production websites as it will not break layout and execution flow;
- Debug, a detailed error report, containing server and client information (but without any privacy-sensitive data) will be generated; this setting will break layout but it is necessary when using non-Stable Drake CMS versions in order to allow developers to fix the bugs
- Auto-submit, like the Debug setting, but automatically sends the error report to the Drake CMS advanced error reporting service; no private data will be collected (e.g. no HTTP_REFERER headers and no IP address, only the content of the debug report)
Five logging settings are allowed:
- Disabled, all log events will be silently discarded;
- Using system log, all log events will be recorded through the syslog() PHP function; be sure that the syslog is working and that you have access to it before enabling this option;
- Using file, all log events will be written to the private/log.php file; be sure that you have write permissions on that file before enabling it;
- By mail, all log events will be emailed to the notification recipients (see Email notifications setting on this page); this setting is not suggested since email sending might be a slow and resource consumptive process depending on your server configuration/resources;
- Custom, all log events will be passed to a custom logging function included from private/custom_logger.php
See Logging for more.
If you specify an URL here (with trailing slash '/'), it will be used to redirect ALL documentation queries sent to docs.php to it. Might be useful if you have different Drake CMS websites in different servers and want to use the fastest one for the documentation (also http://localhost/drake/ for example).
Note: DO NOT specify the same website as URL, unless you want to trigger infinite circular redirections when accessing any documentation page.
The Simple statistics module and Who's online module will activate an internal visits login mechanism when they are displayed; if you want to log visits you should enable this option.
Note: simple statistics logging uses the database to store information, if you are using a flat file database (in particular Gladius DB) it is suggested to not not use the simple statistics as it will slow down the response time.
It is suggested to use a non-PHP statistics system; the best choice would be a statistics system attached to the webserver (your hosting provider might already have this service setup for you).
This setting allows to select a currently installed WYSIWYG XHTML editor, or no editor at all. Read Installing an editor for more.
All pages that might contain spider-sensitive content (looking for keywords and description) will have a suffix on the URL as long as the specified number of characters here.
Admin backend components mostly show tables with entries to be managed; this field will specify how many rows to use for each page into which the table list will be split.
General website settings
This mandatory field should contain the website absolute URL; it is generated automatically by Drake CMS at install time and should usually be edited in case of website relocation.
Note: the website absolute URL should end with a trailing slash '/' since it will be used for the generation of absolute URLs for some particular pages.
This mandatory field should contain the website title (example: Drake CMS website)
This boolean flag (can be On or Off) regulates the online status of the entire website.
By setting your website offline the offline message will be displayed (see below field) and no page will be served through any Drake CMS component. Users authorised to use the administrative backend will be able to access to it using the admin.php page; also, administrators and managers will be able to see the website as online after having logged in.
Note: as of Drake CMS v0.4.2 the documentation interface (docs.php) will always be active, even if the website is offline
This field should contain the offline message shown when the website is taken offline. Its content is not encoded, so it should contain XHTML-valid markup.
Keywords supplied in the META tag before keywords generated for the pathway location
Description supplied in the META tag before the description generated for the pathway location
Note: the specified keywords and description will be used on each page served by Drake CMS, followed by page-specific keywords and description. Feel free not to specify them considering that the specific data will always be automatically generated.
Settings inherent to localization
If your server does not internally use a correct GMT time you might want to offset it using this correction value.
If you will select "Detect from external timeserver (GMT)" an external trusted GMT timeserver will be contacted (if possible) and used to retrieve the offset to GMT time.
This setting allows to specify the default language to be used when the user's language is not available. This is also the language in which content and any other data is written on the website (for example, used to filter common words in search strings)
Note: this is not the website active language, see Language manager for more.
General settings related to the content component
Hide the author name from each content item.
Hide the creation date from each content item.
Hide the modification date from each content item.
Hide the print icon from each content item. It allows to view and print a content-only version of the content item (without template rendering).
Hide the email icon from each content item. It allows to send an email to a friend directly from the website.
Do not edit these settings if you are not sure that the new database settings will work.
A move database feature is currently disabled due to a 3rd party bug in adoDB lite which would prevent it working.
This combo box allows the selection of the database management system on which Drake CMS should run.
The usage of Gladius DB is suggested where MySQL or SQLite or any other professional database management system is not available.
Legend of combo box items:
- Green items for database systems currently available
- Gray items for database systems available on the current PHP installation but not packed with the current Drake CMS (you would just need to add the relative additional adoDB lite driver to this installation package)
- Red items for database systems not available on the current PHP installation (you would need to modify the PHP installation)
Drake CMS will not create the database for you, see Tutorial: creating the database for a detailed explanation about how to create it in some common database management systems.
Note 1: it may be such that your provider does not allopw you to create the database; in such cases your database service provider will tell your assigned database name.
Note 2: you do not need to create multiple databases for multiple Drake CMS installations as they can be seperated through the table prefix (see below)
The table prefix enables you to have different Drake CMS installations and still use the same database
The database hostname is the address on which the database server is located; some database management systems do not require this parameter. For example, it is necessary for MySQL but not for flatfile databases like SQLite or Gladius DB.
The database username is necessary for most databases' authentication. Currently, it is ignored only by Gladius DB.
The database password is necessary for most databases' authentication. Currently, it is ignored only by Gladius DB.
Settings regarding all emails sent through Drake CMS
This setting allows to choose whose email recipients will receive site-wide notification emails regarding:
- frontend item submissions (content, faq, weblink, image, download etc. depending from the installed components);
- contact form emails (with attachments);
- new user registrations (depending from the registration component configuration);
- forum emails (if there are no moderators defined for forum categories, see Forum component configuration);
- log emails (if the relative setting is enabled).
This setting will forcefully convert HTML emails (for example, those queued by the content component on new content submissions) into plain text and send them as text emails.
This setting will force emails sent to multiple recipients through the Bcc header to be split into single emails.
This setting might consume a great amount of resources to send single emails; however, single emails' trust level in antispam systems is usually higher and you can also add the Hashcash header for them. If you have alternative server-side email trusting mechanisms, it is suggested to not use it.
When this setting is enabled all emails sent to a single recipient will be added a X-Hashcash header to increase their trust level in anti-spam systems. If you have alternative server-side email trusting mechanisms you might disable it as the Hashcash header generation will consume from 0.4 to 2 seconds (usually) for each email recipient to be calculated.
Captcha settings for captcha-enabled components