Andie Hunt

<p>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.</p>
<h4>CiviEvent List Widget</h4>
<p>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.</p>
<h4>Single CiviEvent Widget</h4>
<p>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.</p>
<h4>Shortcodes</h4>
<p>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:</p>
<ul>
<li><strong><code>title="Your Title"</code></strong> The widget title (default: “Upcoming Events” for the list widget, or the event’s title for the single widget).</li>
<li><strong><code>summary=1</code></strong> Display the event summary.  Omit the parameter or set it to 0 to hide the summary. <em>(List widget only.)</em></li>
<li><strong><code>limit=5</code></strong> Display the specified number of events (default: 5).  <em>(List widget only.)</em></li>
<li><strong><code>alllink=1</code></strong> 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.  <em>(List widget only.)</em></li>
<li><strong><code>wtheme="mytheme"</code></strong> 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><strong><code>divider=" | "</code></strong> The location field delimiter (default: comma followed by a space).</li>
<li><strong><code>city=1</code></strong> Display the event’s city.  Omit the parameter or set it to 0 to hide the city.</li>
<li><strong><code>state="abbreviate"</code></strong> 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><strong><code>country=1</code></strong> Display the event’s country.  Omit the parameter or set it to 0 to hide the country.</li>
<li><strong><code>offset=2</code></strong> Skip the given number of events before displaying the next one (default: 0).  <em>(Single widget only.)</em></li>
<li><strong><code>admin_type="simple"</code></strong> 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). <em>(List widget only.)</em></li>
<li><strong><code>custom_display='{"event_title_infolink":{"title":0,"prefix":null,"suffix":null,"wrapper":1},"description":{"title":1,"prefix":null,"suffix":null,"wrapper":1}}'</code></strong> 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.  <em>(List widget only.)</em></li>
<li><strong><code>custom_filter='{"start_date": {">=": "2015-12-16"}, "is_public": 1, "options": {"sort": "start_date ASC"}}'</code></strong> 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.  <em>(List widget only.)</em></li>
<li><strong><code>event_type_id=3</code></strong> Display Event with event type id 3 (default: show all event).  <em>(only work with admin_type=”simple”.)</em></li>
</ul>
<h4>Further Notes</h4>
<p>This plugin requires CiviCRM 4.3 or higher to function.  It is only supported with CiviCRM 4.6 or higher.</p>
<p>Read more at https://aghstrategies.com/civievent-widget</p>


CiviEvent Widget

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

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

CiviEvent Widget vs Blocks for CiviCRM