I am trying to:get view working on my live site. The city will not populate. That is the only thing I cant get to work.
Link to a page where the issue can be seen:
I expected to see:hidden link
Instead, I got:hidden link
hidden link THIS IS THE TEST SITE WHERE IT WORKS.
hidden link . MOVED WORK HERE LIVE SITE NOT WORKING
toolset = username
password = !8f^RYq*V^cfOofU2$8QGRol
Template Views Below
hidden link
hidden link
I imported the exact same work over and it doesnt work. Can you please look into this and see what is wrong. I can't find out why it will not work on the live site.
Thank you,
Jim
I have debug on so you may be able to view the issues that are there.
Hi Jim,
Thank you for contacting us and I'll be happy to assist.
The first thing I noticed is that the views in question on both websites are the taxonomy views and not the post views. The front-end search filters are officially supported only for the post views and not for the taxonomy ones.
( screenshot: hidden link )
It seems the content for the search filters was manually inserted in the "Search and Pagination" section and though some of these filters work, it can change or break with future updates, until this gets officially supported.
My first recommendation would be to use post views ( instead of taxonomy views ), in case the front-end filters are required.
As for your original question about why "wpv-control-postmeta" shortcode ( [wpv-control-postmeta field="city" type="select" url_param="address_city" default_label="All Cities"] ) is bringing in the city list on the development website, but not on the live one, it suggests that on the live website, there are no custom field values attached to the "Properties" post type with the slug "city" or "wpcf-city".
If there were custom fields attached with any of these slugs, they would've shown, based on the tests on my own website.
Note: As mentioned in the documentation, "wpv-control-postmeta" shortcode gets the values from the post custom fields (and not the taxonomy's custom fields):
https://toolset.com/documentation/user-guides/views-shortcodes/#vf-520693
Based on that, I'll recommend troubleshooting, if all the custom fields were moved successfully, during the migration/import.
I hope this helps and please let me know if you need any further assistance around this.
regards,
Waqar
Thanks for the reply. I just checked the database. It does show it in this field. I am really just using this as a ability to put the search string into the url. It should work fine with no issues. For some reason it doesnt show up though. I have also manually input it . It works but when I hit the next pagination it pulls in all the other cities. Is this a bug?
Hi Jim,
Thanks for writing back.
I've checked the page on the live website ( hidden link ) and noticed that the view is now changed to a post view and the city field is also using taxonomy "property_city" instead of a custom field.
Looks like you've managed to make this work after writing to us. But, please let me know if you still need any assistance around this.
regards,
Waqar
