Conflict with autocomplete form field

Sorry for my (so) late response

The script used in this module sometimes conflicts with AJAX/AHAH calls
Autocomplete is one of them.

If have a running page with the above error I would be happy to have a look
and find the best way to solve it.

In the last release I added some options to excluded problematic fields,
As a temporary solution you can disable the module for a certain form.

I just came across this bug myself and may be able to shed some more light on it.

I have a content type which includes a taxonomy vocabulary that uses an auto-complete field. When creating a new node, if I type something in this "Tags" field it pops up a list of suggestions below the field. At this point I must select one of these suggestions, tab out of the field, or somehow remove focus from that field before I submit the form. If I fail to do so and the suggestion box is still open when I click the "Save" button, then as Ricardo indicated, the submit buttons will hide, but the form will not actually submit. This is a dangerous bug as it can easily cause data loss and auto-complete fields are very common on forms. In fact, I see two of them on this very page.

In case it matters, I'm using Firefox 3.5.5, running on Mac OS X 10.6.3.

Okay, I reproduced it in my test env,
This issue is another conflict between ajax fields and the script used by the module

I also found out that if you use ENTER key, the form reloads with all the data inside so there is no data lose.

I already tried to solve this conflict but there is no easy way
So I suggest as workaround for now to disable the script for this form (by page or by form id)
And I'll continue to look for a way to solve the conflict.

This means many people, myself included, will be unable to use this on any node add/edit pages, which drastically decreases the usefulness of this module. Any help resolving the issue would be greatly appreciated.

I agree, this is a big usability issue, conflict with AJAX
Unfortunately I couldn't find a solution yet :-(
I'm still looking for one..

subscribing.

From what I can see the current approach tries to hide/disable all submit buttons except those that are specifically excluded. I wonder if a more straightforward approach (from the point of view of avoiding conflicts) might be to only hide/disable certain buttons, e.g. Save, Preview, Delete, i.e. have the module work in inclusion mode rather than exclusion mode. Support for selected contrib modules could also be added in principle, e.g. diff.module --> Preview changes button.

Might also need to force the focus to change to the submit button or something. Hmm, on second thoughts I'm not convinced these suggestions will help much but I'll post them anyway in case there is some merit in them.

It is a good idea to avoid conflicts,
But I think that the current approach works for most site-configurations out of the box without conflicts
Changing the approach will require more steps for this module to work

subscribing

subscribing, this module turns out to be unusable for me, some people have complained about their content not getting submitted.

It's a pity, because an hour after disabling it, the double posts have returned :(

Any progress on this issue?

Subscribing -- This module wonderfully solves a problem we were having with double-clickers, but is of limited use due to its incompatibility with Autocomplete.

I have the same issue, even after changing to "submit on click" only, without the "ENTER" button. I'll probably have to disable the module because it's frustrating for users when they have filled out a long form and can't submit it.
Great module, otherwise ...

Attached patch fix conflict with autocomplete such as taxonomy autocomplete.

Thanks for submitting this issue.

The 6.x branch of this module is not supported. This issue was filed against the 6.x version so I'm closing it because it doesn't seem relevant to the 7.x version.

If the issue is relevant for the 7.x version: I apologize for closing it. Can you please reopen it and adjust the version number?