Hudson Atwell

Hi @pingram3541 @mottenkiller

Thank you two so much for the heads up. I’m implementing continue 2; now. 2.7.9

Although I’m not actively developing this tool anymore, I do try and fix it when it needs it. Please contact me via Twitter @atwellpub or Hudson Atwell @ LinkedIn whenever you see bugs like this in the future.

I do want to rebuild this, I just have a full time job now with Codeable.io so I hardly ever have any dev hours… and the Inbound Now suite is gigantic… too big for just me… and needs to be rebuilt to reflect best understandings learned through its lifetime.

Happy to network!

Nothing in the PHP error logs or the developer console.

Here, I took a quick video illustrating the process, checking the logs, and checking the developer console.

https://www.screencast.com/t/ZPE6DwPqR

Hi Milan,

I tried pushing the site to staging and switching themes to twentyseventeen, and deactivating all plugins but bbPress and GD bbPress Attachments, but the first post still did not allow an image attachment while the second reply did.

I wonder if this is limited to WPEngine hosts.

Kind regards,

• This reply was modified 5 years, 9 months ago by Hudson Atwell.
• This reply was modified 5 years, 9 months ago by Hudson Atwell.

This does not sound like a normal plugin error. Most likely there is a theme or plugin conflict causing this behavior and you’ll have to root it out.

Hi Wregger,

These errors were due to a lack of support for PHP 5.2 and this has since been changed. How is your experience now?

Xavier,

From a new user perspective that’s a fair review. But it’s not fair from a developer’s perspective. We don’t have capital investors and we don’t make enough money from the venture to cover a third of the time we put into building this dream.

To say I’m not serious is wrong too. I work every day improving, developing and supporting.

I expect a little bit of help and understanding from my userbase.

Users can protect themselves by waiting a little while to update. Checking the support threads to see if other users are having issues. Keeping a plugin backup onhand. That to me is a serious user and illustrates understanding and shared responsibility.

I think you give good advice in the form of warning, but you do David and I a disservice by giving us a 1 star review.

Leads has undergone many structural improvements since your review. I welcome you back and welcome your commentary.

How is your experience now?

Inturbidus if you are still using our tools and your experience has improved, please consider increasing the stars in your review.

I’ve added in fixes for these. Thanks for helping us discover new issues. Please consider providing us with a more favorable review if you still use our free tools.

Also we provide excellent customer support at https://support.inboundnow.com

I’ve added in fixes for these. Thanks for helping us discover new issues. Please consider providing us with a more favorable review if you use our free tools.

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

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!

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?

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.