Two Row Studio

1) Still have the issue with version 1.11.0
2) Only see 15 lists for the account
3) the selected lists associated with each form are among the 15 seen on the list admin screen (they are selected from the plugin’s own generated list of lists)

The issue is not present when multiple lists are selected for the form, but there is no way to indicate which ones should be selected by default for the form. The forms submit perfectly well when I comment out the code that creates the wrapper for forms associated with only one list. From these symptoms, I don’t think that the issue I’m having is related to previous threads throwing this same error.

It is each of the forms in the body of the page. The current version has been updated so that the problematic code is commented out. This is a workaround I needed to put into place so that the form would submit without error.

As for embedding only a single form, you can see that done on this page:
https://live-brighton-main-streets.pantheonsite.io/support/volunteer/

It was this page that originally alerted us to the issue so I’m certain it is not due to multiple forms existing on a page.

I’m wondering if instead of wrapping the markup in a div with style defined to have a display:none that wrapping it with a div.single_option class or something similar might not be a better choice. Then you could set the class visibility to “hidden” and height to 0px so that the field can still be validated.

further info: I’m using Version 1.10.1 of the plugin

I’m not sure if my experience with the plugin last evening may be of assistance here or not.

We had a situation where upon the release of 1.5, my client’s authentication ceased to be valid. The error message was that the account was locked out due to too many failed login attempts. At which point our embedded forms would not display and in fact seemed to cause a php error. I do not have that error code as our production system is on an AWS Elastic Beanstalk deployment.

We tried to update the credentials, and could not get the site to re-authenticate using 1.4.13 (I think. It was the immediate release version to 1.5) The error was that the “email was not available for authentication.” I eventually clicked the button “Reset all settings” and the site went down. We could not navigate to either the WP dashboard to the public facing site because of an error.

I restored the database backup from our nightly backup and got the site restored and then attempted to troubleshoot in a development environment.

I then updated the plugin in my dev environment and re-entered my credentials using the Pardot Authentication type (Which was only now available after the update and was able to connect.

There are two things that come from this for me:
1) the error seems to be related to the API itself not accepting backward compatible requests smoothly. Perhaps they were supposed to be routed somewhere differently or whatever, but that seemed to fail for our connection under the 1.4.13 version.
2) trying to completely reset the settings for the Pardot configuration was further missing error catching that brought down our site.

I don’t know if this helps troubleshoot this particular issue, but it seems to have some bearing to me.