Tell us what you are trying to do?
Cannot delete custom fields filter under Query filter
It adds them back after reloading the view page and even after clicking the Yes button on "Can they also be removed from the query filtering?"
Is there any documentation that you are following?
While I can see the issue with the query filter deletion in your website's view "search troubleshoot", I couldn't reproduce this on my test website. Also, I tested the query filter deletion on a new test view "Test view from TS support" and it worked as expected.
This suggests there is something specific to only this particular view ( "search troubleshoot" ), is involved. Have you tried creating a new replacement view with the same settings and content?
In case the issue persists, even with the new view, I'll need your permission to download a clone/snapshot of this website, to investigate this on a different server.
Thank you for waiting as we were little light on the forum coverage due to the holidays.
I've tested your website's clone on a couple of different servers and noticed that issue with the view's settings and query filter not updating, appears only when the "LiteSpeed Cache" plugin is active.
I'll recommend turning off the "Cache WP-Admin" option in the plugin's Cache -> Object settings and then testing the views again, after clearing all caches.
In case the issue still persists only with the plugin active, you can consult its official support and documentation to learn how to exclude admin-side AJAX calls from getting cached.
Happy holidays and no worries 🙂
Thank you for looking into it!
I tried your recommendation on the site (hidden link) about turning off the "Cache WP-Admin" option in the plugin's Cache -> Object settings
but it didn't solve the issue, so I tried deactivating the LiteSpeed Cache plugin but unfortunately, it didn't solve the issue as well
I tried deleting the custom fields filter but they still come back after reloading the view page
Thank you for waiting as this investigation turned out to be more complicated than initially expected.
After doing some further testing and research on my test website and on your website's clone, I was able to figure out what is happening.
A classic/legacy view's settings for the query filter are saved in the form of serialized data in a custom field meta key '_wpv_settings', with that view's post.
The same serialized data also contains information like the content, custom CSS and JS scripts added in the view's "Search and Pagination" section and the "Loop Editor" section.
In a view like "search troubleshoot" where no content template is used and there is a lot of content, CSS, and JS code saved in the "Search and Pagination" and the "Loop Editor" sections, this whole serialized string becomes too long for a single custom field record and hence it's storage and editing is affected.
To avoid a situation like this, it is a good practice to use a separate content template in views where there are a lot of query filters, loop item content, CSS, and/or JS scripts involved. This way, the serialized data in a custom field meta key '_wpv_settings' for the view will remain limited and the content of the loop item, additional CSS and JS scripts will be saved in the separate custom field meta key records, with the content template and not the view itself.
(when using a content template for the view's loop item, be sure to include custom CSS and scripts in the tabs below the loop item content template editor and not the ones under the "Search and Pagination" and the "Loop Editor" sections )
I hope this helps and please let me know if you have any follow-up questions.