Skip Navigation

[Resolved] Query Filter on Views is no longer filtering properly

This support ticket is created 4 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 22 replies, has 2 voices.

Last updated by webadmins 4 years, 8 months ago.

Assisted by: Nigel.

Author
Posts
#1611175

Thanks Nigel, is this an existing entry in the htaccess file or do I need to create it?

#1611367

I added "php_value max_input_vars 4000" to our htaccess file but it did not seem to resolve the issue. Could be caching but I'm not sure.

#1611867

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Could you try re-saving the custom field group now that you have raised max_input_vars and then check again?

(Also, double-check that the field group appears to have saved correctly and not truncated the list of custom fields included.)

#1612765

I've tried both but the issue still seems to persist. I'll try raising the input to 5000.

#1613653

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

OK, let me know, and if that fails I'll look into it again.

#1614085

Hey Nigel, it didn't appear to work.

Additionally, most of the custom fields for our E-D component type are missing now and can't be added back.
I can see them all when I tried to add a new field and it gives you the option to add previously created fields but when I save, they changes don't take.

#1614177

Update:

I exported our Types Setup from our Production Site and imported them into our Staging environment and that appeared to solve the issue!

#1614201

My issue is resolved now. Thank you!

I imported the fields from Production into Staging and it resolved the issue.