0006612: BUG_LIST_COOKIE seems to prevent new bugs from being seen - MantisBT - Signup temporarily disabled due to spam

ID	Project	Category	View Status	Date Submitted	Last Update

0006612	mantisbt	filters	public	2006-01-19 13:38	2006-02-04 05:44

Reporter	mlovell	Assigned To	thraxisp
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	1.0.0rc5

Summary	0006612: BUG_LIST_COOKIE seems to prevent new bugs from being seen
Description	As users enter new issues, I have noticed that my "View Issues" and "My View" page is NOT including the new issues. I think the fault is that BUG_LIST_COOKIE is causing the new issues to be filtered out.
Steps To Reproduce	Have a web browser open to "View Issues". Have another user, using a different browser, report a new issue. Then, refresh the "View Issues" page. What I am seeing is that the newly reported issue is not seen in that list.
Tags	No tags attached.

mlovell 2006-01-19 14:08 reporter ~0011962	The issue appears more nuanced than my original description. Allow me to explain what I just saw... I have one firefox brower open under Windows, pointing at our new database. I have another browser open under Linux, also open to the same database. The Linux browser had just been used to enter a new issue (#6). After I entered that issue, I got redirected to the "View Issues" page, which very happily showed me issues 1-4 and 6. For some reason, Issue 0000005 was not being shown. The BUG_LIST_COOKIE for the browser has the contents: 6%2C3%2C4%2C2%2C1 In the meantime, another user has entered issue 0000007. Hitting refresh on the View Issues page on the windows browser, issue 0000007 showed up just fine. Refreshing the Linux browser (also on the View Issues page), I now get issues 1-4, 6, and 7. Thus, it seems as though the issue I filed in the Linux browser keeps getting filtered out. Looking at various cookie contents again, MANTIS_BUG_LIST_COOKIE now has the value: 7%2C6%2C3%2C4%2C2%2C1 I don't have any filter explicitly set, and the Assigned To filter current says "any". I mention this since issue 0000005 is "new" with no owner, and this whole thing might have been stupid user error. Even if I set the Assigned To filter to [none], issue 0000005 is not appearing, though. It's like issue 0000005 has somehow slighted the cookie and is being forever excluded. :)

mlovell 2006-01-19 15:36 reporter ~0011965	This may end up being a semi-stupid user error...The cookie MANTIS_BUG_LIST_COOKIE may just be showing the effects of interacting Mantis installations. I have two installations of Mantis on the same box, one deployed and the other for testing (they reference separate databases). On the test deployment, I have a couple of saved filters set up. I believe this resulted in MANTIS_VIEW_ALL_COOKIE getting set (to a value of 2). There are, as of this writing, no saved filters setup for the official Mantis deployment. I'll delete the VIEW_ALL_COOKIE to see if it helps at all.

thraxisp 2006-01-19 16:02 reporter ~0011969	You can set a cookie prefix ($g_cookie_prefix) or cookie path ($g_cookie_path) to differentiate the installations.

mlovell 2006-01-19 16:23 reporter ~0011974	I have followed the recommendation in the last note and set $g_cookie_prefix to be different for the two installations. I have only done limited experimentation thus far, but have seen no further issues. I suspect this issue can be marked as resolved. Thanks!

thraxisp 2006-01-19 22:00 reporter ~0011977	Interaction between two mantis installations.