When The JS form elements get injected into the DOM when viewing in any version of IE (Ie6, Ie7) There are 2 "Add" buttons added to the page. Markup is as follows:

<div class="text-field">
  <div class="tag-widget">
    <ul class="inline-tags">
    </ul>
    <div class="tag-widget">
      <ul class="inline-tags">
      </ul>
      <input class="form-text form-autocomplete">
      <input class="form-button"> // This is the Add Button
    </div>
  <input class="form-button"> // This is the other Add Button
  </div>
</div>

Comments

OneTwoTait’s picture

OneTwoTait commented

subscribing... I had 12 "Add" buttons.

owahab’s picture

owahab commented
Status: Active » Postponed (maintainer needs more info)

Unable to reproduce.
Anyone can confirm this?

OneTwoTait’s picture

OneTwoTait commented

Setup a custom view that shows the full nodes. That's how I got a tonne of "Adds". To be more clear, it wasn't actually many add buttons. It was actually one loooong button with "Add" written on it many times.

Or, somebody can PM me and I'll give you access to the specific site to take a look.

Brigadier’s picture

Brigadier commented

I've seen this happen when the form appears more than once on the page, in Firefox 3, as described by taite11, above. Not sure what causes it but in my case I actually only wanted to display the form looking at the node as a single page.

Brigadier’s picture

Brigadier commented

This is related to #329579: Make possible to show more tagging form on a page. I think the patch there would fix this problem.

chaps2’s picture

chaps2 commented
Version: 6.x-1.x-dev » 6.x-2.x-dev
Status: Postponed (maintainer needs more info) » Fixed

I've seen the long Add button where I called community_tags_node_view($node, TRUE) in a theme preprocess_node function but where $node wasn't defined.

I've added a guard to community_tags_node_view in 2.x-dev so rather than see an incorrect CT form you see nothing.

I don't think the long Add button is the same problem as the one described in the original issue but it's been a while and is not reproducible with the information provided so marking as fixed.

Status: Fixed » Closed (fixed)

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