I have the latest version of the git repository installed with the patch from #43 http://drupal.org/node/1309632#comment-6694660. The widget does not work correctly: I can perform only one action like search, add o remove an item or use the pager. After that first action, any other action does not have any effect. So when I try to search a second time or add a second item, or use the pager the throbber is shown but, after that, nothing happens: Neither the new search results are shown, nor a item is added or removed... I don't get any error message neither PHP, nor Javascript.
I suppose the problem is, that the Ajax loaded content is not pushed correctly in the HTML tree. Maybe this has to do something with some classes that are set after the first AJAX event. When I reload the whole widget I can perform another action.
Does anybody else have that problem? Is this a known issue?

Thanks to all who worked for this great module!

Comments

gunwald’s picture

gunwald commented

The problem has to do something with the ids of the HTML elements that change after the first AJAX reload: For example, at first the field element of the widget looks like this

<fieldset class="entityreference-view-widget form-wrapper" id="edit-field-pois-und"></fieldset>

After the first AJAX action it changes in something like this:

<fieldset class="entityreference-view-widget form-wrapper" id="edit-field-pois-und--2"></fieldset>

That means, that the id changes and maybe this id is used to select the element where to push the new AJAX loaded content in.

When I manually change the id (using firebug or something) the AJAX results are shown correctly.

orbistertius’s picture

orbistertius commented

Same Here, but I am working with the last stable version. With the first ajax load the views disapears.

adrien.felipe’s picture

adrien.felipe commented

I was having the same issue. What I did is to force the ID in my callback function.

  $form['message']['#id'] = 'edit-message';
  return $form['message'];

But it forced me to use only one single item for the ajax wrapper, to avoid forcing all IDs

Drupa1ish’s picture

Drupa1ish commented

#3 works for me. Thanks!

aze2010’s picture

aze2010 commented

subscribing.

Where do i have to add the code from #3?

dude74’s picture

dude74 commented

Idem, where in #3 ?
Module can't work (dev + alpha2) in current state with such an issue.
Frustrating, could be great module...

bojanz’s picture

bojanz commented
Issue summary: View changes
Status: Needs work » Closed (won't fix)

The 1.x branch isn't maintained anymore due to a very problematic codebase, as also evidenced by this issue.
The 2.x branch is a complete rewrite that aimed to solve all known problems.
Please switch to the 2.x branch and open new issues for any problems you encounter.

Thank you for your patience.