Andie Hunt

You can use the CiviEvent widget to add two types of widgets for upcoming public events from CiviCRM. There’s no limit to the number of widgets you can add of either type. You can include the widgets in the sidebar like normal, or you can include them via shortcodes in the body of your posts.
<h4>CiviEvent List Widget</h4>
This widget is a basic, flexible listing of upcoming events that are marked as public. You have options to customize the appearance and number of events. There is the option to add the event’s city, state, and/or country to the listing if “Show location” is enabled on the event.
<h4>Single CiviEvent Widget</h4>
This widget displays a single public event from CiviCRM. By default, it will display the first event from the current day or the future, or you can set an offset to skip one or more and display the second or third upcoming event. You may display the location if “Show location” is enabled on the event.
<h4>Shortcodes</h4>
Both widgets are available to be inserted into the body of a post using a shortcode. Use the <code>[civievent_widget]</code> shortcode for the events listing and the <code>[civievent_single_widget]</code> shortcode for the single next (or offset) event. The available parameters for the shortcodes are as follows:
<ul>
<li><code>title="Your Title"</code> The widget title (default: “Upcoming Events” for the list widget, or the event’s title for the single widget).</li>
<li><code>summary=1</code> Display the event summary. Omit the parameter or set it to 0 to hide the summary. (List widget only.)</li>
<li><code>limit=5</code> Display the specified number of events (default: 5). (List widget only.)</li>
<li><code>alllink=1</code> Display “view all” with a link to the page with a full list of public events. Omit the parameter or set it to 0 to hide the link. (List widget only.)</li>
<li><code>wtheme="mytheme"</code> The widget theme (a class added to the widget div). Set a new one and handle it in your theme’s CSS. (Default for list widget: “stripe”, with “divider” as an alternative. Default for single widget: “standard”.)</li>
<li><code>divider=" | "</code> The location field delimiter (default: comma followed by a space).</li>
<li><code>city=1</code> Display the event’s city. Omit the parameter or set it to 0 to hide the city.</li>
<li><code>state="abbreviate"</code> Display the event’s state/province. Default is “none”, which will display nothing about the state or province. Display options are “abbreviate” for the state/province abbreviation or “full” for the full name.</li>
<li><code>country=1</code> Display the event’s country. Omit the parameter or set it to 0 to hide the country.</li>
<li><code>offset=2</code> Skip the given number of events before displaying the next one (default: 0). (Single widget only.)</li>
<li><code>admin_type="simple"</code> Whether to use the “simple” (default) or “custom” display options (as appear in the widget settings). The <code>custom_display</code> and <code>custom_filter</code> parameters only function alongside <code>admin_type="custom"</code>. The <code>summary</code>, <code>alllink</code>, <code>divider</code>, <code>city</code>, <code>state</code>, and <code>country</code> parameters only function when <code>admin_type="simple"</code> (or reverting to the default). (List widget only.)</li>
<li><code>custom_display='{"event_title_infolink":{"title":0,"prefix":null,"suffix":null,"wrapper":1},"description":{"title":1,"prefix":null,"suffix":null,"wrapper":1}}'</code> Custom options for displaying results when <code>admin_type="custom"</code>. The value should be an object written in JSON. Each property name should be a field to display, and the property value should be an object with the following properties: <code>title</code> (1 or 0: whether to display the field name), <code>prefix</code> (<code>null</code> or a string with markup to precede the field), <code>suffix</code> (<code>null</code> or a string with markup to follow the field), and <code>wrapper</code> (1 or 0: whether to wrap the field with the default wrapper elements. You may configure a widget using the standard widget interface, click “Show JSON”, and copy the JSON into this parameter. If <code>custom_display</code> is missing, the listing will revert to displaying in the “simple” mode despite the <code>admin_type</code> value. (List widget only.)</li>
<li><code>custom_filter='{"start_date": {">=": "2015-12-16"}, "is_public": 1, "options": {"sort": "start_date ASC"}}'</code> Custom options for filtering results when <code>admin_type="custom"</code>. The value should be an object written in JSON. The object should be a valid set of parameters for the CiviCRM API. The default is to list all public events starting on today’s date or later, sorted by start date ascending. (List widget only.)</li>
<li><code>event_type_id=3</code> Display Event with event type id 3 (default: show all event). (only work with admin_type=”simple”.)</li>
</ul>
<h4>Further Notes</h4>
This plugin requires CiviCRM 4.3 or higher to function. It is only supported with CiviCRM 4.6 or higher.
Read more at https://aghstrategies.com/civievent-widget

CiviEvent Widget

Display widgets for CiviCRM events: the next public event or a whole list. Embed widgets as shortcodes, too!

Jaap Jansma

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>. 
CiviCRM does not necessarily be installed in the same installation. 
If it isn’t use the [CiviCRM McRestFace Connector plugin(https://github.com/CiviMRF/wpcmrf) to connect to a remote CiviCRM.
Configuration when CiviCRM is on a remote server
Use this when the front-end WordPress site and CiviCRM are on different servers:
<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>
Configuration when CiviCRM is installed locally
Use this when the frontend WordPress site and CiviCRM are in the same wordpress installation:
<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>
NB – If you have not created any Form Processors, no CiviCRM Caldera Processors will be listed!
Funded by
<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.

CiviEvent Widget vs Integration of CiviCRM's Form Processor with Caldera Forms