View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000795 | XMB1 | Bugs | public | 2025-06-14 14:36 | 2025-06-14 14:48 |
| Reporter | flushedpancake | Assigned To | |||
| Priority | low | Severity | trivial | Reproducibility | sometimes |
| Status | new | Resolution | open | ||
| Summary | 0000795: The CAPTCHA cannot be disabled if php-gd is not installed. | ||||
| Description | There is a functional check to see if the GD extension is installed or not, since it blocks you from editing the settings in the admin panel if GD is disabled. However, on a page where the CAPTCHA runs, an error occurs that blocks the page from rendering. [Wed Jun 11 21:25:31.980642 2025] [php:error] [pid 2930:tid 2930] [client 127.0.0.1:33038] PHP Fatal error: Uncaught RuntimeException: XMB captcha is enabled but not working. in /srv/www/htdocs/member.php:408\nStack trace:\n#0 {main}\n thrown in /srv/www/htdocs/member.php on line 408, referer: http://localhost/member.php?action=reg | ||||
| Additional Information | The XMB CAPTCHA is about as effective at defeating spambots as the Maginot Line was at protecting France from being invaded during WW2, so it's debatable whether it's even worth bothering to fix it or not... | ||||
| Tags | No tags attached. | ||||
| MySQL Version | |||||
| PHP Version | |||||
| Web Server | |||||
| Browser | |||||
| Flags | |||||
| Original Reporter | |||||
| SVN Revision | |||||
| Git Commit | |||||
|
|
(Personally, I'd advocate for completely nuking the internal CAPTCHA system for the exact reason mentioned in the additional information box. There's a few methods that exist that don't involve CAPTCHA to combat bots, though most of them have been rendered obsolete thanks to advanced machine-learning...) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-14 14:36 | flushedpancake | New Issue | |
| 2025-06-14 14:48 | flushedpancake | Note Added: 0000565 |
