ACF Recent Posts Widget

ACF supported fields

The plugin has been tested with ACF 6 (Free and Pro).

The plugin supports the following ACF fields:

• Text
• Textarea
• Number
• Email
• Password
• Wysiwg Editor
• Image
• File

No other fields have been tested and are supported at the moment.

Shortcode

From version 4.4 the plugin supports shortcode embeds. Given the amount of options and their specific names (as in shortcode attributes) the shorcode builder has been introduced see 7th and 8th screenshots for the reference.

You’ll see a popup once clicked on ACFRPW button which gives one an ability to automatically set up the shortcode code for you. The rest follows all of the options specified here.

To use the shortcode one needs to have the WordPress editor enabled for the current page / post type. In case it was disabled (say via ACF) the button won’t appear.

Creating Custom Templates

From version 4.3 the plugin supports custom templates. To make usage of these one needs to make a copy of all the files found in the acf-recent-posts-widget/templates directory and copy them over to the active template directory to acfrpw subdirectory. The approach is similar to the way WooCommerce plugin works and has it’s drawbacks. With every new feature the files may be outdated.

Similarly to the widget template files, a separate, custom markup can be created for the shortcode build post listing. Copy the acf-recent-posts-widget/template files to acfrpw-blog directory created inside your active theme directory.

Template files

There are 3 main template files:

• loop-after.php (which displays the markup after each of the posts and closes the markup container)
• loop-before.php (which displays the markup before each of the posts and opens the markup container)
• loop-inner.php (which is enqueued for each of the posts separatelly and contains the markup of every single post)

Usage

The usage is quite advanced hence each template file contains a quite detailed documentation on how to use it.

First of all the template files mustn’t have the global variables removed. Each of these variables stores the widget settings, which are then used to generate the code. Second of all the variable names are unobvious, loop-inner.php template file contains a list of all the names used, which are then extracted and available as php variables.

Different template per widget / sidebar

The templates allow one to adjust the markup of each single widget. One needs first to verify the widget id used, which may then be referenced. The variable which stores the widget id is $acf_rpw_args[‘widget_id’]. Dumping the value in the template is the best way to find out which automatic id has been created for your widget.

The best way to handle the templates is to learn from their code. My personal suggestion is to copy over the templates to the current theme and work directly on them, doing one change at a time. The templates require learning curve to use and there’s no single answer to everyones problem.

Complex usage

This section covers plugin complex usage for advanced user willing to have more control over the behavior of the plugin as well as explains uncommon functionalities.

Using the HTML textarea fields

These sections might not be obvious. The HTML or text before / after the whole loop setting is an area where you can specify custom HTML markup to be added before / after the whole posts list. The HTML or text before / after each post is an area where you can not only specify custom HTML, but you are also given an ability to print any meta key or certain ACF fields (see ACF supported fields )

Meta Key Name / ACF Usage

These fields need to be wrapped inside the {meta name} or {acf field_name} tags (which are similar to shortcodes). The plugin will then parse these fields and print their according value. Say we have a custom ACF field of type text, for which the Field Name is “text”. To print its value one has to use [acf text] inside the befoe / after each post textarea. A similar solution applies to the meta key.

Meta Value Usage

The Meta Value field supports an array of elements, so that all of the meta_compare parameters could be used. To do so, please specify the two parameters separated by semicolon, for instance: 1234;12345. The plugin will convert these into an array and apply the proper operation for the two. Whatsmore the [date] shortcode can be used here. It takes the timestamp paramater as an argument, which is required – the possible arguments are the same as for the function described here: http://php.net/manual/pl/function.strtotime.php. For instance [date +1 day] would generate the tomorrow date in “Ymd” format. This can be used with custom meta field date.

Plugin Filters

The are several filters that can be used to enchance the plugin programatically:

• ‘acf_rwp_query’ which gives one the ability to filter the query applied to each widget.
• ‘acp_rwp_before’ which gives on the ability to filter the Front End output of the plugin before each post. There are two hooks attached here already which allow usage of the [acf] and [meta] shortcodes.
• ‘acp_rwp_after’ which gives on the ability to filter the Front End output of the plugin after each post. There are two hooks attached here already which allow usage of the [acf] and [meta] shortcodes.
• ‘acf_meta_value’ which filters the meta_value query parameter.

Check the acf_widget_widget file for the arguments and use cases.

Dependencies

• ACF (optional)
• Widget Base Class (included)
• Shortcode popups generator (included)

Other

• Online Demo
• Plugin site and Docs
• Plugin Development Survey

Languages Supported

• English (default)
• Polish (since May 11 2015)
• French (since June 29 2015), by wolforg , standalone source
• Spanish (since July 30 2023)