php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #70349 Reopen 70336 or explain how it is not a bug
Submitted: 2015-08-24 22:28 UTC Modified: 2015-08-25 04:42 UTC
From: teo8976 at gmail dot com Assigned: kalle (profile)
Status: Closed Package: Website problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: teo8976 at gmail dot com
New email:
PHP Version: OS:

Further comment on this bug is unnecessary.

 

 [2015-08-24 22:28 UTC] teo8976 at gmail dot com 
Description:
------------
https://bugs.php.net/bug.php?id=70336
https://bugs.php.net/bug.php?id=70347

For the second time, not only closed without explaining why it is not a bug, but closed to comments so I cannot reply.

1) Explain why you consider an antispam filter based merely on keywords (and especially one that does DOES NOT GIVE A PROPER ERROR MESSAGE when rejecting comments) to be an acceptable antispam system, as opposed to requiring people to register and login to report bugs, as every other bugtracker does.

2) Stop locking bugs to comments.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2015-08-25 04:42 UTC] kalle@php.net
-Status: Open +Status: Closed -Assigned To: +Assigned To: kalle -Block user comment: No +Block user comment: Yes
 [2015-08-25 04:42 UTC] kalle@php.net 
Really, ...

As I said in the previous, use the mailing lists for such discussions, not the bug tracker, neither am I interested in recieving personal mails about this, the webmaster list[1], deals with such issues.

http://php.net/mailing-lists.php
 
PHP Copyright © 2001-2026 The PHP Group
All rights reserved. 		Last updated: Mon Jun 01 01:00:02 2026 UTC