getting tags in paragrpah text default values

bump

No on the copy and paste, all of the text was entered in directly. I created another paragraph text box to be certain and it is producing the same html tag bug.

My client needs this page launched ASAP so suggestions on how to get this fixed are greatly appreciated.

I appreciate that but it doesn't ultimately solve the problem/ You've already asserted that GF doesn't produce this error with TwentyTen but what about all of GF's options for overriding CSS classes etc. I was hoping to get some info about that as opposed to simply eating up time with trial and error.

Then I guess it's just buyer beware. I'm really sorry to see that.

I appreciate the offer but I performed a the plugin test before submitting my initial support request and already knew that wasn't the issue. And of course, GF wouldn't be expected to behave that way out of the box, so it is clear to everyone that there was a conflict, that's why I contacted support to begin with.

What I was hoping to encounter was a sense of understanding and perhaps recognition of what the problem might be and where I should look given how much support experience must exist for a product that sells as well as GF. Why spend three hours tracking down a problem when the support board can provide the insight needed to cut that time down to minutes? Or that was at least the plan.

At the very least, a straightforward "we've never seen this before" response followed up by an inquiry as to which theme was being used, if it was on a Network install, etc. which version of PHP/WP/etc. is being used would have been appreciated.

As of now, I simply took more of my time and resigned the form to work around the bug.

As WP themes become increasingly powerful and diverse, I can only image you're going to encounter issues like this more often. Although it won't do me any good, at least GF can benefit from the experience. In the meantime, I guess I'll simply have to satisfied with paying for GF while simultaneously having to work around it's shortfalls.

BTW, the theme is is "Awake" from themes.mysitemyway.com.

As mentioned, I've already taken the time to redesign the form so as to avoid the bug. And I do think you have a great deal of potential to streamline your support process to better direct your efforts and separate users into different skill sets. Being eager and helpful is great but effort, attitude, and achievement are typically mutually exclusive.

You restated the point I made earlier about finding the problem by asking questions and gathering knowledge. But the system you have in place to accomplish that is less than ideal. For example, you could improve your efficiency a great deal and get far more achievement out of the fantastic effort and attitude of the support staff by visiting the support forums at Shopp and Woo Themes. Adopting the processes they use could go a long way.

Although I'll be the first to admit I'm not in the norm, I don't really want someone to go in and fix a problem directly, I'd rather know how to properly troubleshoot and fix the problem myself so as to increase my understanding of the plugin and be better prepared to deal with issues in the future (and ultimately reduce your support load).