CUNY Academic Commons

Christian Wach

Tadpole Collective

Kevin Cristiano

<h3>WordPress Integration</h3>
<p>At its simplest, the CiviCRM Profile Sync plugin keeps the “First Name”, “Last Name”, “Nickname”, “Email Address” and “Website” fields of a WordPress User Profile in sync with their corresponding fields in a CiviCRM Contact. The synchronisation takes place regardless of whether the changes are made in WordPress or CiviCRM.</p>
<h3>BuddyPress Integration</h3>
<p>The plugin also supports syncing the “First Name” and “Last Name” fields of the WordPress User and CiviCRM Contact with BuddyPress when using the BP xProfile WordPress User Sync plugin. Further integration with BuddyPress is in the pipeline.</p>
<h3>ACF Integration</h3>
<p>CiviCRM Profile Sync enables integration between CiviCRM Entities and WordPress Entities with data synced via Advanced Custom Fields.</p>
<p>Whilst ACF integration is not complete in its coverage of the CiviCRM Entities that can be linked, it is fairly comprehensive in its mapping of the built-in CiviCRM Custom Field Types with their corresponding ACF Field Types.</p>
<p>So if, for example, you want to display (or create) a Contact Type on your WordPress site with ACF Fields that contain synced CiviCRM data, this feature could work for you.</p>
<p>Please refer to the <a href="https://github.com/christianwach/civicrm-wp-profile-sync/blob/master/docs/ACF.md" rel="nofollow ugc">ACF Integration Documentation</a> for details.</p>
<h3>Form-building with ACF Extended</h3>
<p>CiviCRM Profile Sync enables Forms to be built for the front-end of your website with the UI provided by the ACF Extended plugin. These Forms can send their data directly to CiviCRM in a similar (though more limited) way to Caldera Forms CiviCRM.</p>
<p>Form building with ACF Extended is currently limited to submitting data for Contacts, Participants, Activities and Cases. This does, however, provide enough functionality to build some fairly powerful and useful Forms.</p>
<p>Please refer to the <a href="https://github.com/christianwach/civicrm-wp-profile-sync/blob/master/docs/ACFE.md" rel="nofollow ugc">ACFE Form-building Documentation</a> for details.</p>
<h3>Requirements</h3>
<p>This plugin recommends a minimum of <em>WordPress 4.9</em> and <em>CiviCRM 5.23</em>. It also requires <em>BuddyPress 3.0</em> and the <a href="https://wordpress.org/plugins/bp-xprofile-wp-user-sync/" rel="ugc">BP XProfile WordPress User Sync</a> plugin for syncing “First Name” and “Last Name” with BuddyPress profiles.</p>
<h3>Plugin Development</h3>
<p>This plugin is in active development. For feature requests and bug reports (or if you’re a plugin author and want to contribute) please visit the plugin’s <a href="https://github.com/christianwach/civicrm-wp-profile-sync" rel="nofollow ugc">GitHub repository</a>.</p>


CiviCRM Profile Sync

Keeps a WordPress User profile in sync with a CiviCRM Contact and integrates WordPress and CiviCRM Entities when using Advanced Custom Fields.

Bastien Ho

aureliefoucher

