Bug: CPT_TAXONOMY::wp_set_object_terms checks capabilities

  • This is a bug, and inconsistency with wp_set_object_terms.

    The CPT_TAXONOMY::wp_set_object_terms currently checks capabilities, this is wrong place to do it. Notice that wp_set_object_terms doesn’t check capabilities, for a good reason, this is a wrong place to do it. Just as wp_insert_post doesn’t check capabilities either.

    Capabilities must be checked during form action handler.

    I can’t use CPT_TAXONOMY::wp_set_object_terms in the front end at the moment cause it incorrectly checks capabilities.

    https://www.ads-software.com/plugins/cpt-onomies/

Viewing 1 replies (of 1 total)

  • Why is it wrong to check capabilities there?

    I would argue that that’s the best place to check them so someone can’t just run the code and assign terms whenever they like.

    But I’m open to debate/discussion. Why do you think this is wrong? Why is it giving you issues?

Viewing 1 replies (of 1 total)
  • The topic ‘Bug: CPT_TAXONOMY::wp_set_object_terms checks capabilities’ is closed to new replies.