Problem:
The user was trying to implement a view filter that will compare values as numbers(>= <=, etc.) for a checkboxes field.
Solution:
It won't be possible to search using a comparison on a Checkboxes field. Because the field's values are stored as serialized arrays, and search within them is always performed using a "LIKE" operator. Check the possible operator for custom field search here https://developer.wordpress.org/reference/classes/wp_meta_query/
If you need to use "greater than" operator you will need to use a different field type.
I'll suggest using a select field instead of a checkboxes field. You may also use a number field or a single-line field.
The issue here was that the user was unable to get a site key to register their website. Solution:
This was a known issue and our Systems team has since resolved it.
The issue here was that the user's frontend page was not loading correctly and was throwing the error
Fatal error: Uncaught Error: Object of class WP_Term could not be converted to string in /home/travelingfaq/public_html/dev/wp-content/plugins/toolset-blocks/vendor/toolset/dynamic-sources/server/Integrations/ThirdParty.php:157 Stack trace: #0 /home/travelingfaq/public_html/dev/wp-content/plugins/toolset-blocks/vendor/toolset/dynamic-sources/server/Integrations/ThirdParty.php(157): str_replace('\r\n', '<br />', Object(WP_Term)) #1 /home/travelingfaq/public_html/dev/wp-includes/class-wp-hook.php(292): Toolset\DynamicSources\Integrations\ThirdParty->replace_in_shortcode_output(Object(WP_Term), '__current_post', 4615, 'post-taxonomies...', 'age-group', Array) #2 /home/travelingfaq/public_html/dev/wp-includes/plugin.php(212): WP_Hook->apply_filters(Object(WP_Term), Array) #3 /home/travelingfaq/public_html/dev/wp-content/plugins/toolset-blocks/vendor/toolset/dynamic-sources/server/DynamicSources.php(811): apply_filters('toolset/dynamic...', Object(WP_Term), '__current_post', 4615, 'post-taxonomies...', 'age-group', Array) #4 / in /home/travelingfaq/public_html/dev/wp-content/plugins/toolset-blocks/vendor/toolset/dynamic-sources/server/Integrations/ThirdParty.php on line 157
Solution:
Through testing I was able to find that the issue was being caused by using Taxonomies as a dynamic content option for the Ultimate addon for gutenburg info box block.
At the moment the issue has been escalated to our 2nd tier supporters and developers.
However the workaround to this can be seen at the link below.
