Anonymous User 14808221
(@anonymized-14808221)
This is strange, when I use the Types version you can download here I can save and edit the Fields just fine.
This must be something connected to either several (!) fields, low server timeout and vars values (which cannot just be overwritten by ini or config overwrites, but only by server admins on the server side).
Can you turn on WP Debug and let me know if some error is produced, when you perform those steps?
As well, did you test this without any other plugin and a native WordPress Theme?
Often, the issues begin somewhere and end somewhere else. Especially timeouts and memory allocation issues or var inputs.
Please let me know if the steps above lead to some results
I also suggest replacing the current copy of your Types Plugin with a Fresh copy from the link above, to be sure no files are corrupt
Sorry for the delay – here’s what I see after enabling debug:
Nothing. No debug messages at all. Deleted a field, won’t save. Edited a field, won’t save.
All other plugins are disabled. I dunno why the theme would matter, but switching to Twenty Seventeen did not change anything either.
Downloading a new copy of the plugin did nothing either.
-
This reply was modified 8 years ago by
echoleaf.
-
This reply was modified 8 years ago by echoleaf.
-
This reply was modified 8 years ago by echoleaf.
I just need to delete some of these damn fields that don’t work at all like normal custom fields.
How do I edit the wpcf-fields table to delete a field manually?
Anonymous User 14808221
(@anonymized-14808221)
It is not suggested to delete them in the Database as you would need to delete the entry in the post meta table but as well the stored options for those fields.
What you can do, is head to Toolset > Custom Fields > Custom Fields Control and delete them from there.
This will delete them completely and safely.
But, it’s unexpected that you cannot save or edit them and no error is thrown.
Plase as well enable WP Debug Log.
It may be that you get an Error 500 in the Console of your browser when you perform those actions and do not see the PHP error (exhausted memory, most likely) directly on the screen.
For this, if you enable WP Debug Log, you can later see the error in the Debug Log in your FTP files.
That may be a something related to memory allocation, please let me know.
Do you have an unusual number of Taxonomy Terms or Custom Fields in this install?
I found the custom field control & deleted most of the fields. Changing the field type of one from ‘file’ to ’embedded media’ didn’t work so I deleted it too. Thanks for your help.
