Support Forum
Hi Support,
I am adding custom fields and have assigned these to a Settings Page. However, when the number of custom fields exceed (say) 48-50, the configuration of Custom Fields -> Settings -< Locatoin is reset automtically.
With this issue, from the desired Location of Settings page - Settings About, the config goes back to default and I lose all the display on the frontend. I then have to manually update the config.
Is this a bug or am I missing anything?
Kind regards,
Hello,
You can try to follow this tutorial to increase the PHP setting max_input_vars
to fix the issue
https://metabox.io/wordpress-custom-fields-not-saving-increase-max-input-vars/
Let me know how it goes.
Thank you Peter,
I am not sure that link you shared about WordPress Custom Fields Not Saving? Increase max_input_vars! is relevant.
Actually, the fields save okay but the Location attribute is reset when the number of fields go above 50 or so. Location is reset to Posts - Post. Please refer to the screenshot here - https://imgur.com/a/gXa4rqD
To fix this, I have to manually re-select the appropriate CPT. But after adding one or more fields, the error recurs.
Do you think its an issue with the PHP max_input-vars ? Or am I missing something?
Kind regards,
Hello,
Is there any chance you follow the suggestion to increase the PHP setting and check the issue again?
The field group in the builder is a post type so it is affected by the PHP setting max_input_vars
. You can refer to this topic
https://support.metabox.io/topic/after-edit-custom-field-group-only-applies-to-posts/#post-43114
Thanks Peter.
In the interet of time for my client, to bypass this limitation, I simply created a separate (part II) set of custom fields. It works this way and so I can clearly see the reasoning / logic you offered.
PS: I will try increasing the PHP max_input_vars value next time.
Appreciate your support,
Unakriti, did you try increasing the max input vars and if so, did it fix the problem?
I'm in the same boat here, I have increased the max input vars but still not working for me.
@David, I haven't had a chance to try this again, yet. In the interest of time for my client, I simply split the total by creating a second and a third set of custom fields to keep the total below 50 (per set).
Hope it helps.