Skip Navigation

[Resolved] When creating a post relationship custom search filter in the blocks editor, I see an error "The ancestors attribute is missing"

This support ticket is created 4 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Author
Posts
#1548293
ancestors-missing.jpg

Custom post types which are in a relationship with other post types are not viewable in the search field (see attached image). The custom post types are also imported and I saved them without making any changes to trigger the system but nothing seems to work.

I see an error in the Block Editor "The ancestors attribute is missing".

#1548347

Hello, as discussed in the other ticket it seems there is a problem with post relationship custom search filters in Views created in the Block Editor. This issue has been escalated to our developers and they are working on a fix. I can keep you updated here in the ticket as I receive more information. Thanks for the report!

#1553517

Hello, our developers have published a patch for this issue. Please follow the instructions in the following erratum post to install the patch: https://toolset.com/errata/cannot-add-a-post-relationship-filter-to-a-view/

Once you have followed those instructions to install the patch, please test again and let me know if the problem is not completely resolved.

#1583437

Just a quick update to note that the fix for this issue has been added to the software and the patch is no longer needed.