Creating leads in triplicate

Hi David,

hmmm, we only ever observed a “trigger finger” effect where user would click multiple times on submit button… I assume it’s always a triplicate, i.e. it’s never 1 or 2 records, always 3 (which would indicate some coding issues not user’s behavior)… I also assume that there are no plugins or workflows registered on lead create event (if there are any, please deactivate them while testing)

Can you please let us know:

• Your theme (we are aware that some themes aren’t really bootstrap friendly)
• List of plugins activated on the site (to make sure
• Plugin shortcode from the page with all attributes (I assume some variant of msdyncrm_form shortcode)
• Is the page bound to an entity (property that you can see at design time) and if any parameters are being passed to it

Thanks
AlexaCRM Team

• This reply was modified 7 years, 11 months ago by alexacrm.

Hi

I’ve just updated the plugin to the new version and I’m afraid it is still doing it. Definitely not trigger finger as it is 3 every time (and my careful finger :).

In answer to your questions
– We’re using Sydney
– Other plugins are Aksimet, Better Font Awesome, Cookie Law Info, Duplicate Page, FAQ, Form Maker, Insert Headers and Footers, Jetpack, Page Builder by SiteOrigin, Page Links To, Search Engine Visibility, SiteOrigin Widgets Bundle, Sydney Toolbox and Yoast
– Shortcode is [msdyncrm_form entity=”lead” name=”Wordpress Lead” mode=”create” captcha=”false” message=”You are awesome. We’ll reply as quickly as we can.” default=”{leadsourcecode:Web}” validation_error=”Aw man! This couldn’t be submitted. Please try again” hide_form=”true”]
– the page is bound to the Lead entity (as a lead is what we’re trying to create)

Thanks
David

Hi David,

trying unbinding the page, i.e. setting it to nothing.Binding is really for read-only pages, we’ll make a note to clarify it in the docs.

Let us know if the problem is still there.

Any chance we can get a log file sent to [email protected]? Location of the file is on About tab of the plugin settings.

Cheers
AlexaCRM Team

Thanks – I’ve unbound it and I’m still getting it in triplicate.

I’ve looked in the directory on the plugin settings page nd the only file there is an .htaccess file. Is that the one you want?

Thanks
David

David,

the exact location of the log file is shown on the About tab of the plugin settings. Usually it’s in the storage subfolder of the plugin installation directory.

Are you able to use tools like Fiddler or even browser-based tracing to see how many submit requests are being sent to the server?

Also, can you check if you have any workflows or plugins on the lead entity?

Failing that, please contact us on [email protected] – we can do a Skype session with screen sharing to help you to get to the bottom of the problem.

Thanks
AlexaCRM Team

David,

it’s been a while and I would like to follow up on the issue. Is it still happening?
Someone else reported a similar issue on github and I wonder if it’s the same route cause.

Two suspects: CRM plugins, etc and WordPress side of things.

As a quick test, can you add a form for a different entity and test it. Do you get those records in triplicate as well? If not, that’d be then a side effect of something in CRM, if yes then it’s on the WordPress side of things.

If it’s WordPress then I suspect some other plugins or theme interfering – we can investigate furher

Thanks
AlexaCRM Team

Hi Alexa guys/gals

Thank you for following up, that’s awesome. To be honest, I haven’t tried since the confusion about the .htaccess file. We’re considering enabling Dynamics Portals on our website, not for just our “Contact us” page but if we do get that sorted then we’ll naturally route all inbound engagement through the portal.

Lots of the plugins, yours included, have gone through updates since we last tried so in the next few days I may try update all and have another bash. If it all works seamlessly, we might consider using it instead of portals.

If we’re still getting stuck, I’ll come back here and post again.

Thanks
David

Hi David,

we do now suspect that it’s a result of interaction with either another plugin or the theme. If you decide to try again, please send us the list of your site plugins to [email protected] – we’ll match it against another problematic site – that will help us to narrow the scope.

Thanks again
George
AlexaCRM Team