Availablity of extensions
The biggest difference is the availability of extensions/add-ons/extra-integrations -- there are more addons for Civi+Drupal, but the differences are shrinking over time.
Civi 1.x didn't originally support its own extension mechanism - the only option was to write a Drupal module. Consequently, Civi-Drupal modules grew first/...
We struggled with this initially. Things we went through:
Check the debug console in Chrome to make sure Civi isn't having trouble finding resources - look for 404s in the Source tab. This can slow down Civi tremendously as it waits for them to time out. Can be fixed in the Admin -> Resource URLs / Directories / Update Paths
If you're running PHP 5.3, get ...
Besides what Tim wrote, it is currently still important to note that most people use it with Drupal. This means Drupal integration has the least amount of bugs and more active maintenance, which is even more significant in the context of the long term support (LTS) releases.
I'd originally started my Civi 'journey' by bolting it onto our existing Wordpress site, and that was fine for holding contact details and sending out bulk emails/SMS.
As we started to use Civi more though, it became quickly apparent that we couldn't do many of the things in Wordpress that we'd like to. The lack of an equivalent to the Drupal webform ...
If you're using Drupal, Webform-CiviCRM Integration will handle your scenario pretty easily. It allows registering any number of participants for any number of events on a single form.
You may also want to e-mail Sarah Gladstone, the author of the Youth Registration extension, what she uses instead - but I'm pretty sure they use Webform-CiviCRM integration ...
CiviCRM has a built in form builder which are called Profiles. It's not as powerful as Webform integration, but may fit your needs.
If not, the equivalent for WordPress would be Caldera Forms with CiviCRM integration.
I think the big differences relate to architectural differences between the three, and of course all come about as you increasingly seek to integrate between the CMS side and the CRM side. If you just want to use the core CRM it is self contained. So in Joomla you really use plugins (that respond to event triggers) and modules. Once key difference is that ...
Yes, CiviCRM works fine with WordPress on Nginx. However, since Nginx doesn't use .htaccess you'll want to add any changes to your site-specific configuration.
For example, there are a few upload directories that have .htaccess files denying access to their contents. To do the same thing in Nginx, you'd want to add a location block to your site's ...
This is a bit of "surprise" but essentially for 4.6 and beyond Civi event registration for Wordpress won't work unless you either 1) use a 'base page' or a 2) WP short code
Solution #1 has two steps.
create a WP page with the 'civicrm' permalink
set a 'base page' within CiviCRM
See attached images.
Migrating from Drupal/Civi to Wordpress/Civi is relatively painless. You'll need to truncate your civicrm_uf_match database table, which links Civi records to CMS users, and repopulate it - Administer menu > Users and Settings > Sync Users to Contacts works well if you want ALL your Wordpress users to be linked up.
That said, there are numerous gotchas to ...
The URL formula is different for each CMS. The most accurate approach is to open a CiviCRM page and examine its URL. For example, I logged into the public demo sites for v4.5, navigated to "Contributions => Dashboard", and the URL of each page:
You should also consider giving your staff their own personal user accounts for a number of reasons.
It will be clear that they're acting as themselves rather than as a generic staff person
You can isolate the culprit(s) who are recording memberships the wrong way (see Jon's answer), meaning they don't cause problems for others and you can talk with them ...
CiviEngage, at the moment, is a Drupal module that currently ships with the official CiviCRM Drupal release (see https://github.com/civicrm/civicrm-drupal/tree/7.x-master/modules/civicrm_engage, which ends up installed in sites/all/modules/civicrm/drupal/modules/civicrm_engage). That means you won't find it on drupal.org or any other drupal module site and ...
Below are the simplified instructions taken from Moving an Existing Installation to a New Server or Location, but specific to answer your question.
Open the file wp-content/plugins/civicrm/civicrm.settings.php in any text editor and change the value for CIVICRM_UF_BASEURL with your new domain name
For CiviCRM Version 4.7 open the file wp-content/uploads/...
Summarising the above conversation:
The upgrade of PHP to version made the PEAR DB extension unavailable. So the exception "DB Error: extension not found" was thrown.
Changing to the database connection URL in the civicrm.settings.php using the prefix mysqli solves the problem.
Contributing or sponsoring upgrades to the youth-registration extension seems like a good option for you. The extension has already been written and seems to need minimal maintenance to get it working with the latest version of CiviCRM.
Short of that, your current options are limited. You could set up your registration form in such a way that the child's ...
Ideally, the day-to-day workflow of entering contributions/memberships for your staff should be to use the back-end forms, not the front-end forms, so you don't experience this. However, to help with this transition, you may want to consider installing the "no overwrite" extension, which prevents the problem you're describing: https://civicrm.org/extensions/...
The CiviCRM Gravity Forms integration by CiviVIP is looking like a good first step towards full integration with CiviCRM. Currently it has integration with multiple contacts (that can be linked via relationships) and activities. I think event registration and contributions are on the list of features currently being developed. Nathan's presentation at ...
Going by the shortcode function, there are five possible ways to use the shortcode.
Technically there's only one shortcode used ([civicrm]) but it uses the component attribute to switch between different content.
The five possible components are:
Contribution: [civicrm component="contribution" id="x"]
shows a contribution page specified by the id ...
The problem isn't WordPress, but Hostmonster. Shared hosting makes its money on sites that don't need any CPU or memory - simple WordPress sites, for instance.
CiviCRM is a much more resource-intensive program than your typical CMS (like WordPress). If you have good shared hosting - which is hard to come by! - then you can sometimes run a very small ...
Mosaico doesn't create any custom data in CiviCRM, so it is safe to Uninstall the extension. However, any template created in Mosaico will be lost.
To uninstall the extension you will need to disable it.
PHP 7.2 does not have the mcrypt module, and the Sparkpost extension needs that module. If you can install php7.2-mcrypt as a pecl module Sparkpost will work. If not, I would move to php 7.1 for the time being.
I encountered the same problem and investigated a bit further...
The SparkPost extension does not directly use mcrypt but it does use CRM_Utils_Crypt which makes use of mcrypt if it is available.
If you upgrade to php 7.2 without mcrypt and you already have an API key saved, the result is that the extension cannot decrypt the key. That's why the ...
Can we verify a few things?
What are your WordPress permalinks set to?
They should be Post Name (%postname%) That setting is here: example.com/wp-admin/options-permalink.php
This will add to your .htaccess file the following:
# BEGIN WordPress
RewriteRule ^index\.php$ - [L]
A new alternative to Gravity Forms is Caldera Forms with CiviCRM integration. Unlike the Gracity Forms integration, development is active and it now far surpasses Gravity Forms integration in functionality.