Support » Plugin: Gravity Forms + Custom Post Types » [Plugin: Gravity Forms Custom Post Types] Taxonomy field broken

  • Chris

    (@renaissancedesign)


    Cancel that, appears to be another plugin at fault.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Chris

    (@renaissancedesign)

    Nope, turns out it’s not the other plugin. At least, not entirely.

    When used in conjunction with the plugin Gravity Forms – Update Post, this plugin does not allow taxonomies to be updated because GFCPTAddonBase->save_taxonomy_field() passes wp_set_object_terms() a value of “true” for the “append” argument.

    Since this plugin is purely aimed at creating new posts for which it’s reasonable to assume no terms exist that argument can (and should) be false. If nothing else, for the sake of being a good neighbour and not breaking the other plugin.

    Plugin Author bradvin

    (@bradvin)

    Hey Chris,

    I am looking at updating the plugin in the next week, so I will include this change

    thanks

    Phil

    (@philnelsonweb)

    I too was using GFCPT to update existing posts, with taxonomies represented by checkbox fields. The GFCPT plugin successfully assigns new taxonomies (appends new), but fails to unassign taxonomies whose checkbox is unchecked.

    As Chris noted, the issue appears resolved once I remove the “true” (for the “append”) argument from wp_set_object_terms() in GFCPTAddonBase->save_taxonomy_field() (under the condition of $field[‘type’] == ‘checkbox’). I didn’t try to imagine potential use cases this edit might break.

    Thanks Brad and Chris.

    I am using this to create Posts and am having the same problem in that the taxonomy field no longer displays the checkbox – a problem as its a required field.
    What is the quick fix I can make?

    Just found the conflict is with User Access manager new version 1.2.3 out yesterday. Will this be the same issue?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: Gravity Forms Custom Post Types] Taxonomy field broken’ is closed to new replies.