Project

General

Profile

Actions

bug #3737

closed

task #4338: [MASTER] Handle abbreviated title and protected cache correctly in TaxEditor

Protected caches for taxa and names behave inconsistent

Added by Andreas Müller over 8 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Highest
Assignee:
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:

30%

Estimated time:
Severity:
critical
Found in Version:

Description

Some name protected caches do not really work as expected here. We need to test the protected cache behaviour by hand.

  • rank is not colored but should

  • if both, name.titleCache and name.nameCache are protected, switching the titleCache to unprotected results in no coloring of all nameparts like genus, specific Epi, etc. This is not correct. Correct behavior shows when no protected cache exists and only nameCache is set to protected. This means that the coloring depends on the previous state which is unwanted. Coloring should always be computed from the current state so behavior is always the same independent of a previours state (a similar behavior has been observed for references: #4944)

Also for protected taxon.titleCache we may expect that the name fields will be colored (but maybe not organge) if the taxon titleCache is protected (see ideas for coloring strategy in #4944)

see also #4338, #3561, #4944, #9405


Related issues

Related to EDIT - bug #7484: Protected titleCache handling not correct in Reference detail viewClosedKatja Luther

Actions
Copied to EDIT - bug #9405: Fields set to irrelevant for cache should be set by state onlyClosedAndreas Müller

Actions
Actions #1

Updated by Andreas Müller over 8 years ago

  • Severity changed from normal to major
Actions #2

Updated by Andreas Müller over 8 years ago

  • Assignee changed from Andreas Müller to p.plitzner -
Actions #3

Updated by Andreas Müller over 8 years ago

  • Priority changed from Priority13 to Highest
  • Severity changed from major to critical
Actions #4

Updated by Cherian Mathew over 8 years ago

  • Target version deleted (TaxEditor CDM 3.3)
Actions #5

Updated by Andreas Kohlbecker about 8 years ago

  • Target version deleted ()

no release 3.3.1 of the taxeditor so I am moving all tickets to the next milestone 3.3.2

Actions #6

Updated by Patrick Plitzner almost 8 years ago

  • Keywords set to review2014-07-12
Actions #7

Updated by Andreas Müller almost 8 years ago

  • Assignee changed from p.plitzner - to Andreas Müller
Actions #8

Updated by Andreas Müller over 7 years ago

  • Target version deleted (TaxEditor RELEASE 3.3.7)
Actions #9

Updated by Andreas Müller about 7 years ago

  • Target version deleted ()
Actions #10

Updated by Andreas Müller almost 7 years ago

  • Target version deleted ()
Actions #11

Updated by Andreas Müller almost 7 years ago

  • Subject changed from Protected caches for taxa and names sometimes behave strange to Protected caches for taxa and names behave inconsistent
Actions #12

Updated by Andreas Müller almost 7 years ago

  • Assignee changed from Andreas Müller to k.luther -
  • Target version deleted (Release 3.7)
Actions #13

Updated by Andreas Müller over 5 years ago

  • Description updated (diff)
  • Target version changed from Unassigned CDM tickets to Release 4.5
Actions #14

Updated by Andreas Müller over 5 years ago

  • Target version changed from Release 4.5 to Release 4.6
Actions #15

Updated by Katja Luther over 5 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50
Actions #16

Updated by Katja Luther over 5 years ago

  • Assignee changed from Katja Luther to Andreas Müller

please review

Actions #17

Updated by Andreas Müller about 5 years ago

  • Private changed from Yes to No
Actions #18

Updated by Andreas Müller almost 4 years ago

  • Related to bug #7484: Protected titleCache handling not correct in Reference detail view added
Actions #19

Updated by Andreas Müller over 1 year ago

  • Copied to bug #9405: Fields set to irrelevant for cache should be set by state only added
Actions #20

Updated by Andreas Müller over 1 year ago

  • Status changed from Resolved to Closed
  • Assignee changed from Andreas Müller to Katja Luther
  • % Done changed from 50 to 30

The first issue is solved. The second was improved, however, it still sometimes works inconsistent meaning that the state of "irrelevance" of a field may depend on the previous state not on the generell state of the cache protection.

This is because setting "relevance" is always called in a given context and also the current code does not always reset fields from irrelevant to relevant if it should.

As this ticket was worked on long time ago I open a new ticket #9405 and close this one.

Actions #21

Updated by Andreas Müller over 1 year ago

  • Description updated (diff)
Actions

Also available in: Atom PDF