Event Espresso Plugin Post Types are not available in Types Custom Fields Groups

This support ticket is created 6 years, 10 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.

This topic is split from https://toolset.com/forums/topic/create-a-drop-down-list-for-a-search-page-according-to-date/

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	-	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00
-	-	-	-	-	-	-

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Tagged: Custom search, Views plugin, WordPress Archives

This topic contains 2 replies, has 2 voices.

Last updated by augustd 6 years, 10 months ago.

Assisted by: Beda.

Author

Posts

February 6, 2018 at 11:05 am #613277

augustd

I can not add a custom field ( from Toolset ) to a post that has been created outside the plugin...i am working with Events Espresso along side with toolset. I can set a parent-child relationship between the posts created by both plugins but when it comes to a custom field i am not seeing any of the event posts created by the second plugin...
Do you have any experience with this ?

February 6, 2018 at 11:15 am #613293

Beda

Post Types must be public to be available in WordPress and the Types controls.
If the programmer somehow manipulated the native schema of Post Types it might be that they are hidden, not public or else how excluded.

Could I get a copy of that Plugin, and the steps to replicate the issue?

I enabled a private reply so to make sure you can submit this safely.

Thank you.

February 6, 2018 at 12:27 pm #613357

augustd

Hi Beda, the issue has to be let aside as i have seen that the custom field according to a set date is filtering according to day, month, year. Since i want only month, and year i can not go this path. I will open a new ticket though for a new issue.