Problem:
The customer reported that the single quote characters in the classic views editor are getting converted to their equivalent ASCII character.
Solution:
Guided that this only happens when the option "Disable the visual editor when writing" is checked on the user profile page.
( WP Admin -> Users -> Profile )
Problem:
The customer reported that there are two views on the page with the same taxonomy filter, but the search works only for one of them.
Solution:
Guided that to make the same search filtering work for the two different views on a page, you'll have to make sure that:
1. Both are using the exact same query filter settings and the query string parameters.
And
2. Both views are set to update the search results with the page refresh and not using AJAX.
Problem:
The customer was using a many-to-many relationship and wanted to show related posts, filtered by one of the custom fields from the intermediary post.
Solution:
Guided how to add a custom field query filter to the view's setting.
Problem:
The customer reported that when the option to link to the term archive page is enabled, the layout of the archive is affected.
Solution:
Guided that by the HTML standards, it is not valid to nest one link inside another link and most modern browsers try to fix this on their own by changing the markup/code accordingly.
For this reason, whenever the option "Make the entire container a link" is enabled in a container block, it is better to avoid any other links inside the containing blocks.
Problem:
The customer reported that the caret symbol formatting for the select field is not showing correctly.
Solution:
Guided that some styles from WooCommerce are interfering with the default styles of the select type input field and shared some custom CSS code.
Problem:
The customer reported that when the view's results are updated through AJAX, background images shown in the view's loop get missing.
Solution:
The view was using the 'acf' shortcode to get the background image URL from the ACF plugin's image type field.
But, when the AJAX operation was performed on the view, the value of that field was not becoming available, so suggested to replace it with the Toolset's 'wpv-post-field' shortcode.
