Captcha integration

We ran into a similar problem using Mollom as the captcha provider.

In forward.module, we changed the line

$form['message']['submit'] = array(

to

$form['submit'] = array(

It may work for you too. It takes the submit button out of the field group, but it makes the module more compatible with captcha providers.

Patrick

I had tried that previously, but it causes it's own problems. If you set forward to display an in inline form on pages rather than a link, the form appears as collapsed by default. The problem with this suggestion is that it'd cause the submit button to appear by itself even when the fieldset is not expanded, leading to confusion. I'm certainly open to recommendations, but I think this is more an issue of the CAPTCHA module not adequately traversing the form tree to find the submit button.

The CAPTCHA is correctly placed automatically with CAPTCHA 6.x-2.x-dev. They heavily refactored the code so it now avoids problems like this. They should be stable soon and there's no easy work around for the 6.x-1.x version, so I'm marking this as won't fix.

Re: #1, the problem with that is that when Forward appears as a form embedded in the node page rather than a link to a separate page, if the fieldset is collapsed, the submit button will still be visible outside the fieldset.

Tonight's DEV release detects whether Forward is in link or collapsible form mode, and handles the submit button appropriately for both cases. This allows for optimal captcha placement in link mode, while keeping the submit button within the fieldset in form mode.