Jaap Jansma

<p>This plugin makes it possible to submit caldera forms to <a href="https://lab.civicrm.org/extensions/form-processor/" rel="nofollow ugc">CiviCRM’s Form Processor</a>.<br />
CiviCRM does not necessarily be installed in the same installation.<br />
If it isn’t use the [CiviCRM McRestFace Connector plugin(https://github.com/CiviMRF/wpcmrf) to connect to a remote CiviCRM.</p>
<p><strong>Configuration when CiviCRM is on a remote server</strong></p>
<p>Use this when the front-end WordPress site and CiviCRM are on different servers:</p>
<ol>
<li>On the front-end site, install and activate:
<ul>
<li><a href="https://wordpress.org/plugins/caldera-forms/" rel="ugc">Caldera Forms</a> – WP plugin</li>
<li><a href="https://github.com/civimrf/cf-civicrm-formprocessor" rel="nofollow ugc">Caldera Forms integration with CiviCRM Form Processor</a> – this WP plugin</li>
<li><a href="https://github.com/CiviMRF/wpcmrf" rel="nofollow ugc">CiviMcRestFace Connection Plugin</a> – WP plugin</li>
</ul>
</li>
<li>On the front-end site, configure a CMRF connection to connect the front-end to the back-end</li>
<li>On the back-end server, install and enable:
<ul>
<li><a href="https://lab.civicrm.org/extensions/form-processor/" rel="nofollow ugc">CiviCRM Form Processor</a> – CiviCRM extension</li>
</ul>
</li>
<li>On the back-end server, create a CiviCRM Form Processor</li>
<li>On the front-end server, create a Caldera Form</li>
<li>On the Procssors tab, click <code>Add Processor</code></li>
<li>For each Form Processor you created, you should see a processor named the same as the Form Processor prefixed by ‘CiviCRM Form Processor’ and suffixed by ‘at ‘</li>
</ol>
<p><strong>Configuration when CiviCRM is installed locally</strong></p>
<p>Use this when the frontend WordPress site and CiviCRM are in the same wordpress installation:</p>
<ol>
<li>Install and activate:
<ul>
<li><a href="https://wordpress.org/plugins/caldera-forms/" rel="ugc">Caldera Forms</a> – WP plugin</li>
<li><a href="https://lab.civicrm.org/extensions/form-processor/" rel="nofollow ugc">CiviCRM Form Processor</a> – CiviCRM extension</li>
<li><a href="https://github.com/civimrf/cf-civicrm-formprocessor" rel="nofollow ugc">Caldera Forms integration with CiviCRM Form Processor</a>  – this WP plugin</li>
</ul>
</li>
<li>Create a CiviCRM Form Processor</li>
<li>Create a Caldera Form</li>
<li>On the Processors tab, click <code>Add Processor</code></li>
<li>For each Form Processor you created, you should see a processor named the same as the Form Processor prefixed by ‘CiviCRM Form Processor’</li>
</ol>
<p>NB – If you have not created any Form Processors, no CiviCRM Caldera Processors will be listed!</p>
<p><strong>Funded by</strong></p>
<ul>
<li><a href="https://www.civicoop.org" rel="nofollow ugc">CiviCooP</a></li>
<li><a href="https://civiservice.de/" rel="nofollow ugc">Civiservice.de GmbH</a></li>
<li><a href="https://www.soziokultur.de/" rel="nofollow ugc">Bundesverband Soziokultur e.V.</a></li>
<li><a href="https://www.article19.org/" rel="nofollow ugc">Article 19</a></li>
</ul>


Integration of CiviCRM's Form Processor with Caldera Forms

This plugin integrates Caldera Forms with CiviCRM's form processor. Funded by CiviCooP, Civiservice.de, Bundesverband Soziokultur e.V., Article 19

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.5.0</h3>
<ul>
<li>New selector to allow to display any CiviCRM page</li>
<li>Security: escape notice output</li>
<li>Catch preview errors in editor</li>
</ul>
<h3>1.4.7</h3>
<ul>
<li>Update dependencies</li>
<li>Test up to WP 7.0</li>
</ul>
<h3>1.4.6</h3>
<ul>
<li>Test up to WP 6.9</li>
</ul>
<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

Integration of CiviCRM's Form Processor with Caldera Forms vs Blocks for CiviCRM