Issue 35 in gref-mvz: omnipresent reference set
codesite...@google.com
http://code.google.com/p/gref-mvz/issues/detail?id=35
New issue report by 7qaxi...@earthlink.net:
What steps will reproduce the problem?
After completely saving a page which had 5 reference sets on it, I hit the
tab at the top of the page (53) for the next page (page 54). When I got to
the next page, three of the five reference sets were carried onto the new
page, and I have been unable to delete them.
What is the expected output? What do you see instead?
I expect to not have reference sets carried onto the next page unless I hit
"continue on the next page. I also expect to be able to delete them if
they are not necessary. Neither of these things happen.
Attachments:
0 bytes
Issue attributes:
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
http://code.google.com/p/gref-mvz/issues/detail?id=35
Comment #1 by 7qaxi...@earthlink.net:
> I wanted to add a couple more details to the omnipresent ref set issue, because
I just got a couple more omni-sets (beginning on v1319_s1_p078.jpg). It seems that
when there are multiple reference sets on one page, an extra ref set appears that
was not created by the user, and this set is un-deletable. As well, when one of
these ref-sets that I appears, one or more reference sets that come after it become
omnipresent as well. In both of the last two occurrences, there have been multiple
reference sets on one page, and some of these reference sets include the same date,
but different collecting events, because they occur at different localities.