The first time a WordPress version of CiviCRM was available it was [version 4.1](https://civicrm.org/blog/yashodha/announcing-civicrm-41) back in February 2012. It has now been more than 5 years, and I thought it would be nice to outline what has happened since WordPress became available as a CMS option for CiviCRM.
I had been working with CiviCRM on a few sites prior to that, and was looking forward to a time when we could use CiviCRM with WordPress. As with most beginnings, things were a little rough around the edges as WordPress developers learned more about CiviCRM and vice-versa. Later the same year, in October 2012, version 4.3 [ACLs were added](https://civicrm.org/blog/rajesh/wordpress-access-control) and the [first version of a plugin](https://civicrm.org/blog/jag/wordpress-civimember-role-sync-plugin) CiviMember Roles sync was available (which is no longer maintained, so keep reading!). About a year later, another plugin become available to display [CiviEvents in a widget](https://civicrm.org/blog/andrewhunt/civievent-widget-for-wordpress) and [CiviCRM Contribution Page Widget](https://wordpress.org/plugins/civicrm-contribution-page-widget/) by [AGH Strategies](https://aghstrategies.com/). These were the initial enhancement and integrations that came about in the first two years.
At the same time, the CiviCRM community was placing more emphasis on CMS-independent extensions (this initiative actually pre-dates the WordPress integration), as it started in [version 3.3](https://civicrm.org/blog/michal/civicrm-extensions-framework-taking-33). This focus has been extremely beneficial to WordPress, as it lets us extend all the latest CiviCRM enhancements to WordPress users. We are extremely grateful to all the partners and developers who have worked on extensions that make CiviCRM, as a whole, a more versatile application.
We at [Tadpole Collective](https://tadpole.cc) started focusing on WordPress and CiviCRM implementations early. It took us time to learn how these two applications interacted with each other, but we started finding ways to contribute to improvements. That is when [Kevin started going to sprints](https://civicrm.org/blog/kcristiano/dc-sprint-drupal-and-joomla-and-wordpress). He's been at a few since and [his contributions](https://github.com/kcristiano/) have helped improve integration between WordPress and CiviCRM immensely. Since our work also involves theme development, we created a [CSS Helper extension](https://develop.tadpole.cc/extensions/cc.tadpole.csshelper.git), which helps manage the CSS output of CiviCRM pages on the frontend, and provides filters for easier customization in theme development.
Another longtime contributor is [Christian Wach](https://github.com/christianwach), whose initial deep dive is documented in [Working with CiviCRM 4.6 in WordPress](https://civicrm.org/blog/haystack/working-with-civicrm-46-in-wordpress). He has been instrumental in a number of improvements to the integration and has some must have plugins for WP/Civi installs, which are:
* [CiviCRM Admin Utilities](https://wordpress.org/plugins/civicrm-admin-utilities/)
* and if using CiviMember [CiviCRM WordPress Member Sync](https://wordpress.org/plugins/civicrm-wp-member-sync/)
These were the first two plugins he released to the community. He also has a couple [BuddyPress](https://buddypress.org/) plugins:
* [BP Groups CiviCRM sync](https://wordpress.org/plugins/bp-groups-civicrm-sync/)
* [CiviCRM WordPress Profile sync](https://wordpress.org/plugins/civicrm-wp-profile-sync/)
So if you are using BuddyPress, you should check those out.
Recently he has developed [CiviCRM Event Organiser](https://github.com/christianwach/civicrm-event-organiser), which requires [Event Organiser plugin](https://wordpress.org/plugins/event-organiser/); and we have worked with him on a new plugin, [CiviCRM Directory plugin](https://github.com/christianwach/civicrm-directory). These last two are currently only available on Github, as they are still in active development.
[//]: # (Should we bullet this list for readability?)
In searching around the web for development that has been done over the last two years, I found the following:
* [WooCommerce Integration](https://civicrm.org/blog/parvez/woocommerce-integration) by [Veda Consulting](https://vedaconsulting.co.uk/)
* [Contact Form 7 CiviCRM integration](https://wordpress.org/plugins/contact-form-7-civicrm-integration/) by [CiviCoop](https://www.civicoop.org/)
* [CiviRules actions/triggers that interact with WordPress](https://github.com/CiviCooP/org.civicoop.wpcivirules) by [CiviCoop](https://www.civicoop.org/)
* [WordPress plugin with shared WP+CiviCRM integration code](https://github.com/CiviCooP/wpcivi-shared), which documents that it has Gravity Forms integration by [CiviCoop](https://www.civicoop.org/) .
* and a Premium plugin for [Gravity Forms integration](http://shop.civivip.com/civi-plugins/gravity-forms-integration/).
I reference these to highlight the work that has been done, and highly recommend testing them before using them to ensure they work as intended and meet the needs you are wanting.
More recently, in the past year, [Andrei Mondoc](https://github.com/mecachisenros/) has released [Caldera Forms CiviCRM (CFC)](https://github.com/mecachisenros/caldera-forms-civicrm) (which is dependent on [Caldera Forms plugin](https://wordpress.org/plugins/caldera-forms/)). This plugin has provided an incredible amount of flexibility in how data can be captured on a form and processed into CiviCRM. It's a huge enhancement to the WordPress integration. I have worked with Andrei to report any bug imaginable, and he has been incredibly responsive. Andrei also did a huge rewrite to the [WooCommerce Integration v2.0](https://github.com/veda-consulting/woocommerce_civicrm/pull/16), with more to come!
Lastly, I want to give a quick shout out to [Agileware](https://agileware.com.au/) who is a recent contributor to the CFC integration.
There are now at least [2,300 active, WordPress-based CiviCRM sites](http://stats.civicrm.org/?tab=sites). We are seeing more and more folks joining the WordPress channel at [chat.civicrm.org](https://chat.civicrm.org/civicrm), and an increasing number of contributors to the [WordPress integration](https://github.com/civicrm/civicrm-wordpress/graphs/contributors), which is very exciting to see! If you haven't checked into these channels yet, please do.
Moving forward, we hope to continue increasing the collaboration around the work that has been started, developing enhancements to support this integration. We are committed to supporting the work both Christian and Andrei have begun, and are open to more collaborations. If you like what you see, please join in and let us know how you can contribute. Also, please share any work that has been done that was not mentioned in this blog post.
Onto the next five years!