Thanks Miked,

Seems you got me the result as version 1.17.2.9 now seems to be applying leadsources again!.
This has been functional since 4th Sept 09 12.56pm.
All I had to them was update all the leadsources previous using mass update and I'm back on track.

Thanks again.

Anton

Anton --

Thanks for working with Mike to address this. I know it was difficult for us to narrow down and required us to have to do more research to resolve.

Secondly, we don't have a complaint department. Every customer's concerns, interests and needs are important to us. We make many difficult decisions at the end of the day as to whose needs will be met with software defects, features and the like. It's difficult because we can't say that one person's concern is more important than others; however, we try to focus ourselves on the issues and features impacting the most customers at one time. I hope you understand that your experience wasn't intentional or negligent by us and see we have compassionate, caring employees who are vested in our customers' success.

Mike -- A HUGE thank you goes out to you for grabbing the reigns on this and working with the rest of the Dev team to identify, isolate and address this.


~Joe

Joe,

Perhaps opening up a complaints department would be useful. Currently, the entire process of addressing issues is not really working. It seems to be more of a voluntary thing rather than a clearly delineated process designed to help paying customers.

And something else you might consider...

Before any changes are made, you may want to proactively float the idea in the community, especially if the changes are going to affect other applications.

Recently, a new hidden post field was added to web forms, which is being passed back to applications.

For the life of me, I cannot understand why you would choose to pass a variable by the name of "name". Do you know how many legacy applications are using "name"? Why couldn't you give it a less generic name?

This is 2009, with 2010 around the corner. We don't do things like that any more.

Use names like "is_form_name" or whatever other non-generic name, but, for Pete's sake, not just "name". Infusionsoft is NOT operating in a vacuum.

Best,
Bob

Joe,

Little did I know when I wrote the previous post that I was a victim of your latest experimental programming...

Wordpress already uses "name"... and that managed to break one of my payment thank you pages. At this point, each time you redirect to a thank you page within Wordpress, it doesn't work.

Other clients have reported the same problem as well.

Who makes these "smart" decisions at Infusionsoft?

Isn't there any quality control taking place?

Must everything be run on a experimental basis with us as beta users?

This kind of stuff is costing money and reputation.

And yes, where is the complaints department?

Best,
Bob

Name was added because people wanted an easy way to look at their code and know which Web Form it was. You used to be able to just look at the Id, but Id was swapped out for Xid during the push for PCI compliance.

It is not used by the Web Form processor at all, other than being logged in the person's notes for your records. You may safely remove the field if it conflicts with the rest of your page.

Mike,

Thanks for the feedback.

Please do give advance warning when you guys are going to make changes to things that affect the "outside" world. This is crazy, having to make changes to who knows how many forms... AFTER the fact.

Best,
Bob

Hi,

I can only agree with, and reiterate the comments Bob Keen has made in this thread.

Calling a field "name" is a big mistake. I also WASTED my time recently determining why some thank you pages were failing.

I might add another related point. Whilst your field naming convention is sound in only allowing/creating field names with alphameric, numeric and underscore characters why does the system append fields in the other fields box of a form with Custom- (Custom plus a hyphen), to be robust surely this should be Custom_ (Custom plus an underscore).

My view is that a mutlitude of these little errors and 'mistakes' are combining to prevent Infusionsoft from being classed a 'great' as opposed to a good system.

Believe me I want it to be great!

Yours,

Arthur.