676
edits
Setup Other: Difference between revisions
Jump to navigation
Jump to search
→Agenda Module: AGENDA_ALL_CALDENDARS
Tag: 2017 source edit |
(→Agenda Module: AGENDA_ALL_CALDENDARS) |
||
| Line 169: | Line 169: | ||
*MAIN_ADD_EVENT_ON_ELEMENT_CARD ► Allow to create an event from a document (proposal, order, invoice) | *MAIN_ADD_EVENT_ON_ELEMENT_CARD ► Allow to create an event from a document (proposal, order, invoice) | ||
*AGENDA_ALL_CALENDARS ► Change the default view to calendar for all the Agenda's | |||
[[#Top|(back to top)]] | [[#Top|(back to top)]] | ||
| Line 200: | Line 201: | ||
== Direct Debit Orders == | ==Direct Debit Orders== | ||
*WITHDRAWAL_ALLOW_ANY_INVOICE_STATUS ► If this option is set, all invoices status (even already paid) may appear on the list of invoices qualified for a direct debit payment. This is the list of invoices with a payment request done, and not linked to a direct debit payment. By default, only "unpayed" invoices are used to avoid to pay twice the same invoice. | *WITHDRAWAL_ALLOW_ANY_INVOICE_STATUS ► If this option is set, all invoices status (even already paid) may appear on the list of invoices qualified for a direct debit payment. This is the list of invoices with a payment request done, and not linked to a direct debit payment. By default, only "unpayed" invoices are used to avoid to pay twice the same invoice. | ||
| Line 695: | Line 696: | ||
==For SaaS / Cloud hosting integrators== | |||
== For SaaS / Cloud hosting integrators == | |||
The following options are useless for a common usage of Dolibarr. But they are usefull if you plan to host / provide Dolibarr instances as Software As A Service (SAAS) to your customers. | The following options are useless for a common usage of Dolibarr. But they are usefull if you plan to host / provide Dolibarr instances as Software As A Service (SAAS) to your customers. | ||
| Line 702: | Line 702: | ||
*To avoid bad use of the emailing module, it is recommanded to set the option MAILING_NO_USING_PHPMAIL to 1 (This option is described previously). Also you can complete the message visible by customers when they try to setup the SMTP credentials of their Dolibarr by using the constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS (This option is described previously). For example, you can point to a FAQ on your website. | *To avoid bad use of the emailing module, it is recommanded to set the option MAILING_NO_USING_PHPMAIL to 1 (This option is described previously). Also you can complete the message visible by customers when they try to setup the SMTP credentials of their Dolibarr by using the constant MAILING_SMTP_SETUP_EMAILS_FOR_QUESTIONS (This option is described previously). For example, you can point to a FAQ on your website. | ||
* MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS: Set here the ip of list of ip where your Dolibarr instances are hosted. So when your customer go into the setup area of email, a message will explain him how to setup its SPF record for its email domain. This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers. | *MAIN_EXTERNAL_SMTP_CLIENT_IP_ADDRESS: Set here the ip of list of ip where your Dolibarr instances are hosted. So when your customer go into the setup area of email, a message will explain him how to setup its SPF record for its email domain. This is to avoid to have its emails, sent from its Dolibarr instance, fails due to strict antispam rule of some emailing servers. | ||
* MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE: If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock so the administration tools like install.php and repair.php can't be used on your customer instance (until the lock file is deleted). | *MAIN_ALWAYS_CREATE_LOCK_AFTER_LAST_UPGRADE: If set, when you launch upgrades of your customer instances, you are sure that the upgrade process recreate automatically the file install.lock so the administration tools like install.php and repair.php can't be used on your customer instance (until the lock file is deleted). | ||
* MAIN_FILECHECK_LOCAL_SUFFIX: If you offer a customized or patched version of Dolibarr, when the user will use the tool to chek the integrity of files, the default xml file name used for signature checking will be the official file provided by the Dolibarr team. To have the suggested signature file beeing your own file you can set ths constant to a suffix. For example, set this to "'''-mysaassolution'''". So, when the user will use the file integrity tool, the default file to check for signature will be "'''/install/filelist-mysaassolution.xml'''" instead of "'''/install/filelist-10.0.2.xml'''". All you have to do is generate the signature file '''mysaassolution''' using the tool '''build/generate_filelist_xml.php''' and put this file into the install directory of your customer instance. Doing this, your customer, and yourself, will be able to check if a file was modified without beeing disturbed by false alerts due to your customized files or patches (they are included in the signature used for check). | *MAIN_FILECHECK_LOCAL_SUFFIX: If you offer a customized or patched version of Dolibarr, when the user will use the tool to chek the integrity of files, the default xml file name used for signature checking will be the official file provided by the Dolibarr team. To have the suggested signature file beeing your own file you can set ths constant to a suffix. For example, set this to "'''-mysaassolution'''". So, when the user will use the file integrity tool, the default file to check for signature will be "'''/install/filelist-mysaassolution.xml'''" instead of "'''/install/filelist-10.0.2.xml'''". All you have to do is generate the signature file '''mysaassolution''' using the tool '''build/generate_filelist_xml.php''' and put this file into the install directory of your customer instance. Doing this, your customer, and yourself, will be able to check if a file was modified without beeing disturbed by false alerts due to your customized files or patches (they are included in the signature used for check). | ||
* WEBSITE_REPLACE_INFO_ABOUT_USAGE_WITH_WEBSERVER: Put here a text a a translation key of a text to show when the user will use the feature "Deploy" when he want to deploy a website done with Dolibarr CMS. So you can, for example, show him a message that this feature is not part of is subscription and putting a website online may need a complementary subscription. | *WEBSITE_REPLACE_INFO_ABOUT_USAGE_WITH_WEBSERVER: Put here a text a a translation key of a text to show when the user will use the feature "Deploy" when he want to deploy a website done with Dolibarr CMS. So you can, for example, show him a message that this feature is not part of is subscription and putting a website online may need a complementary subscription. | ||
* CRON_DISABLE_KEY_CHANGE: When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]]. | *CRON_DISABLE_KEY_CHANGE: When you provide an instance to a customer, you probably also add an entry in the cron of this user so Dolibarr batch and scheduler can work correctly. For security purpose, it may have a security key that is inside the command line into the cron entry and this entry must match the value defined into Dolibarr setup (setup of module 'Scheduled Jobs'). Because, a customer of a Saas platform will probably have no access to edit the cron file, it is also import that he has no way to edit the key into the Dolibarr setup, so the key in the cron command line will always match the key in Dolibarr setup, and the Dolibarr batches will executed without security errors. To be sure, the customer does not change the value, you can set this constant to 1 into the table [[Table_llx_const]]. | ||