Problem: I would like to use a View in the Mega Menu feature, but when I place the View in a Mega Menu using the Beaver Builder plugin, the Beaver Builder plugin stops working. I'm using the legacy Views editor.
Solution: It seems to be a conflict between Toolset's Content Templates and the Beaver Builder plugin. As a workaround in the legacy Views editor, move the contents of the template editor area directly into the loop editor, replacing the wpv-post-body shortcode(s) with the actual content of the template as needed.
Problem: I am using Blocks to create a custom search View with front-end sorting controls. I have removed Post Date from the sorting control configurations, but it still appears on the front-end of the site. How can I remove the Post Date sorting option?
Solution: The best current workaround is to select the top-level View block using the Block Navigation menu at the top of the screen . Then in the block configurations panel, open the Ordering Settings section and select the post title or post author here as the default sorting setting instead of post date. That should remove the post date sorting option from the front-end sorting controls.
Problem: I am trying to create a custom post type with the slug "downloads" but I see a message that the word is already in use, or reserved. I have a custom Page with the slug downloads already.
Solution: You must rename the custom Page slug to something else before you can reuse the slug "downloads" for a custom post type. In this case, the site also uses WPML to translate posts. The downloads slug must be changed in all languages before it is possible to reuse the slug elsewhere.
Problem: I have a custom search View that contains several filters. I would like to display the filters in the left column of the page, and results in the right column of the page.
Solution: If you are designing this View in the Block Editor, you may find the following course lesson helpful.
There is a video with more details showing how you can move the filters and results into a two-column design, side-by-side.
Problem: I would like to use a Conditional Group in Forms to test whether or not a custom field value is empty, but the conditional does not seem to work correctly.
Solution: You can omit the quotation marks from the condtion to test an empty value.
