Json error dropdown (me too)

so the json error on dropdown comes from a javascript error on your page. The dropdowns are displayed using the HybridDropdown plugin and the json error can result from multiple reasons. Can you inspect your page to see if you have any errors on your console?

Thank you so much again for your readiness to help! The console thorws no errors, neither in the backend nor in the frontend.

However, now that you’ve mentioned the HybridDropdown plugin, I’ve found a warning (not an error) in the console:

HybridDropdownError:Option list has duplicate value: size=

Can this be related to the error? Any clue to point me in the right direction?

Thank you again!

Can this be related to the error? Any clue to point me in the right direction?

yes, that’s the issue. Possibly due to duplicate field name?

There are no duplicate field names in the form. Actually, the form is very simple. Here’s a screenshot of what I’m facing:

https://ibb.co/7vdHCPX

(As you can see, the only field that works is the featured image field).

I’ve started a blank form and the dropdowns seem to work fine. I still don’t know at which point it becomes corrupted, but I’ll take a deeper look at it. The migration to version 5.0 was perfect and flawless (as I said on my review), but at some point the post creation dropdowns became JSON-errorish. I tried several rollbacks to 5.X, but CF7 has updated every form’s database, and rollbacks don’t work. The strangest thing is that the form works fine in the frontend, even though I can’t edit the field mapping.

Please allow me a few more days to debug the error. If I get to a solution, I’ll post it here in case others experience this, too. Thank you again, Aurovrata.

OK. I’ve got it. You and I were right: there are not repeated fields, but the dropdowns detect other shortcodes as repeated fields.

Let me elaborate. I’m using “Shortcodes Ultimate” plugin to create columns. These are created with the shortcode format:

[su_row]
[su_column size="1/2"] CONTENT [/su_column]
[su_column size="1/2"] CONTENT [/su_column]
[/su_row]

At this point, Post My CF7 Form thinks that [su_row], [su_column size="1/2"], [/su_column] and [/su_row] are fields, and since I’m using several columns all across the form, the plugin thinks that those are repeated fields.

I am aware of your “Smart Grid-Layout Design for Contact Form 7” plugin to create those columns, but I’ve tried it twice in the past and all my forms broke (that’s another story), and I prefer to avoid as many plugin conflicts as I can. For now, I think the best solution is to use CSS classes and media queries to recreate those columns instead of using Shortcodes Ultimate.

Thank you very much again for giving me the key clue to find the solution. I’ll leave this topic opened in case you want to add something, but feel free to mark it as resolved.

ah yes, that would pause a problem.

I am aware of your “Smart Grid-Layout Design for Contact Form 7” plugin to create those columns, but I’ve tried it twice in the past and all my forms broke (that’s another story),

sorry to read this. I would rather focus my energy on fixing the Smart Grid as i ensure that it works with the Post My CF7 Form.

I made a change to the way the fields are identified in the form.

The changes are available in v5.4.2beta on the GitHub repo

Can you manually update and let me know if that fixes the issue

OMG!!! It works!!!

First, when I activated the 5.4.2beta version, a message popped up:

CF7 2 POST WARNING: Your form is live! Changing its fields and mapping may create inconsistent data entries.

But when I selected the Post Creation tab, BOOM, all my fields were there, as expected. ?? ?? No more json errors! All I had to do was turn on the draft-live toggle switch again. Then, in the frontend, I submitted a test post and all the fields were magically mapped, as expected.

Thank you so much!!! I look forward to having this fix included in the next release. You can now mark this topic as truly resolved! ??

Just a quick note: hidden fields are not fetched in the field selection dropdown. (Maybe hence the message that popped up, because it possibly detected that some fields had changed). Not a big deal, anyway. Thank you!

• This reply was modified 3 years, 3 months ago by codimex. Reason: Adding more info

CF7 2 POST WARNING: Your form is live! Changing its fields and mapping may create inconsistent data entries.

when a form is live and submissions have been saved as posts already, the plugin throws this warning because subsequent mapping may change the data structure. It’s not an error, just a warning so make sure you understand what you are doing.

Thank you so much!!! I look forward to having this fix included in the next release. You can now mark this topic as truly resolved! ??

great, will push it out.

Just a quick note: hidden fields are not fetched in the field selection dropdown.

let me check that first….they should be visible in the dropdown.

so I confirm the hidden fields were not being picked up…. this is now fixed in v5.4.2, could you update and confirm?

Version 5.4.2 works perfectly. No warning popup, all fields mapped as expected. THANK YOU! Also, I’m glad that I could be a little helpful on this.

Marking now as resolved with all honors. ??

thanks, good to know!