Issue Number | 241 |
---|---|
Summary | [Full Citation] "Conflicting Hash" Error Message on DEV |
Created | 2014-08-19 18:45:38 |
Issue Type | Bug |
Submitted By | Juthe, Robin (NIH/NCI) [E] |
Assigned To | |
Status | Closed |
Resolved | 2023-12-14 11:45:54 |
Resolution | Won't Fix |
Path | /home/bkline/backups/jira/oceebms/issue.136634 |
I just received an error message on the full citation page when, in the context of testing on DEV, I added the Cancer Genetics Board to the following citation: PMID: 22846142
I will post a screenshot.
Did Erika add this to the current iteration?
No, I did. I came across it when testing on DEV so I figured it was probably related to another ticket in this iteration, but I don't know which one. I haven't seen this problem on prod.
I'm pretty sure this is not caused by the work we're doing on 3.1 (I can reproduce the problem on QA).
Moved to the backlog and upped the priority since the error is on DEV and QA, and will likely be on prod with release 3.0. Maybe we can put this into a patch.
I suspect this may be on PROD already, but I'm reluctant to test there myself. I was able to reproduce it on QA by opening up the block for one of the existing boards, then adding a new one.
Moved to the backlog ...
I had already started injecting some debugging code into citations.inc before I saw that. I'm about to do some testing on DEV which may disrupt things briefly (I hope not, but thought it best to warn you of the possibility). If I'm not able to figure out easily what he's doing with this code, I'll back out the changes I just made.
I was able to reproduce it on QA by opening up the block for one of the existing boards, then adding a new one.
There's one more step in my repro procedure. Here's the full repro instructions:
Bring up "Full Citation" page for an article
Click on an existing board name to expand its block
Click on "Add New Decision" under that block
Click the pencil next to "EDITORIAL BOARD(S)"
Pick a board and continue
Pick a topic and continue
Pick a cycle
Enter a comment
Click Save
Step 3 (clicking "Add New Decision") may not be necessary to reproduce the behavior, but I didn't get the error messages without step 2.
From Bob:
We've given this 13 story points but that might not be enough. However, it seems to me that if it goes beyond the level of effort estimated, it might be more sensible to spend our time on more useful tasks, and fall back on instructions for how to avoid this edge case situation.
It was a toss-up between "Fixed" and "Won't Fix" for this ticket, but the behavior reported by this ticket was specific to the Drupal 7 version of the EBMS, so this ticket can be closed.
File Name | Posted | User |
---|---|---|
screenshot-1.jpg | 2014-08-19 18:46:36 |
Elapsed: 0:00:00.000601