Skip Navigation

[Resolved] Getting "The post reference field … could not have been displayed" warnings

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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 2 replies, has 2 voices.

Last updated by Luo Yang 1 year, 6 months ago.

Assisted by: Luo Yang.

Screen Shot 2022-10-19 at 12.35.43 PM.png
Screen Shot 2022-10-19 at 12.35.26 PM.png

We have a custom post type "People" and "Videos".

Both videos and posts can be associated with people (e.g. who made the video or wrote the blog post.)

For a while there, also had something called "Resource Pages" which could be related to people.

We abandoned that idea, and got rid of our resource pages custom type (and presumably the relationship.)

However now when we go in to edit some people who were previously associated with a resource page, we get these errors (see below.) I don't see any way to clear this out so we don't get these errors.

TLDR: We are being haunted by the relations of a ghost custom post type. Boo!



Please provide a database dump file of your website in below private message box, I need to test and debug it in my localhost, thanks



I can install the your website database dump file in my localhost(latest version of Toolset Types + Toolset Blocks plugins), and it works fine in my localhost, see my screenshot 2479467.jpg
So there might be other compatibility/cache issues in your website, please try these:
1) Make sure you are using the latest version of Toolset plugins, you can download them here:
2) Clear the cache of other cache plugins, and test again
3) deactivate all other plugins, and switch to WordPress default theme 2022, and test again

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.