Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict with plone.formwidget.autocomplete #18

Open
jperals opened this issue Oct 2, 2012 · 3 comments
Open

Conflict with plone.formwidget.autocomplete #18

jperals opened this issue Oct 2, 2012 · 3 comments
Labels

Comments

@jperals
Copy link

jperals commented Oct 2, 2012

After installing collective.z3cform.widgets, the autocomplete functionality of all widgets that use plone.formwidget.autocomplete is lost.

This seems to be because plone.formwidget.autocomplete uses the jQuery Autocomplete widget, while collective.z3cform.widgets uses jQuery UI's Autocomplete widget, and the latter is overriding the former. See http://plone.293351.n2.nabble.com/plone-formwidget-autocomplete-and-collective-js-jqueryui-td6618231.html for another description of this issue.

Just deactivating jQuery Autocomplete from @@jqueryui-plugins-controlpanel makes plone.formwidget.autocomplete work again, but then the autocomplete functionality of collective.z3cform.widgets is obviously lost --so, you have to choose between having autocomplete in one kind of widgets or the other.

There has been some discussion about integrating jQuery UI in Plone, which could include the jQuery UI Autocomplete widget (https://dev.plone.org/ticket/12350), but this seems just a rough idea so far -- and anyway, plone.formwidget.autocomplete would then have to be modified. So unless there is a good reason to use the jQuery UI Autocomplete widget, I would stick to the jQuery Autocomplete plugin.

@hvelarde
Copy link
Member

hvelarde commented Oct 3, 2012

thanks! just for the records, which widget you were trying to use? I was planning to release some of them as separate packages as they seem to be mature enough.

@flecox please take a look on this when you have time.

@jperals
Copy link
Author

jperals commented Oct 4, 2012

Thanks for the quick response. Just a further notice: after writing this issue, I saw this: collective/collective.js.jqueryui#1
According to that, the jQuery Autocomplete plugin should be seen as deprectaed being its successor the jQuery UI Autocomplete plugin, thus "this is plone.formwidget.autocomplete that should be updated" to use jQuery UI Autocomplete. So I'm not sure now what would be better --to fix collective.z3cform.widgets so that autocomplete works right now for all widgets, but then it may have to be changed again in the future, or help fixing plone.formwidget.autocomplete so that everything works sooner with jQuery UI Autocomplete.

As a last note, this may be a useful resource for migrating from one plugin to the other (from the old to the new, but maybe also vice versa if needed): http://www.learningjquery.com/2010/06/autocomplete-migration-guide

I am using EnhancedTextLinesFieldWidget and TokenInputFieldWidget.

@hvelarde
Copy link
Member

hvelarde commented Jan 9, 2013

sorry, but I haven't time to take a look on this until now; I think we are going to update the widget at some point but I'm not sure when.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants