Hi,

The 2.x version of collapse text puts the text in a form. However, when the text was already supposed to go in a form in the first place, this causes a nested form. Google Chrome and Firefox just ignore the inner form, but IE can't handle it.

I don't know how to fix this though.

Comments

pukku’s picture

pukku commented
Assigned: Unassigned » pukku
Status: Active » Fixed

Hi! I just put up a new release (6.x-2.5) which allows you to disable the form in two ways.

First, there is now a setting for the entire input format.

Second, you can now add a tag '[collapse options form="noform"]' to the start of a particular text field to prevent a form from being added to that block.

HylkeVDS’s picture

HylkeVDS commented

Great!
I'll test it first thing on Monday.

HylkeVDS’s picture

HylkeVDS commented

Yep, it works like a charm now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

nhoeller’s picture

nhoeller commented

I think I may have tripped over this problem. I have a page in which there are multiple form fields (PayPal Subscribe) buttons. The second and subsequent form fields are inside collapse_text blocks. Everything worked fine in collapse_text 1.1 but after upgrading to version 2.7 the target for the first subscribe button pointed back to the Drupal page rather than PayPal.

After some head-scratching, I noticed that my page content was wrapped with:

<div class="content clear-block">
    <form action="/node/606/"  accept-charset="UTF-8" method="post" id="collapse-text-dynamic-form-number-1">
<div><div class="collapse-text-text collapsed-text">

and 

</div></form>

where /node/606/ was the page that contained the collapsed text and forms.

Assuming this is a the same problem as described above, can someone point me to the documentation for implementing the two ways of disabling the form mentioned in http://drupal.org/node/1105248#comment-4261894 ?
Thanks, Norbert