Bug #17748 Updated: bug search form doesn't stripslashes() on terms when no results found
| From: | sander@php.net | Date: | Thu, 13 Jun 2002 19:02:26 +0000 |
| Subject: | Bug #17748 Updated: bug search form doesn't stripslashes() on terms when no results found | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-10823@lists.php.net to get a copy of this message | ||
ID: 17748
Updated by: sander@php.net
Reported By: pgl@instinct.org
-Status: Open
+Status: Closed
Bug Type: Website problem
PHP Version: 4.2.1
New Comment:
This bug has been fixed in CVS. You can grab a snapshot of the
CVS version at http://snaps.php.net/. In case this was a
documentation
problem, the fix will show up soon at http://www.php.net/manual/.
In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites.
Thank you for the report, and for helping us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2002-06-13 13:06:17] pgl@instinct.org
On this page:
http://bugs.php.net/search.php
If no results are found and the search terms contain quotes, the values
in the input fields appear backslashed.
eg:
http://bugs.php.net/search.php?cmd=display&search_for=%22not%20a%20bug%22
Basically, someone forgot to stripslashes().
regards,
Peter Lowe
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=17748&edit=1