View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0026581 | mantisbt | custom fields | public | 2020-01-08 16:06 | 2020-03-10 17:23 |
Reporter | rogueresearch | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 2.21.1 | ||||
Summary | 0026581: Editing custom "bug_print_page_fields" gives "APPLICATION ERROR #100" | ||||
Description |
Result:
If I understand 0022247 correctly, "bug_print_page_fields" was removed? If so:
| ||||
Tags | No tags attached. | ||||
As a side note: |
|
I've just restored the 2.21.1 admin folder on my prod server and ran admin/check/index.php. It doesn't say anything about |
|
As you see in the screen shot, you should get this warning. Maybe you see some other errors when running the script. |
|
Independant from that, I am not able to reproduce the original issue in my test installation. No idea at the moment what's the difference between your workflow/installation and mine. |
|
Hmmm, I do have one error, so indeed maybe it stops at that point. I'll see if I can get that error fixed then check again. |
|
Not maybe - that's exactly what happens. The checks are executed by group, and if one group has a failure, then the subsequent ones are not executed at all. |
|
Waiting for feedback concerning
and also the warnings in admin/check/index.pp |
|
I've fixed my allow_local_infile warning, that was trivial. But, from the searching I've done so far, converting a MySQL database from Latin1 to UTF-8 seems non-trivial, especially for a non-SQL-expert like me. But I'll get it fixed eventually, and update to mantis 2.23, and see if I still repro this issue. |
|
@rogueresearch this may help https://dba.stackexchange.com/questions/123572/convert-mysql-database-from-latin1-to-utf8mb4-and-take-care-of-german-umlauts |
|
@dregad, thanks, I found similar threads too. But I haven't found anything as simple as a single command/script to run. I'll get there eventually... In the mean time, I have updated my prod server from 2.21.1 to 2.23.0, and I do still get the "APPLICATION ERROR #100" error. I'll report back here again once I managed the UTF-8 conversion too. |
|
rogueresearch, You did not provide any new feedback to reproduce the issue; I am therefore resolving this issue as "no change required". Feel free to reopen the issue at a later time and provide the requested information. |
|