Comments on: Have a Look at the New Web Form Generator

By: John

John — Mon, 01 Mar 2010 15:02:10 +0000

You’ve sold it to me. I’ll sign up soon.

Great autoresponder!

By: New HTML Email Templates: Good Things Come In Pairs

New HTML Email Templates: Good Things Come In Pairs — Thu, 25 Feb 2010 14:51:00 +0000

[...] knew our new Web Form Generator marked the dawn of a new era for your email signup [...]

By: How To Market Like Nine Inch Nails

How To Market Like Nine Inch Nails — Tue, 23 Feb 2010 15:36:12 +0000

[...] try this with your own tracks, post offers with web forms on your website, to your Facebook profile, in your blog – and link to them everywhere. [...]

By: Justin Premick

Justin Premick — Fri, 12 Feb 2010 14:07:30 +0000

You can get an unformatted, basic form via the "Publish" tab in the Web Form Generator.

http://www.aweber.com/faq/questions/554/How+Do+I+Get+a+Basic%2C+Unformatted+Form%3F

By: C

Thu, 11 Feb 2010 05:43:43 +0000

Do I have to use the form generator? I’d like the option to use the old code that I was using previously & handing it off to my designer to build the design around the form. Now it just seems that I’m getting a ton of code, that I don’t really want?

By: TheNightOwl

TheNightOwl — Sat, 30 Jan 2010 05:44:56 +0000

Hi there

I, too, like the new optin form templates a LOT.

VERY nice work! =) And a great value-added feature.

Thank you.

—————————————

The code generated by the new forms is, however, throwing up W3 validation code errors such as this:

[start of error returned from http://validator.w3.org ]

# Line 115, Column 33: character “&” is the first character of a delimiter but occurred as data

if (document.compatMode && document.compatMode == ‘BackCompat’) {

This message may appear in several cases:

* You tried to include the “<” character in your page: you should escape it as “<”
* You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&”, which is always safe.
* Another possibility is that you forgot to close quotes in a previous tag.

# Error Line 115, Column 33: XML Parsing Error: xmlParseEntityRef: no name

if (document.compatMode && document.compatMode == ‘BackCompat’) {

[/end of error notes]

The problem seems to be occurring because of the “&&” part of the script code.

Any way of getting around this? I’d really like the homepages for my sites (which almost all include an Aweber optin form!) to actually be valid code. All my other code is fine. It’s just THIS that prevents my pages from being valid.

If you could look into it, that’d be greatly appreciated.

By: Don’t Let Your Opt-In Form Get Out Of Control

Don’t Let Your Opt-In Form Get Out Of Control — Wed, 30 Dec 2009 15:55:09 +0000

[...] creating your web form, think about the sign-up experience. You can add up to 25 fields with the new web form generator, but consider each addition [...]

By: Codrut @ Blog Post Ideas

Codrut @ Blog Post Ideas — Thu, 17 Dec 2009 10:04:24 +0000

I have a few suggestions

1. Add more templates to reflect the number next to each category.

2. Enable us to change the arrow color and adjust the opt-in window vertically too.

I hope this helps other users

By: Trigger a Lightbox Web Form With a Link or Button

Trigger a Lightbox Web Form With a Link or Button — Wed, 16 Dec 2009 19:48:59 +0000

[...] we recently re-did the Web Form Generator, the project’s lead developer, Dan, unsurfaced a neat option. By [...]

By: Bob

Bob — Thu, 10 Dec 2009 04:19:37 +0000

I look forward to trying it out as we proceed with our new design- like the audio thank you page idea too!

We’ll be trying both…