Timeline for Separate sites for CiviCRM and public site?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2017 at 13:06 | comment | added | ErikH - CiviCooP | The issue we face a lot of time is also that we need quite a few extensions. And the user really then should test the complete processes everytime a Drupal security update is installed. So separating is usually the best option for the bigger customers we have. | |
| Sep 26, 2017 at 11:34 | comment | added | KarinG - Semper IT | Of course the most secure setup would be to go back to on-premise desktop CRM installs; I think the key point if you engage webform_civicrm eg is to ensure your Drupal is at the same level of security as your CiviCRM - down to every single module one is considering to add. It's the weakest link that will provide a way in; | |
| Sep 26, 2017 at 6:55 | comment | added | ErikH - CiviCooP | That is a choice we usually explain to the customer? If they want the most secure set up they loose Webform CiviCRM. It is a question of priorities. But there is github.com/CiviMRF/cmrf_core. Some of our customers prefer the server separation and specific forms. | |
| Sep 25, 2017 at 15:30 | comment | added | KarinG - Semper IT | What about webform_civicrm module on a Drupal/CiviCRM -> would you not want to leverage that? | |
| Sep 25, 2017 at 15:13 | comment | added | ErikH - CiviCooP | The latter! So have a separate Drupal/CiviCRM. Having them on one is a bit like having your gold room next to the public entrance? | |
| Sep 25, 2017 at 13:39 | comment | added | KarinG - Semper IT | Or are you saying if you have a Wordpress public (example.org) site -> have a separate Drupal/CiviCRM (secure.example.org) | |
| Sep 25, 2017 at 13:10 | comment | added | KarinG - Semper IT | Are you saying the most secure option is Standalone CiviCRM? | |
| Sep 25, 2017 at 8:06 | history | answered | ErikH - CiviCooP | CC BY-SA 3.0 |