sandyS
Support threads created in the last 30 days: 0
Favorite Forum Topics
This user has no favorite topics.
Forum Topics Created
Status | Topic | Supporter | Voices | Posts | Freshness |
---|---|---|---|---|---|
Block editor is not working
Started by: sandyS
in: Toolset Professional Support
Problem: The customer wanted to create a search form with drop-down options for filtering academic texts on their website, aiming to replicate a search functionality similar to that on the Jeb Dunnuck site. They faced difficulties implementing this using Toolset Views with the legacy editor. Solution: To achieve the desired search functionality, the customer was advised to add a select dropdown for post type filters within their view and use the following code for implementation: [wpml-string context="wpv-views"]Post Type:[/wpml-string] [wpv-control url_param="wpv-post-type" type="select" values=",page,post" display_values="All,Page,Post"] Next, they were instructed to add a custom function to their theme’s functions.php file to modify the query based on the selected post type: add_filter('wpv_filter_query', 'post_type_filter_func', 10, 3); function post_type_filter_func($query_args, $settings, $view_id) { if ($view_id == 9999 && isset($_GET['wpv-post-type'][0]) && !empty($_GET['wpv-post-type'][0])) { $query_args['post_type'] = $_GET['wpv-post-type'][0]; } return $query_args; } The customer was reminded to replace 9999 with the actual View ID. For displaying the search form and results on different pages, they were guided to insert the View on the results page using: [wpv-view name="my-search-view" view_display="layout"] And on the search form page with: [wpv-form-view name="my-search-view" target_id="123"] Here, 123 should be replaced with the ID of the results page. Relevant Documentation: |
3 | 6 | 2 months ago | ||
Split: issue with navigation when the user is not logged in
Started by: sandyS
in: Toolset Professional Support
Problem: The customer reported an issue where the navigation on a page wasn't functioning correctly when the user was not logged in. The problem was traced to a lock icon appearing on the 'rating' field when users were not logged in. This lock was initially thought to be added via Toolset settings, but it was later discovered to be caused by a third-party plugin called "Restrict Content" by StellarWP. Solution: After identifying that the lock icons were being added by the "Restrict Content" plugin, we suggested temporarily disabling the plugin to confirm that it was the cause of the issue. The customer confirmed that the issue disappeared when the plugin was disabled. Since the plugin caused the issue, we recommended contacting its support team for further assistance. As a workaround, we provided a custom CSS code snippet to hide the lock icons from the outside of the table, allowing the page to function correctly even with the plugin enabled: p:has(> .vc_icon_element-icon.fas.fa-lock):not(table p) { display: none; } |
2 | 10 | 2 months, 2 weeks ago | ||
it is taking 100 as smallest number and 99 as large number
Started by: sandyS
in: Toolset Professional Support
Problem: The customer experienced an issue where a numerical field was sorting incorrectly, treating numbers as strings. After fixing this, they reported a new issue: navigation problems when users are not logged in, but everything works fine when users are logged in. Solution: The initial sorting issue was resolved by changing the field type to a number. The new issue with navigation for logged-out users was split into a separate ticket to maintain a focus on one issue per ticket. |
3 | 5 | 2 months, 2 weeks ago | ||
Filter is not working properly. you need to click 3 times
Started by: sandyS
in: Toolset Professional Support
Problem: The customer reported an issue where a filter they created worked fine, but the sorting by "vintage" on the results page was not functioning properly. The issue was observed after clicking on the sorting option by "vintage." Solution: We identified that the issue was related to the "vintage_post" field, which was created and managed by ACF (Advanced Custom Fields). The sorting issue did not occur when using a Toolset custom field. As a workaround, we advised the customer to manage the "vintage_post" field with Toolset by following these steps: - Go to Toolset > Custom Fields and click on the "Post Field Control" button. <th>[wpv-heading name="post-field"]Vintage[/wpv-heading]</th> to <th>[wpv-heading name="types-field-vintage_post"]Vintage[/wpv-heading]</th> This workaround allowed the sorting to function correctly using the ACF field within the Toolset View. The customer confirmed that the solution worked perfectly on the staging site. |
2 | 6 | 3 months ago |