Hello,
I upgraded Mantis version 1.2.19 to 2.10 with the following:
mysql 5.7.20 configured ok
php version 7.0.27 phpinfo okcopy config files:config_inc.php- custom_strings_inc.php -custom_constants_inc.php to to mantis/config folder.
script "admin/install.php" executed..I can open matis application upload files, view files uploded, but when i try to open attached files uploded I recieve 'http 500 internal server error, please find in atteched my conf files and screeshot of error.
Get http 500 server error when I try to open file attachment
Moderators: Developer, Contributor
Re: Get http 500 server error when I try to open file attachment
Did you run admin/check/indexp.php and checked for errors or warnings?
maybe you have to enable PHP fileinfo extension.
BTW, I removed you attachment as there are passwords for LDAP in it.
maybe you have to enable PHP fileinfo extension.
BTW, I removed you attachment as there are passwords for LDAP in it.
Re: Get http 500 server error when I try to open file attachment
thank you for your quick reply
; plese find the the check result in atteched
- Attachments
-
- check.PNG (61.91 KiB) Viewed 4727 times
Re: Get http 500 server error when I try to open file attachment
There is a warning concerning attachments, the problem is exactly what I mentioned before: You have to enable the PHP fileinfo extension.
Re: Get http 500 server error when I try to open file attachment
thanks a lot for your help..you are right..solved by enbling php infofile.
I've another issue :1) Names with accents or other characters are not correctly displayed. Cfr picture below
I've another issue :1) Names with accents or other characters are not correctly displayed. Cfr picture below
- Attachments
-
- mantis.PNG (211.56 KiB) Viewed 4722 times
Re: Get http 500 server error when I try to open file attachment
I don't know how you migrated from old to new Mantis version.
Just a guess, maybe you used another character encoding than UTF-8 in your old database and did not convert the right way to UTF-8.
Just a guess, maybe you used another character encoding than UTF-8 in your old database and did not convert the right way to UTF-8.