Support threads created in the last 30 days: 1
Favorite Forum Topics
This user has no favorite topics.
Forum Topics Created
|Media Fields & Uploads 1 2||2||17||9 months, 3 weeks ago|
|Capabilities||2||5||10 months ago|
|The Forum (again)||3||7||10 months, 1 week ago|
|Views Module – Legacy plugin or not???||2||7||11 months ago|
|Multiple CRED Forms on Same Page||2||4||11 months, 3 weeks ago|
|The Forum||4||16||12 months ago|
Custom Date Fields & CRED Expiry Field
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.
|2||5||12 months ago|
|CRED Forms & Accessibility (WCAG)||2||7||12 months ago|
|CRED Redirects 1 2 3||4||36||1 year, 1 month ago|
Related Posts Function
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:
$args = array( 'numberposts' => -1, 'post_type' => 'child-post-type-slug', 'orderby' => 'post_date', 'order' => 'DESC', 'meta_query' => array( 'relation' => 'AND', array( 'key' => 'wpcf-colour', 'value' => 'Red', 'compare' => '=' ), array( 'key' => 'wpcf-description', 'value' => 'Ball', 'compare' => '=' ) ), 'toolset_relationships' => array( 'role' => 'child', 'related_to' => $post_id, 'relationship' => 'relationship-slug' ), ); $child_query = new WP_Query( $args );
|2||3||1 year, 1 month ago|
|Maps & Convert Cache||2||3||1 year, 1 month ago|
Views & Clean Cache
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.
|2||3||1 year, 1 month ago|
|For Beda please (re-opening previous ticket)||2||3||1 year, 1 month ago|
How to specify Post status to get posts with toolset_get_related_post question
You should pass an array of post status values or a string with one or more statuses separated by commas.
$role_name_to_return = '';//parent or child $args = array();// see args array - Additional query arguments. $post_status = 'publish,draft';//you can only use those from https://developer.wordpress.org/reference/functions/get_post_statuses/ or passed to toolset_accepted_post_statuses_for_api $writer = toolset_get_related_post( $post_id, array( 'one-side', 'other-side' ), $role_name_to_return, $args, $post_status );
|3||6||1 year, 1 month ago|
Toolset Maps database table name can cause an issue related to a bug in mysqldump
Problem: Toolset Maps uses a custom database table called _toolset_maps_address_cache. That table has a column named point, which is a reserved word of mySQL 5.7
This alone is not an issue because MySQL is context-sensitive in this case and understands when we are referencing the column.
However, due to a bug in mysqldump, it can happen that invalid data is used even though the table format is pretty strict, and later it can lead to issues when exporting and importing database tables to other databases.
|2||14||1 year, 1 month ago|