Closed kcristiano closed 9 years ago
There is, if you're prepared to sacrifice functionality - the plugin just won't receive callbacks from Civi events such as creating or updating memberships.
However, there really is no need to alter any core CIviCRM files. As the readme says, just put the file civicrm_custom_php/CRM/Utils/Hook/WordPress.php
in a path such as: /wp-content/plugins/files/civicrm/custom_php/CRM/Utils/Hook/WordPress.php
and then tell CiviCRM where to find its resources by going to Administer --> System Settings --> Directories and fill that out appropriately.
Thanks for the advice on the status of WordPress integration in the Civi community. I'll have another go at interesting people in my solution.
Is there a way to use this without 'CiviCRM WordPress Hook Tests'?
I (in general) don't like to alter core files on client installs, so this makes me a bit apprehensive. If this is a necessary add on, have you attempted to get the core team to incorporate your changes? If so and it was not successful, this may be a time to try again as I am seeing them very open to WordPress specific changes.