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
Try to create an association to a topic of a type that's organized in a
hierarchy. Say you have a topic type "concept" that's organized into a
taxonomy. And you have a topic type "article" which has an "is-about" relation
with "concept". Now go to an article, and open the browse dialog. Pick the
topic type "concept".
The top level of the concept hierarchy will be displayed. The "expand all" and
"collapse all" buttons will work. The + and - buttons, however, have no effect
at all. There are no errors in the error console, but pressing the buttons does
nothing.
This is consistent across different topic maps, different servers, and
different browsers. We assume the problem originated with Ontopia 5.1.0.
Original issue reported on code.google.com by lar...@gmail.com on 20 Aug 2010 at 1:54
The text was updated successfully, but these errors were encountered:
I've tried to fix this a couple of times, but with no luck so far. This is not
really a show stopper as expand all will work, but I agree that it is a little
inconvenient.
I've tried upgrading and downgrading Wicket with no luck.
The AJAX interaction seems to work fine, but the problem is that the AJAX reply
returns the did not expand the selected tree node. So for some reason the
serverside call was not able to expand it.
I'll give this another look this weekend.
Original comment by indiapaleale@gmail.com on 24 Sep 2010 at 8:23
I did not quite understand the error description above, but we at NRK Skole
cross our fingers and hope this could be fixed! The expanded subject tree in
our project is really huge, and therefore tagging a topic to a subject is
therefore very combersome when having to scan the whole expanded tree.
Original comment by pmlov...@gmail.com on 29 Sep 2010 at 12:01
Fixed by revision 1389. No longer using LoadableDetachableModel to hold the
tree model, but instead using a standard Model object. Note that this relies on
the serializability of the tree model.
Not quite sure whether this fix introduces any other issue. Please test. :)
Original comment by indiapaleale@gmail.com on 7 Oct 2010 at 5:47
Original issue reported on code.google.com by
lar...@gmail.com
on 20 Aug 2010 at 1:54The text was updated successfully, but these errors were encountered: