ACF (Advanced Custom Fields)
In order to make my crossposting plugins fully compatible with Advanced Custom Fields (ACF), you just need to install and activate the add-on below. No extra configuration is required.
In case you’re using a multisite version of the plugin:
Download Simple Multisite Crossposting – ACF 2.1
For a regular version of the plugin:
Download Simple WP Crossposting – ACF 3.9
Please use the correct version of the add-on depending on which plugin you have! 🤬
Please also check that your custom fields have the same names on both sites. For example, “news_description” and “news_Description” aren’t the same!
If you’re using a non-multisite (regular) version, don’t forget to allow ACF fields for REST API in Field Groups > Edit > Group Settings. Otherwise, the fields aren’t going to be copied.
Crossposting Relational-type fields
When you’re about to crosspost field types from the “Relational” group, you should know how it works exactly.
Please keep in mind the following:
- When you’re using “Post object”, “Page Link”, or “Relationship” fields, the posts from these fields should be crossposted to a target site beforehand. It works the same way for parent and child posts. In cases when the related posts were created on the target site manually, you need to connect them first so the plugin will see the connection.
- When you’re using “Taxonomy” or “User” field types, just make sure that your terms have the same slugs (or users have the same usernames).
Below is a step-by-step video on how to configure ACF field groups for a non-multisite (regular) version of the plugin:
ACF plugin issues
The REST API endpoints of Advanced Custom Fields have a small issue for the following field types: “Number”, “Email”, “Select” (and maybe some others) when used as nested fields. The field values will be updated without issues; however, if you try to empty those fields, they will be ignored on target sites (by ACF). In other words, if the target site already has a value for these fields, it will not be emptied.
In our case, it only affects the non-multisite (regular) version of my crossposting plugin.
What to do?
First of all, there are workarounds:
- Do not use “Select”, “Number”, and “Email” fields inside a “Group”, “Repeater”, or “Flexible Content”.
- Use a “Text” field instead of “Number” or “Email” fields.
Second, you can leave a reply on the ACF support forum in this thread to get their attention (as you can see, this bug is not new).
Third, contact ACF for help. Once you get a reply from them, then and only then, you can get back to me.