Refer this ticket to Waqar, please.
We are trying to setup this query filter for multiple pages:
Field - Development index
The field Development index is a number that is greater than or equal to the following:
Constant: 70
However the query filter is only saved for one page, it gets deleted all the time for the other pages.
What is going wrong?
Hi,
Can you please share details about on which page the query filter is saving and on which pages, it doesn't?
The screen capture video of the steps to see the issue would be very helpful, in this case.
I've set your next reply as private.
regards,
Waqar
Waqar,
The query filter:
Field - Development index
The field Development index is a number that is greater than or equal to the following:
Constant: 70
is saving for:
- hidden link
is NOT saving for:
- hidden link
- hidden link
Steps to take:
Open the respective pages
Go to View > Content selection > Query filters
Try to save the above query filter
You will see that the filter does save first BUT if you re-open the respective pages the filter is no longer saved, instead it saves the filter:
Field - Development index
The field Development index is a number that is greater than or equal to the following:
URL parameter: wpv-wpcf-development-index (instead of: Constant 70)
Thank you for sharing these details.
On the first page ( Acquisitie opportuniteiten professionele kopers met en zonder verkoopintentie ), where the query filter is saving, there is no front-end search field for the "Development index" field. This is why the query filter for that field can be set statically in the view's query filter settings.
However, in the views used on the other two pages, where the static query filter is not saving, the front-end search field for the "Development index" field is added in the search form. As a result, no matter what static query filter you'll set in the view's settings for this field, it will revert back to be linked to the associated front-end field.
If you'd like to set a static query filter for this field in the view's setting, you'll need to remove the associated front-end search field from the view's search.
( screenshot: hidden link )
My issue is resolved now. Thank you!
