Problem:

Users created as “Subscriber” (per the WPML + Toolset Access guide for language-specific editors) could not upload images or access the Media Library. Even after granting rights in Access, WordPress still blocked uploads.

Solution:

Subscribers don’t have Media Library access by default because media items use the separate attachment post type and require the core capability upload_files.
Create a custom role (e.g., “Translator” or “German Subscriber”) that is based on Subscriber but includes upload_files, assign it to the translators, then keep language restrictions handled by the WPML/Access setup. This enables uploads in the Media Library and builders like Elementor.

Relevant Documentation:

https://wpml.org/documentation/translating-your-contents/how-to-use-access-plugin-to-create-editors-for-specific-language/

Problem:

The get_search_query() function was returning an empty string when used inside a Toolset View, causing the Relevanssi relevanssi_didyoumean() function to fail. The issue occurred because Toolset custom search does not use WordPress’s default ?s= parameter, so get_search_query() had no value to read.

Solution:

Instead of using get_search_query(), the Relevanssi function was modified to use the Toolset View’s search URL parameter. By passing the View’s actual search parameter value to relevanssi_didyoumean(), the “Did you mean” functionality worked correctly inside the View’s “No items found” section.

Relevant Documentation:

https://toolset.com/course-lesson/searching-texts-in-custom-fields-with-toolset-and-relevanssi/

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/