Problem:

When using the toolset_association_created hook to retrieve a relationship field value from the intermediary post, the custom field returned an empty value, even though the value was confirmed to exist in the database. The field was stored on the intermediary post, and get_post_meta() was being called inside the hook, but it returned blank.

Solution:

The issue was caused by timing. At the moment toolset_association_created fires, the intermediary post meta may not yet be fully saved and available for retrieval.

To resolve this, the meta retrieval was delayed until after Toolset completed saving the relationship. This was achieved by scheduling a secondary action using wp_schedule_single_event() and retrieving the field value in a later hook.

Confirmed the intermediary post exists and has the expected post type and status.

Verified the correct meta key (wpcf-donor-scholar-relationship-status) is stored on the intermediary post.

Ensured the field is indeed saved on the intermediary (relationship fields are not stored on parent/child posts).

Relevant Documentation:

https://toolset.com/documentation/customizing-sites-using-php/post-relationships-api/

Problema:

After updating Toolset Blocks to version 1.6.21, Toolset dynamic blocks (Featured Image, Post Title, Post Categories with dynamic source) stopped working or disappeared in the editor, especially inside View templates.
With the previous version (1.6.16), everything worked correctly.
The issue occurred in a setup using the Kadence theme and only appeared after updating Toolset Blocks.

Solución:

The issue was identified as a plugin/theme conflict involving Toolset Blocks 1.6.21. To work around and diagnose the problem, the following steps were taken:

Downgrade Toolset Blocks to a previous stable version (e.g. 1.6.16 or 1.6.20) downloaded from the Toolset account.

Isolate the conflict by:

Deactivating all plugins except Toolset.

Switching temporarily to a default WordPress theme (e.g. Twenty Twenty).

Test which Toolset Blocks version introduces the issue before updating on a production site.

Using these steps, the site remained functional by staying on a stable Toolset Blocks version while confirming the source of the conflict.