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 10 years ago.
Updated about 3 years ago.
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
- Severity changed from normal to major
- Assignee changed from Andreas Müller to p.plitzner -
- Priority changed from Priority13 to Highest
- Severity changed from major to critical
- Target version deleted (
TaxEditor CDM 3.3)
- Target version deleted ()
no release 3.3.1 of the taxeditor so I am moving all tickets to the next milestone 3.3.2
- Keywords set to review2014-07-12
- Assignee changed from p.plitzner - to Andreas Müller
- Target version deleted (
TaxEditor RELEASE 3.3.7)
- Target version deleted ()
- Target version deleted ()
- Subject changed from Protected caches for taxa and names sometimes behave strange to Protected caches for taxa and names behave inconsistent
- Assignee changed from Andreas Müller to k.luther -
- Target version deleted (
Release 3.7)
- Description updated (diff)
- Target version changed from Unassigned CDM tickets to Release 4.5
- Target version changed from Release 4.5 to Release 4.6
- Status changed from New to Resolved
- % Done changed from 0 to 50
- Assignee changed from Katja Luther to Andreas Müller
- Private changed from Yes to No
- Related to bug #7484: Protected titleCache handling not correct in Reference detail view added
- Copied to bug #9405: Fields set to irrelevant for cache should be set by state only added
- 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.
- Description updated (diff)
Also available in: Atom
PDF