Google New Multivariate Experiment error

I'm trying to get a New Multivariate Experiment in Google Web Optimizer to work on a squeeze page within amember (public_html/amember/templates/index.html)). The page contents are complete, the

"1. Test Page: Add Control Script, Tracking Script, and Identify Your Page Sections" is complete, including page sections etc.

and

"2. Conversion page: Add Conversion Script" is added to thanks.html in amember's templates.

..and Validating JavaScript Tags says,

"Congratulations!
All your pages have been validated and you are ready to continue and define variations."

And further says, "All of your pages have been validated. You may continue and define variations."

...but when i click Continue Google says,

"Warning: We've detected more than one occurrence of a given section name. This usually means that you have copied the script above without changing the section name. Please go back to your page and make each section name unique."


This is NOT correct. There is only one occurance of each section. And each is named uniquely. I've deleted the New Multivariate Experiment and removed the google optimizer code from the pages and started over from scratch with new code and new tests several times over past three days.

Each time I get the above error.

And when I 'continue anyways', none of the test work in preview mode. Only the default entries show.

So I'm guessing there's some code or setting conflict somewhere.

Any ideas where to begin to fix this error?

Thanks.

Andre
PS: Oh. I even took the header.html contents and manually added it to every template that called for header.html... then edited index.html and thanks.html so their headers would be unique from all other html pages served by amember. Did same with footer. Still no joy

PPS: I already also tried testing google validation with and without Google Analytics Account ID filled into amember advance window. The google error is the same either way

Oh. to be sure the code is fine I did enter my google web optimizer code into blank text files and they validated fine. But entering the same code into signup.html or index.html Google generates the error listed above. Something is amiss but i can't find it. hope you've already seen how to fix this.

thanks in advance

Nevermind.

I did a line-by-line removal replacing of each line of a 16-page sales letter and found two areas that independently of each other triggered the error:

1) Google Website Optimizer did not like this meta tage -> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

2) in the long 16-page sales letter there was a phrase within a <div>tag</div> that said, '10-13 blah blah blah' instead of '10 to 13 blah blah blah'. Once I changed the hyphen to the word 'to' the google error went away. The strange thing is, this text wasn't even part of the google web optimization at all. Go figure.

Anyhow, in case anyone else runs into this error imagining it might be amember related, test removing the http-equiv= meta tag if it is the same as the one i removed. Maybe that will work for you too.

No problem I wanted to save anyone else the hassle. Wasn't fun to find.

Had to take a blank text file and add the google web optimization code, and then save, and then validate. Once the original google optimization was validated I then added sections of html from my customized /templates/index.html over and over until the validation 'broke'.

That narrowed down the problem sections.

Then I did line-by-line removal from the 'broke' section, saved, validated again and again until the page passed validation. That's when i could know the exact removed lines that were the problems.

Then once i knew the lines I did a word-by-word removal, then saving, then validating over and over... until found which word/phrase on the line was the exact problem. In my case there were two validation problems.As noted. And sixteen printed pages of html to go through.

Wasn't fun at all to do. But at least now I know to use the word 'to' in my pages when using google optimization and not dashes. And I know to omit that meta tag.

Hope the pain saves at least one other person the hassles.

thanks for the link