Problem: I have a custom search WP Archive for a taxonomy that uses custom search. I have set the search feature to display only those options that would produce results. If I select one option, the options update as expected, but when the page loads all options are displayed. I have included other Views on the page.
Solution: In this case, it seems that omitting the filters from other Views included on the page is responsible for producing the problem in the archive filters. The filters were omitted by removing the wpv-filter-meta-html shortcode in the Output Editor. Replace the filter shortcode in the Output Editor of the other Views to solve the problem:
Problem: I would like to know if it is better to include User data in User fields in the User profile, or to create a proxy post type as explained in the documentation for post relationships and custom search for Users?
Solution: There are pros and cons for each approach. If you plan to use custom search Views to search for Users based on filtering by these custom fields, or if you plan to use Repeatable Field Groups for some of these fields, or if you plan to use post relationships to connect multiple Users to the same post, a proxy post type is probably required as explained in the documentation link below.
Problem: When I disable AJAX for Form submissions, one of my site's Forms will submit, but no post is created. The User is redirected to the same page URL, but a URL parameter tt is added and a generic 404 error is displayed. No JavaScript or PHP errors are logged in this scenario. With AJAX active for this Form submission, the Form submits successfully without any errors and the post is created as expected.
Solution: In this case, the problem seems to be related to a generic field with the slug name. Forms that include a generic field with the slug name will not create or edit posts successfully and will redirect to a 404 error page. Our developers are aware of this problem and will resolve the issue in the upcoming Forms 2.6.10 release. Until that time, a workaround is required. You can either rename the field slug to something other than "name", or you can enable AJAX submissions for this Form.
