After upgrate to latest in August 28, 2012 I have multiple duplicate entries

First off, calm down.

We have absolutely no control over your web site, so we have no control over the themes and plugins that you have installed and no control over the code within those themes and plugins. The end result is we can only control what Gravity Forms does and we can't prevent other code on your site from interfering and changing Gravity Forms code or code output. So you need to keep this in mind anytime you run into issues with a WordPress theme or plugin.

The issue you have encountered cannot be replicated on our end. This means it's an issue that is only happening on your site. That isn't to say other users can't encounter this same situation, what it means is the issue is being caused by something else on your site that is changing the Gravity Forms behavior at the code level.

We know exactly what the issue is.

The issue is a javascript error that is caused by an ampersand character being escaped when the form is output. This should NOT be happening and it does not happen when we test Gravity Forms locally on a default WordPress install.

Why does this happen with Gravity Forms v1.6.6 and not Gravity Forms v1.6.5? Because the ampersand that is being escaped was part of a code change in Gravity Forms v1.6.6.

But the bottom line is it should NOT be getting escaped and is NOT escaped in a default WordPress install which means code in your theme or another plugin is manipulating and changing core WordPress behavior and causing this javascript error to occur.

What this means is either your theme or another plugin on your site is manipulating shortcode output and escaping the ampersand that is being output in the AJAX related javascript that is output on the page by the shortcode... breaking the jQuery in the process.

This isn't something we can "do our job" and fix without your assistance. The issue is happening on your site and is being caused by your theme or another plugin on your site. It's a code level issue that is happening and therefore not something we can magically fix without first determining what code on your site is producing the problem.

As this is happening at the code level, you have to determine what code is causing the problem.

We can't do this. We don't have access to your site and all we can see is the output, we don't see what is happening behind the scenes at the code level.

What Chris asked you to do is correct. You have to test for theme and plugin conflicts to determine where the conflict is coming from. In order to do this you have to follow the test instructions here: http://rkt.gs/testing

You would follow the instructions and then the end result is you would be able to tell us if it's your theme or another plugin that is causing the issue... this is NOT something we can determine without performing this test. The issue is at the PHP code execution level and not something we can debug and fix just by viewing the front end page.

This is standard debugging procedure when encountering a theme or plugin conflict in WordPress and if you are running your own WordPress site then you need to be comfortable performing procedures such as this because it's key to narrowing down the cause of theme and plugin conflicts.

This isn't something we can do ourselves, unless you provide us with access to your site... in which case we'll be glad to do so.

Without narrowing down which code on your site is causing this issue, we can't determine how to resolve the issue. It's as simple as that.

Frankly you have code on your site that is manipulating and changing core WordPress behavior... which it should not be doing. You should WANT to determine the cause.

I can tell you with about 90% certainty what the cause is... you are using a ThemeForest theme. They are NOTORIOUS for causing problems like this with plugins because most of the theme developers selling on ThemeForest have NO clue what they are doing. It's common for them to manipulate the wp_content output or change shortcode behavior. Changes that should NOT be made.

If you can perform the test and tell us if it's your theme or which plugin is causing it (most likely your theme), we'll be glad to them take a look at the theme code and tell you what the theme is doing wrong that is breaking things.

OR if you can email me a copy of the theme you are using to carl@rocketgenius.com I can install it locally and see if my 90% certainty is correct and if it's the theme and if so what needs to be corrected in your theme.

Bottom line is other code on your site is causing the issue and we are more than happy to work with you on resolving the issue but it's code specific to your site and not something we can replicate locally so you need to be willing to work with us to get to the bottom of it instead of fighting and yelling at us.

Another update... the cause of this issue is the RAW shortcode that seems to be so popular with ThemeForest theme developers who are completely clueless. This code changes core WordPress behavior and negatively impacts your site. It's this code that is causing the javascript error that is causing this problem.

Here's a screenshot of an example of the offending code that came from the "Striking" theme sold by ThemeForest:

http://dl.dropbox.com/u/185347/Slingshot/Pictures/Screen%20Shot%202012-09-05%20at%203.54.41%20PM.png

This code causes the javascript error when AJAX is enabled because it changes default WordPress behavior. By default WordPress does NOT auto-format shortcode output. This code changes this behavior and tells WordPress to auto-format ALL shortcode output. The end result is Gravity Forms does not behave the way it is designed and a javascript error is caused.

Unfortunately due to the way WordPress works there is nothing we can do to prevent conflicts such as this from happening. We can't control what a theme does and can't prevent it (or another plugin) from breaking functionality or changing core WordPress behavior.

All we can do is help users who encounter these issues as they come up. It's too bad we are the ones that end up having to provide you with support when ultimately the cause of the problem is a theme developer who doesn't know what they are doing.

I don't have a copy of your theme but I can tell you with 99.999% certainty that your theme has the same code in place and that is the cause of the problem.