Position and location with same name

  • Resolved CodedFault

    (@cconard92)


    6 years, 8 months ago

    There appears to be bug where if there is a location and position with the same name, they act like the same field (at least in the edit member form). For example, we have a location “Technology” for our technology department and a position “Technology” for our districts main contact form that represents the external contact for technology.

    If you try to add anyone to the location “Technology”, that automatically get the position “Technology”. Neither tag can be removed unless you uncheck both of them and then save.

Viewing 1 replies (of 1 total)
  • Plugin Author DBAR Productions

    (@dbar-productions)

    I don’t believe that has anything to do with code in my plugin, but it is how WordPress itself handles terms and taxonomies. Members are a custom post type that my plugin creates, and Position and Location are taxonomies. Any entries you create for a position or a location are a term, and it appears (from a quick google search) that WordPress doesn’t differentiate between identical term names, even if they belong to different taxonomies. For examples, see these posts:

    https://wordpress.stackexchange.com/questions/60702/why-does-wordpress-combine-a-term-with-the-same-name-in-the-wp-terms-table

    https://skyverge.com/blog/dont-share-terms-between-wordpress-taxonomies/
    This second one explains how you can modify the term slug, while leaving the name the same, so that the terms will be treated as different terms (need different slugs).

    I’m not doing anything special or custom with the taxonomies and terms, and am using standard WordPress functions to create, edit, and save those. So, this is just one of those weird things with WordPress, and you’ll need to create slightly different term slugs or names, if for some reason you need a position and a location with the exact same name.

Viewing 1 replies (of 1 total)
  • The topic ‘Position and location with same name’ is closed to new replies.