<p>CiviCRM uses shortcode in order to insert dynamic content into WordPress pages, such as Petition, Survey, Contribution form, Membership…</p>
<p>As mentioned into the <a href="https://docs.civicrm.org/sysadmin/en/latest/integration/wordpress/" rel="nofollow ugc">CiviCRM documentation</a>:<br />
“Currently there is no specific CiviCRM block for Gutenberg so there is no interactive way to see the options available for the shortcode.<br />
You will need to know the format and look up IDs and options in CiviCRM before creating the shortcode in WordPress.”</p>
<p>Knowing an object ID is not very convenient. So we’ve made a plugin which uses the CiviCRM API to get and display all attributes for the shortcode, directly in a simple block.</p>
<p>This way, embedding CiviCRM content into any WordPress page becomes a child’s play!</p>
<h3>1.4.5</h3>
<ul>
<li>Catch civicrm’s crashes in block preview</li>
<li>Prevent links and buttons from being clickable in preview</li>
</ul>
<h3>1.4.4</h3>
<ul>
<li>Fix dependency for php8.4</li>
<li>Move block API version to 3</li>
<li>Update dependencies to latest version
<ul>
<li>wordpress/block-editor: v15.2.0</li>
<li>wordpress/blocks: v15.2.0</li>
<li>wordpress/components: v30.2.0</li>
<li>wordpress/element: v6.29.0</li>
<li>wordpress/hooks: v4.29.0</li>
<li>wordpress/i18n: v6.2.0</li>
<li>wordpress/scripts: v30.22.0</li>
<li>wordpress/server-side-render: v6.5.0</li>
</ul>
</li>
</ul>
<h3>1.4.3</h3>
<ul>
<li>Update contact of error reports</li>
<li>Set php8.4 as max supported version</li>
<li>Optimize deployment</li>
</ul>
<h3>1.4.2</h3>
<ul>
<li>Fix warning for too early i18n</li>
</ul>
<h3>1.4.1</h3>
<ul>
<li>Fix version propagation</li>
</ul>
<h3>1.4.0</h3>
<ul>
<li>Add preview in editor</li>
<li>Test if CiviCRM is activated before loading its options</li>
<li>Load after <code>plugins_loaded</code> hook</li>
<li>Uses composer autoload</li>
<li>Uses wp_add_inline_script to pass options to the block</li>
<li>Update all dependencies to latest version
<ul>
<li>wordpress/block-editor v12.14.0</li>
<li>wordpress/blocks v12.23.0</li>
<li>wordpress/components v25.12.0</li>
<li>wordpress/element v5.23.0</li>
<li>wordpress/hooks v3.46.0</li>
<li>wordpress/i18n v4.46.0</li>
<li>wordpress/server-side-render v4.23.0</li>
<li>wp-reporting v1.6</li>
</ul>
</li>
</ul>
<h3>1.3.4</h3>
<ul>
<li>Update wp-reporting to v1.5.1, fix WP Notices about scripts</li>
</ul>
<h3>1.3.3</h3>
<ul>
<li>Update wp-reporting to v1.5</li>
</ul>
<h3>1.3.2</h3>
<ul>
<li>Fix “Undefined array key className” warning. </li>
<li>Update wp-reporting to v1.4</li>
</ul>
<h3>1.3.1</h3>
<ul>
<li>Let CiviCRM call its generated shortcode</li>
<li>Update wp-reporting to v1.3</li>
</ul>
<h3>1.3.0</h3>
<ul>
<li>Cleanup shortcode attributes (only keep those CiviCRM understands)</li>
<li>Set default value for mode & hijack</li>
<li>Update NPM dependencies</li>
</ul>
<h3>1.2.0</h3>
<ul>
<li>Removes limit of options</li>
<li>Uses CiviCRM API4 when possible</li>
<li>Remove some PHP8+ deprecated warnings</li>
</ul>
<h3>1.1.2</h3>
<ul>
<li>Fix Parse error on PHP7.4</li>
</ul>
<h3>1.1.1</h3>
<ul>
<li>Fix Parse error on PHP7.4</li>
</ul>
<h3>1.1.0</h3>
<ul>
<li>Refactor: use latest version of blocks library</li>
<li>Wrap output into a div. Allows editor to add CSS classes</li>
<li>Add error log report option</li>
</ul>
<h3>1.0.0</h3>
<ul>
<li>Initial release</li>
</ul>
<h3>Upgrade notice</h3>
<p>No particular informations</p>


Blocks for CiviCRM

Gutenberg block in place of CiviCRM shortcode

CiviCRM Profile Sync vs Blocks for CiviCRM