Bugs
Jump to navigation
Jump to search
File bugs here, move them to Changelog when they are fixed. Use the following format:
| ID | YYYY-MM-DD-number |
|---|---|
| Status | NEW |
| Description | Some description |
| ID | 2015-06-19-01 |
|---|---|
| Status | NEW |
| Description | if admin.pl is trying to replace package path/to/foo.zip with package path/to/foo.lha, it forgets to delete the old database entry so we end up with database entries for foo.zip and foo.lha (cg) |
| ID | 2007-02-18-01 |
|---|---|
| Status | WONTFIX |
| Description | ADT server is not running yet. It also needs to be added to server startup (cg) |
| ID | 2007-02-15-01 |
|---|---|
| Status | NEW |
| Description | If an uploaded package has a size of 0 bytes, the email offered for flaming is that of the *previously* moderated package. This only happens under certain circumstances, probably if the faulty package has no uploader email of its own (cg) |
| ID | 2007-02-07-03 |
|---|---|
| Status | NEW |
| Description | AmFTP doesn't display RECENT files when in ADT mode (cg) |
| ID | 2006-09-01-01 |
|---|---|
| Status | NEW |
| Description | admin.php: If you're not in doc/ move_package fails to change the value of the type: field in the readme, because there's an fopen() call which uses a relative path instead of an absolute path (cg) |
| ID | 2006-08-12-01 |
|---|---|
| Status | NEW |
| Description | If a readme contains backslashes (in the body, not in one of the header fields - didn't check header fields), these get stripped from *both* the actual readme *and* the database entry. Enclosing the string containing backslashes in double quotes helps the backslashes to actually reach the database entry, but they're still getting stripped from the actual readme. An example would be the windows path in comm/www/firefox_searchplugin.zip (cg) |
