[Gelöst] Can't take control of 3rd party custom fields
This support ticket is created vor 8 Jahre, 3 Monate. 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.
As in one of the above topics described I managed to enable the hidden custom fields in Views/Settings/Hidden Custom fields. This helps me a lot as I can now use these fields in Views queries and sorting.
But unfortunately I still can't see the custom fields in Types -> Custom Fields Control.
I know that this is a bit frustrating for you but there isn't much we can do 🙁 If the custom fields of a plugin are hidden then they won't be available to our Types plugin to take control.
Our views plugin is able to display the information of these hidden fields via the use of the hidden field settings but our Types plugin does not have such a setting.
We can only take control of fields that are declared as public and not hidden.
well, yes a bit frustrating. But maybe you could still help me out.
We need to change the Date format of this custom field: [wpv-post-field name="_EventStartDate"].
The format is "YYYY-MM-DD HH:MM:SS". We need it in the WordPress Date format like this "l, d. m. Y".
Is there a way to rewrite the format? Some custom function and/or custom shortcode?
Unfortunately i'm not able to assist with this as our shortcode doesn't provide a parameter for retrieving the field in a specific format. Our shortcode gets the value as it is in the database.
What I recommend that you do is to contact the Events calendar support team for them to assist with this. They should be better able to advise you on getting this done that us here.
Thanks,
Shane
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.