Skip to content

Name collision with get_post_status filter #905

@davidmpurdy

Description

@davidmpurdy

Not sure if there's a backwards-compatible way to fix this, but I tracked down an error to the Edit Flow plugin's "post_status" taxonomy name triggering a call to get_post_status filters - but whereas I have a plugin that expects that to be the core filter to be related post statuses, it's actually triggered by get_{$taxonomy} running on the Edit Flow taxonomy called post_status.

The practical fix is to get the other plugin to more carefully check what it's actually being passed, but I don't feel like I can entirely fault them for using the get_post_status filter as documented, either.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions