Hi, i had the same problem and i could fix it doing that papaSnowShoveler told here. Is necessary first remove all the dropppables before make the change of the content where will whow the new dropabbles. Remember that each time you remove a droppable, change the lenght of the droppables collection.
On Jan 15, 7:15 pm, "papaSnowShoveler" <[EMAIL PROTECTED]> wrote: > Ah Ha!! > > Chris - I thought more about what you said about unregistering the > droppables. What I did was add a line in the .rjs that gets called > after the controller action runs its course. I added a remove > statement to remove the divs that contained the drop receiving > elements. For example, the id of one of the divs with the drop > receiving elements was "planned_goals0", so I just added > > page.remove "planned_goals0" > > prior to the page.replace_html statement and it works!! So, by using > the page.remove statement, I "unregister all the droppables prior to > removing them" as you had said to do. > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
