gamaup

Hi,

Thanks for your feedback. I actually replied to your email about this a few days ago with some follow-up questions to better understand your setup.

If you have a moment, please check your inbox and reply there so we can continue troubleshooting and see what might be happening in your case.

I’ll be happy to take a closer look once I have a bit more information about your configuration.

Hi,

Thank you very much for reporting this and for the detailed explanation, including the repro steps. I really appreciate it.

You’re absolutely right about nl2br() not being ideal for WYSIWYG fields, especially when the content already contains proper block-level HTML. It makes sense to let WordPress or ACF handle the formatting instead of manually injecting line breaks.

I will update this in the next release to ensure WYSIWYG fields are processed using the proper content filters rather than nl2br().

Thanks again for taking the time to point this out.

Hi,

Thank you for the detailed explanation and for sharing the sample code from your developer.

That makes sense. I can see how checking for ACF too early in the constructor would cause issues when ACF is bundled and loaded during theme setup. Hooking the check into after_setup_theme is a solid approach.

I will implement this improvement in the next update so the ACF presence check runs at the proper time and works correctly with bundled setups like yours.

Thanks again for reporting this and for providing a working example. It really helps 👍

Hi René,

Thanks for the update, and sorry for the delay in releasing the oEmbed support.

Glad to hear you were able to fix it using the render_block hook.

Just to let you know, oEmbed support has now been released in the latest update. Feel free to update the plugin and give it a try.

Let me know if everything works well on your end.

Hi,

Thanks for the detailed explanation. That helps a lot.

In this case, Blocks for ACF Fields is not able to handle this setup. The plugin can only display ACF field values from the current WordPress context (the post, page, or template being rendered). It does not support switching the field source dynamically based on a URL parameter such as ?id=123.

However, there is an alternative approach that works well and is fully supported.

You can add an ACF Post Object field to your Event post type and use it to select the detailed post. This creates an explicit relationship between the event and its detailed page.

Then, on the event detail layout, you can:

1. Insert the ACF Field block
2. Select the Post Object field and set the display type to List (this will create a post loop)
3. Inside the loop, insert another block to load the post content

This setup will display the selected detailed post directly inside the Event layout, allowing each event to control which detailed content is shown. Please note that displaying Post Object fields as a List is available in the PRO version of this plugin.

I hope this helps, and let me know if you have any questions about setting this up.

Hi Oliver,

I’ve just released an update that includes the fix for this issue (v1.2.8). You should now be able to load the custom fields from your linked “location” post inside the loop as intended.

Since you’re a Pro user, feel free to reach out to me directly anytime at [email protected] if you run into anything else or need help with your setup.

Thank you for your patience!

Best regards,
Gama

Hi Oliver,

Yes. This is absolutely possible, but it requires the Pro version of Blocks for ACF Fields.

In your setup, both location and organizer are ACF Post Object fields attached to the event. With the Pro version, you can load Post Object fields as a loop, even if the field only contains a single item. Inside that loop, you can then display any custom field that belongs to the linked post type. In your case, the address fields from “location” or the phone/website fields from “organizer.”

I also have a short demo video that shows the exact concept (the example uses the same post type, but the method is identical for your case):
https://youtu.be/L53j_6ApCh4

Best,
Gama