0010900: Using a Permalink without beeing loged in -> Error #200 - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0010900	mantisbt	other	public	2009-09-03 05:01	2009-10-07 14:19

Reporter	Funkman	Assigned To	dhx
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
OS	Win XP Pro	OS Version	SP3
Product Version	1.1.6
Target Version	1.2.0rc2	Fixed in Version	1.2.0rc2

Summary	0010900: Using a Permalink without beeing loged in -> Error #200
Description	Using a Permalink without beeing loged in is leading to Application error #200 (missing parameter "hide_status_id") after the login form. The link works fine if you are logged in . Permalink: http://xxx/mantis/search.php?project_id=0&resolution_id=30&sticky_issues=on&sortby=last_updated&dir=DESC&hide_status_id=90 At the login page: http://xxx/mantis/login_page.php?return=%2Fmantis%2Fsearch.php%3Fproject_id%3D0%26resolution_id%3D30%26sticky_issues%3Don%26sortby%3Dlast_updated%26dir%3DDESC%26hide_status_id%3D90
Steps To Reproduce	create a permalink log off click the link log in -> error
Tags	No tags attached.
Attached Files	Error#200.png (5,639 bytes) Error#200.png (5,639 bytes)

MantisBT: master-1.2.x 2417de5c 2009-09-04 06:56 dhx Details Diff	Fix 0010900: Permalink should not require hide_status_id field If a permalink is created within a hide_status_id field, the user currently sees an error message. We should just use the default hide_status_id value from the configuration file if no value is provided via the permalink.	Affected Issues 0010900
	mod - search.php	Diff File
MantisBT: master 0353a9b3 2009-09-04 06:56 dhx Details Diff	Fix 0010900: Permalink should not require hide_status_id field If a permalink is created within a hide_status_id field, the user currently sees an error message. We should just use the default hide_status_id value from the configuration file if no value is provided via the permalink.	Affected Issues 0010900
	mod - search.php	Diff File

dhx 2009-09-04 06:36 reporter ~0022859	Reproducible in the current git master. Thanks for reporting this bug! I'll try and fix it :)

dhx 2009-09-04 06:59 reporter ~0022860	Thanks for the bug report. I should now have this fixed in the 1.2.x and 1.3.x branches ready for the next release.