bug #7850
closedFurther problems with term editor
100%
Description
After fixing LIE in #7827 there are further issues with term editor.
- Sometimes when opening or working with term editor during EagerLoading an not server not available comes (though the server responds but may work load is to much) (#7827#note-8)
- Moving e.g. a NamedArea somewhere else (not same parent) does not remove it from the old position in tree view, when trying to save a multiple representations exception shows up
====
Copy from #7827#note-6: The Termeditor has to be refactored as still all term operation are done on the editor side and should be moved into the cdmlib service layer.
Files
Related issues
Updated by Andreas Müller almost 6 years ago
- % Done changed from 0 to 20
Added commits from #727 related to this ticket to the ticket.
Updated by Andreas Müller almost 6 years ago
AM:
Gibts für die MultiRep bzw. das Term Verschiebeproblem schon ein Ticket? Wenn ich ein Area verschiebe wird er derzeit an der alten Stelle nicht im Baum entfernt. Wenn ich dann save kommt es regelmäßig zu MultiRep Exception. Das müsste da rein. Getestet mit test.E+M
(this happened after the above commits were pushed and nightly were build)
Updated by Andreas Müller almost 6 years ago
- Related to bug #7851: [DISCUSS] How to handle connection issues during tasks added
Updated by Andreas Müller almost 6 years ago
- Copied from bug #7827: LazyInitializationException when saving term editor (named areas) added
Updated by Patrick Plitzner almost 6 years ago
- Status changed from New to Resolved
- Assignee changed from Patrick Plitzner to Andreas Müller
- % Done changed from 20 to 50
Updated by Andreas Müller almost 6 years ago
- File picture357-1.png picture357-1.png added
still not yet fully fixed
Updated by Andreas Müller almost 6 years ago
Next time when opening term editor Belgium was completely gone, though in the DB everything was ok (vocabulary, parent_id and orderindex correctly set).
After restarting the TaxEditor everything at the correct place again.
Updated by Andreas Müller almost 6 years ago
The problem always occurs during the second move. Moving first time works correctly.
Updated by Andreas Müller almost 6 years ago
- Assignee changed from Andreas Müller to Patrick Plitzner
Maybe one problem is the order index. After moving the area gets the highest order index though it is placed as child somewhere in the middle (child of Great Britain in my test).
By the way this time I could save the data so the area was displayed 2x.
Maybe we should stop this here.
Term structure urgently needs to be refactored and will be done soon. We should fix the hierarchie issues of the term editor then (maybe they are automatically fixed then)
Updated by Patrick Plitzner over 5 years ago
- Assignee changed from Patrick Plitzner to Andreas Müller
@Andreas M.: Can you please check if this is still an issue?
Updated by Andreas Müller over 5 years ago
- Target version changed from Release 5.4 to Release 5.5
Updated by Andreas Müller over 5 years ago
- Related to feature request #7887: Use DTOs in term editor added
Updated by Andreas Müller over 5 years ago
Andreas Müller wrote:
Copy from #7827#note-6: The Termeditor has to be refactored as still all term operation are done on the editor side and should be moved into the cdmlib service layer.
I think this is better handled in #7887. However, it is not recommended to run these operations only on server side as this requires immedate save which is against the general TaxEditor philosophy.
Updated by Andreas Müller over 5 years ago
- Status changed from Resolved to Duplicate
- Assignee changed from Andreas Müller to Patrick Plitzner
Updated by Andreas Müller over 5 years ago
- Related to deleted (feature request #7887: Use DTOs in term editor)
Updated by Andreas Müller over 5 years ago
- Is duplicate of feature request #7887: Use DTOs in term editor added