Doesn’t keep more than 9 custom fields saved.
Anonymous User 14808221
(@anonymized-14808221)
Can you elaborate the steps to reproduce this?
You can save and create as many Custom Fields Groups, and Custom Fields as you want with Types.
You can see here how to do that.
There’s two save buttons, using the one above the custom fields tends to save more than 7. However it still isn’t saving unlimited fields.
When I leave the page to check them on a post, they aren’t all there. When I go back to the fields page , they weren’t saved. I am even hitting save after each new field I create.
Why are there two save buttons?
Anonymous User 14808221
(@anonymized-14808221)
There are 2 Buttons to make it easier to find the save button.
You might edit a field on top of the list and want to save, or on bottom, and save.
Having 2 Buttons avoids you from scrolling all the way down or up.
I can reproduce your issue, have escalated it and the DEV will ensure a FIX ASAP-
Thank you very much for the detailed description of the problem and for your patience.
Anonymous User 14808221
(@anonymized-14808221)
I must ask, are you saving the Fields with numerical Slugs?
Because if I save any number of fields (I Tried 20 a time) this issue does not happen
This might be due (if you do save proper strings and not numbers) to your Server Settings.
I have solved this in past with the max_input vars
Also, sometimes it needs 256 PHP MEM and 1GB min. server MEM
(large site, many Custom Fields, lots of meta, == needs more server mem and PHP mem)
This could help here
I initially mistakenly created 8 fields with numerical Slugs, and that’s why I thought I can reproduce this issue.
But I can not. I just created another 40 fields with text slugs all saved at one time, and that worked fine with both buttons.
Can you confirm my approach?
Thank you
Slugs seem to auto fill based on the label. I tested entering a number for the slug , was not before, still not saving.
How would I fix mas_input vars? Is this specific to custom fields?
Tested upgrading php and memory limit, not helping. Half of my 18 fields are wsywg if that’s contributing. I also remember checking out the custom fields control link before, maybe i changed something?
I’ve got one more to add with the top button, another after , then deleted and could not add it back. I want to think wsywyg back to back has less chance of saving. Tested with different types.
It’s also sometimes telling me the field name already exists.
Updating didn’t work.
It’s saving consecutively so far when I deleted a custom field from the controls which it said was duplicated (the odd thing is some that I previously created weren’t saved to controls , but still wasn’t saving).
The notice was all the way at the top , I was using both save buttons whilst scrolled to the bottom of the page. Tested creating a duplicate and I think it only shows the yellow warning in the field box if that field is still on the page ( didn’t notice it before), so it probably doesn’t when it’s referring to “already saved” in controls only.
Anonymous User 14808221
(@anonymized-14808221)
1. I tested entering a number for the slug , was not before, still not saving.
Field Slugs can not be numerical as I explained.
2. It’s also sometimes telling me the field name already exists.
This is expected, you can not create the same field (with same slug) over and over.
I know that this was possible in older versions and we are looking into this, so to either add a explanation why it’s not anymore possible, or to bring back the feature.
3. You can contact your Server Admin to increase the max_input vars and PHP MEM and server MEM
I understand you can now safely and successfully save Custom Fields?
Thank you
It seemed to be fine once I deleted previously used terms from the controls table ( because they weren’t deleted although deleted on the creation page). However it still doesn’t consistently save new new labels even when they are not in the controls.
Anonymous User 14808221
(@anonymized-14808221)
It’s expected that to DELETE a Custom Field / Group you need to do that in Control screen.
Deleting them in the group edit screen only removes them from Types Control
Elaborated here:
https://wp-types.com/documentation/user-guides/using-custom-fields/#introduction-to-wordpress-custom-fields > Adding Fields to Groups > Blue disclaimer
Adding Fields works fine with Types 1.9.1
If this does not work on your end, it’s either a compatibility issue or Custom code interfering.
If you can exclude all 3rd party software to be the source of issue, please register here and open a ticket here, so I can login and see this.
Wouldn’t have guessed until experimenting, because I wasn’t even aware I had configured any controls. Could use a prompt when deleting in the groups edit screen or something.
What’s the difference between the Control screen and Types Control? Path please?
What does Types control do anyway? To stop controlling with types would do what?
I takes a minute for the label to show up in controls by the way.
