Ticket #520 (closed Defect: fixed)

Opened 7 years ago

Last modified 7 years ago

Topicmaps management oddities

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.2
Component: DeepaMehta Standard Distribution Version: 4.1.2
Keywords: Cc: dgf, Malte
Complexity: 3 Area:
Module: deepamehta-topicmaps

Description

Topicmaps plugin:

  • Topicmaps that are reloaded are not put in the topicmaps cache. That happens on login/logout. As a result that topicmap is not subject of global topic updates/deletes.
  • Once a topicmap is deleted the "was this the last topicmap?"-check is not accurate (as it is based on checking the topicmaps cache, not the DB). As a result another bogus "untitled" topicmap might be created.

Change History

comment:1 Changed 7 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 7 years ago by Jörg Richter

  • Status changed from accepted to closed
  • Resolution set to fixed

comment:3 Changed 7 years ago by Jörg Richter

Topicmaps: fix display of initial topicmap (#520).

When the initial Webclient URL contained a topic reference dm4c.do_select_topic() was called twice. At time of the first call the topicmap might not yet be displayed (due to asynchronicity) which under some circumstances caused problems.

Now dm4c.do_select_topic() is called only once and at a time when the topicmap is guaranteed to be displayed.

See #520.

comment:4 Changed 7 years ago by Jörg Richter

Topicmaps: fix display of initial topicmap (#520).

When the initial Webclient URL contained a topic reference dm4c.do_select_topic() was called twice. At time of the first call the topicmap might not yet be displayed (due to asynchronicity) which under some circumstances caused problems.

Now dm4c.do_select_topic() is called only once and at a time when the topicmap is guaranteed to be displayed.

See #520.

Note: See TracTickets for help on using tickets.