Views is a WordPress plugin that lets you easily design the display of single pages using content templates. You can also include any field belonging to the content in your templates, without writing PHP code.
When you ask for help or report issues, make sure to tell us what you have created so far and what you want to achieve.
Viewing 15 topics - 1,906 through 1,920 (of 2,092 total)
Problem:
Use Non-Types custom fields of YITH Tickets plugin for Search filters
Solution:
To use the non Types field (third-party custom fields) with views you should enable those fields from:
=> Toolset => Settings => Front-end Content => Hidden custom fields
Problem: I am trying to use wpv-conditional to test for an empty value in an email custom field. If I include another shortcode inside the wpv-conditional, it does not work as expected.
Solution: Add the following line to your wp-config.php file to disable the PCRE regex engine:
The issue here is that the user has a view that lists their items with their images, however when the user changed the image. The new image isn't being reflected on the view.
Solution:
In this user's case they were changing the wrong image. The view was loading the image from a custom field, however they were changing the featured image which is what was causing the issue.
Problem: I am unable to add nested repeatable field groups in the custom field group editor. When I try to save, the nested RFG and fields are not saved as expected.
Solution: Increase available memory and max_input_vars.
I'm trying to hide a row which contains a conditional statement/data. I tried to switch back to general editor for adding the conditional statement so the row isn't visible anymore, that works. But after switching back to WP Bakery for further editing, WP Bakery adds extra rows for the conditional statement and also one for the closing tag.
Solution:
You can create a Views content template, put the [wpv-conditional] shortcode into this content template, then display the content template shortcode where you want using [wpv-post-body] shortcode, for example:
I've been requested to add an additional taxonomy for English and Spanish languages.
My question is whether it is best to use a new Custom Field or a new Taxonomy to distinguish the languages?
Also, how can I set up a separate language views?
Is there a tutorial of some sort?
Solution:
It depends on your website request, if your website will add more languages in the future, I suggest you try with custom taxonomy "languages", so you will be able to add more terms when you create/edit a "Channels" post.
If there are only two "languages" items in your website in the future, then you can setup it as a custom field "languages", then all the options are controlled by website administrator.
If it is a taxonomy "languages", you can add a filter in your post view:
Value set by View shortcode attribute "languages"
Then display the view's shortcode like this:
[wpv-view name="MY-VIEW-NAME" languages="english"]
[wpv-view name="MY-VIEW-NAME" languages="Spanish"]
