• Resolved cdonner

    (@cdonner)


    It is late and I am bit lost. I am using WCK Post Type Creator and Taxonomy Creator but ACF for custom fields.
    I have been setting up the site structure for two days until I realized that I had an issue with a custom image field. Apparently when the image field return type is changed after a post is created, the value does not get updated and remains the old type. I was not able to get my image to return the URL, it always returned the ID. So I deleted the image from the library and from the post. This broke the Add Image function system-wide. It just spins forever. Uploading images results in an error (the file makes it into the wp-content folder, but the field is not populated). I can still browse the media library and add to it there.

    So I figured I’d start to remove post types and taxonomies. First I deleted the custom post type. The behavior remained when I recreated it. Then I was no longer able to link the taxonomy back to the recreated post type. When I updated the taxonomy, all the values were stripped and an empty taxonomy was saved. So I deleted the taxonomy. Now I am trying to recreate it but have the same issue. When I link it to post types, it does not save properly. I can save a new taxonomy with just a name and the labels, but not when it is linked to post types (not even Post).

    It is obvious that some artifacts remained in the database from this. I’d hate to blow away all my custom fields, post types, and taxonomies, and start from scratch. Is there an easier way to narrow down the cause? Maybe this is a known issue?

    https://www.ads-software.com/plugins/wck-custom-fields-and-custom-post-types-creator/

Viewing 1 replies (of 1 total)
  • Thread Starter cdonner

    (@cdonner)

    It turned out that this was caused by the Advanced Custom Fields – Taxonomy Field add-on and not by WCK. This plugin isn’t even needed, because ACF handles taxonomy fields already. Once I disabled the plugin, things started to work normally. Why this plugin worked for a while and what broke it I cannot say. I still believe it was data-related. I tried to remove individual posts and postmeta rows from the database that I thought could be causing it, but this did not lead anywhere.

    It is a bit unfortunate that there is not a more meaningful error message and that diagnosis is very cumbersome. It appears that many people saw similar symptoms after the WordPress 3.5 upgrade. There is much chatter in the forums from about a year ago, but no meaningful advice. This post ultimately made me go about it in a more methodical way.

Viewing 1 replies (of 1 total)
  • The topic ‘Cannot save taxonomy’ is closed to new replies.