WordPress.org

Ready to get started?Download WordPress

Forums

[Plugin: Custom Field Taxonomies] Rename custom field key? (4 posts)

  1. kidradio
    Member
    Posted 2 years ago #

    I am using Custom Field Taxonomies 2.0.1 and I am receiving the message of "A name is required for this term" when I try to convert a custom field into a Taxonomy.

    I've seen an older post saying it may be due to the use of utf characters. I've gone through and removed all utf characters and still had the same issue. Also, the custom field keys I am trying to convert have capital letters and spaces. I've saw scribu mention on another post that you could just rename the custom field using the "Rename custom keys" box, although that box is not visible anywhere. Was this functionality removed from the 2.0.1 version? Or is there a compatibility issue with wp 3.2?

    This would be great to sort out since I'm not really seeing any alternatives out there.

    http://wordpress.org/extend/plugins/custom-field-taxonomies/

    Thanks!

  2. scribu
    Member
    Posted 2 years ago #

    It works just fine for me, converting custom fields with the key "Caps and Spaces".

    Please post some example custom field values that aren't working for you.

    There's no point in adding a "Rename custom keys" box, since they'll be replaced with the taxonomy name anyway, when they're converted.

  3. kidradio
    Member
    Posted 2 years ago #

    Thanks for the quick response!

    Here is a link to a listing of all values for my "Artist Name" field. I've done some more testing and have not been able to replicate the problem on another wp install (although I was not converting nearly as many values). I was also unable to convert the key of "Label".

    What are the known reasons for the "A name is required for this term" message?

  4. scribu
    Member
    Posted 2 years ago #

    Well, it happens when you try to create a term with an empty name.

    In any case, even you get that error message, all the usable custom fields will have been converted.

    The development version (2.0.2-alpha) shows you a list of all the fields that couldn't be converted.

Topic Closed

This topic has been closed to new replies.

About this Topic