You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: