Support » Plugin: Post My CF7 Form » Cannot map to more than one custom taxonomy; admin interface very buggy

  • Resolved tnightingale

    (@tnightingale)


    The admin screen for mapping is super buggy. I have an existing custom post type (registered manually) using ACF custom fields. When I’m adding custom fields to the map, sometimes some of the selections get reset to blank (after saving draft), or are mixed up and the wrong form fields are mapped to the meta fields, or some are completely gone. If I leave that screen and come back by clicking the link on the Contact Forms summary page, sometimes they are fixed, sometimes I have to select the meta fields and form fields again. Eventually after re-saving as draft multiple times it seems to “stick”.

    Then for the custom taxonomies: I have two, one “Professions” and another “Countries”. I was able to add and map each one to corresponding form fields, but as soon as I finish that selection process, there’s a message appearing briefly below the Save buttons saying “Something is wrong, try reloading the page” then right away the page reloads by itself and the second taxonomy map is then completely messed up, in one of several ways: just not there, or there but the name is missing (only the edit link is there), or only the form field is there, or there’s a duplicate of the first taxonomy map (but with a singular version of the name). When the edit link is still there for the taxonomy, and I click it, it sometimes shows the correct taxonomy info, sometimes no info or the wrong info. If I delete that map (using the red minus sign in the circle) and try to add it again from scratch, the same thing happens. If I save the whole map, then return to view it, the second taxonomy mapping is missing the form field selection (just shows “Select a form field to map”), and the name of the taxonomy is missing, only the Edit link is there.

    I tested a form submission and everything worked except the second taxonomy.

    I’ve gone through the entire process twice, same result.

    I made sure my custom taxonomy labels are one word, no spaces.

    The “Professions” taxonomy has the terms in the database, and the CF7 form has the matching checkbox options. For the “Countries”, same thing, except the CF7 field is a select box.

    Very frustrating!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Aurovrata Venet

    (@aurovrata)

    looks like you’re having a tough time.

    I have an existing custom post type (registered manually) using ACF custom fields.

    ACF only allows you to create new fields, not custom post types. What plugin are you using to register your cpt?

    When I’m adding custom fields to the map, sometimes some of the selections get reset to blank (after saving draft), or are mixed up and the wrong form fields are mapped to the meta fields, or some are completely gone

    you need to understand one fundamental concept in meta-field creation which explains why you are facing so many issues.

    Unlike post types and taxonomies, meta-fields are never ‘registered’ by WordPress. A post type or taxonomy can be registered and appears on your dashboard regardless if you have created any posts or terms respectively.
    A new meta-field only get created once a value is stored for a given post.

    Hence this plugin is only able to pick up meta-fields that have actually been saved with values in the DB.

    A plugin such as ACF actually registers a meta-field witin its own plugin settings configuration and is specific to the ACF plugin and unless a value has already been stored for that meta-field (ie you have a post in your post table with that meta-field saved), then that meta-field simply does not exists for the rest of the std WP environment. As a result the Post My CF7 plugin is not able to discover your meta-fields when they are creaed with the ACF plugin.

    Others have complained about this, but till date I have not had the time to make the plugin compatible with ACF created fields.

    What this plugin does on the other hand is create custom post types and meta-fields for you. So if you wish to use Post My CF7 form, don’t use ACF to create meta-fields for your forms mapping, let the plugin handle it for you, you’ll find the plugin a lot more stable and productive.

    Thread Starter tnightingale

    (@tnightingale)

    Hello and thanks for the quick answer.

    As I already stated, I’m not using a public plugin to create the CPT, it’s coded manually (my own plugin for that purpose), and ACF is used for the custom fields associated with the post type.

    Your plugin IS finding the ACF fields – they are there to select in the drop down list of meta fields. They just don’t always seem to stay selected when saving the mapping as draft.

    My client will be editing these posts so I need to give them the user friendly ACF interface.

    The submission ends up finally working with the ACF fields (though I did notice the email submission listed the term ID’s instead of their names). It’s the taxonomies causing the biggest problem (nothing to do with ACF).

    I’ve decided to just write my own function to capture the form data, seems easier than I first thought, no need for the plugin after all (thought it seemed like a great idea initially, some others were recommending it for the type of setup I have).

    Thanks!

    Plugin Author Aurovrata Venet

    (@aurovrata)

    Your plugin IS finding the ACF fields – they are there to select in the drop down list of meta fields. They just don’t always seem to stay selected when saving the mapping as draft.

    any js errors on the console? any back-end errors when you enable WP_DEBUG?

    My client will be editing these posts so I need to give them the user friendly ACF interface.

    be careful that if you change the post fields once you have mapped and saved several submissions from your forms, then you can end up with broken posts. I would not recommend you change cpt/meta-fields of posts that have forms mapped to save submissions.

    I’ve decided to just write my own function to capture the form data, seems easier than I first thought, no need for the plugin after all (thought it seemed like a great idea initially, some others were recommending it for the type of setup I have).

    ok no worries, would have been nice to get to the bottom fo the issue though.

    Plugin Author Aurovrata Venet

    (@aurovrata)

    assuming you have resolved your issue and marking this thread as such

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Cannot map to more than one custom taxonomy; admin interface very buggy’ is closed to new replies.