Problem: Even though the post expiration timestamp in the database is identical to a custom field timestamp in the database, they are displayed on the front-end as different times.
Solution: Custom fields are assumed to be entered as GMT, and will be displayed as GMT. Post expiration is assumed to be entered as local time, and will be displayed as local time. Unfortunately there is no simple workaround right now.
Problem: I am trying to use a meta_query with the post relationships API toolset_get_related_posts, but it doesn't seem to be filtering as expected.
Solution: Some complex meta_queries, like using "IN" or "AND" with more than one term, fail with the post relationships API. Instead, you should use a standard WP_Query and add the toolset_relationships clause:
Problem: It seems like the new caching system will require manual intervention to update the cache any time content changes.
Solution: An individual View's cache is invalidated any time a post that could appear in the View results is added or edited. Manual intervention is not required here.
We document known issues and their solutions in Toolset errata. Save time by checking there first and seeing if what you are facing is a known issue. This list is kept short. We do our best to resolve all known issues with every release of Toolset plugins.
Support Policy
Toolset staff will help you use the Toolset plugins correctly, provide any information you need, help troubleshoot problems and advice on best-practices.
Please make sure to issue only one topic per each support ticket.
