This Borks (screws up) Contact Form 7

Please post live link to the page in question with the live problem. Otherwise we can’t solve this. Thanks

You can disabled form pre-population in Leads->Global Settings and the inputs will stop being remembered for your users.

This kind of topic is better posted on our support forms.

A 1 star review for a feature that can be disabled and a case specific oddity due to a new release is an aggressive move. It’s vindictive even.

We are looking into the issue though. We think it may be related to some other issues users are having with duplicate lead notification emails.

I found and disabled that checkbox and it made no difference – the same behaviors occurred.

I have a site under development that has the problem – I’ll look into creating a test case. Only it messes up the forms and it’s a live site so I don’t want to leave it active.

Please post live link to the page in question.

Update,

After our latest update form population is automatic and there’s no toggle to turn it off.

We will support an exception class in our next release where you can add ‘nopopulate’ as a class name to the cf7 form and it will prevent auto population.

For most cases it’s a good thing.

Issue dealing with form prepopulation.
https://github.com/inboundnow/leads/issues/98

Still looking into dupe post issues. I have confirmed it.

For this level of free support I believe you can take the one star gun off the head and leave it on a 3 star level until the other problems are solved.

What do you say?

Happy holidays… From the user point of view, I truly don’t expect a supporting plugin like this to bork my site. People use CF7 widely so I do not think it wise to negotiate down the seriousness of this side effect. At such time that your updated plugin causes no such problems and demands no special attention to use, I will crank up the rating. Thanks for your attention to this, honestly.

Happy holidays!

Very fair appreciate it will keep you updated. . A fyi: Our form creation tool can absorb all the powers of CF7 and we have better quality control over our own form component. David told me last night that he had a break through on the CF7 issue and solving this issue will also solve an outstanding issue we’ve had concerning duplicate emails a couple of our customers are experiencing.

Also with us, I’d always recommend waiting a week or two before updating to let things settle. We usually have a major release and then a couple of subsequent releases to solve the bugs that show up and then it will settle and stabalize. When we move to a SAAS model we’ll build a beta team and even hire a Quality Assurance guy to build unit tests and front end macro tests for every support issue we encounter.

That’s tomorrows dream though!

New updates are in place with a manual fix for CF7.

Hey Hackerdon

The fix is in place.

Do you want to update your review?