Bug #66653 [Com]: "Incorrect CAPTCHA" trying to file or comment a bug report

Edit report at https://bugs.php.net/bug.php?id=66653&edit=1 ID: 66653 Comment by: chealer at gmail dot com Reported by: chealer at gmail dot com Summary: "Incorrect CAPTCHA" trying to file or comment a bug report Status: Assigned Type: Bug Package: Website problem PHP Version: Irrelevant Assigned To: peehaa Block user comment: N Private report: N New Comment: I am under the impression that this has been fixed. Previous Comments: ------------------------------------------------------------------------ [2020-01-03 07:57:05] cmb@php.net Related To: Bug #79057 ------------------------------------------------------------------------ [2019-06-01 23:54:08] chealer at gmail dot com Thank you petk. Your description brings me as many questions as it answers though. I suggest you explain your decision on your blog, or post an explanation to a PHP mailing list. Thank you peehaa ------------------------------------------------------------------------ [2019-06-01 17:57:48] peehaa@php.net I will have a look in the (relatively) short term to see if I can repro it too and can implement a quick fix for it where I find the problem. ------------------------------------------------------------------------ [2019-05-31 14:42:46] petk@php.net > There is no need justify unassigning a ticket, but if you do, I would appreciate a deeper > explanation (perhaps with a link). Hello, there isn't any particular link to the exact problem here actually or steps to reproduce this. This is a thing that happens over several periods of time and loads of discussions so one can make an impression of how things are being done here, what kind of practices are used to fix and maintain (or not maintain) certain parts of the websites, and mostly the too expensive burden being present to fix some existing issue. You can trust me, that I've invested a lot, and tried many things to get things moving forward here. Mostly it's the problem of what kind of practices and requirements run these projects and if these can't be changed neither moved forward into different and better ways then from my point of view this app can't be moved forward. This app is not a tutorial how to do things in web. We just need a fully working environment to report and have an overview of the bugs of PHP software... Now, if we need to discuss if even using Composer is a good thing or not, or if some weird mixed, customized unsynced coding style is used in multiple different files and syncing that into a common coding style for particular project is a problem of a level that causes arguments and issues, or that some dependency is a problem then even if there would be a discussion happening we can already see that it's happening way to slow to something to be done. I've opened several topics that would be good to discuss but no responses. I couldn't move forward since my changes started causing all kinds of conflicts etc etc and here we are now. I'm really not into some "fun" challenges that are mostly brain damage so I simply move on to something else instead where things can go forward more smoothly. I'm not saying that someone else couldn't fix this. Maybe they will see a way with this messy coding way to improve this app and they can do it... But not me, sorry :) I have no time for this anymore. Way too much quality things have been already proposed and not welcomed so, let's just move on and we're good to go to the next things on our todo lists. Cheers. ------------------------------------------------------------------------ [2019-05-29 02:43:44] chealer at gmail dot com Thank you petk There is no need justify unassigning a ticket, but if you do, I would appreciate a deeper explanation (perhaps with a link). ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=66653 -- Edit this bug report at https://bugs.php.net/bug.php?id=66653&edit=1