Hi,
I have a clean install of mantis 1.0.0a2 on SuSE Linux ES 8 (SLES8):
mod_php4-4.2.2-165
apache-1.3.26-57
mysql-3.23.52-41
All works except for file uploads - even a 20 byte text file. I've looked at the previous posts and have changed the following settings but with no improvement:
/etc/php.ini:
file_uploads = On
upload_tmp_dir = /srv/www/htdocs/mantis/tmp
upload_max_filesize = 10M
I've tried:
chmod 777 /srv/www/htdocs/mantis/tmp
And each time I try to upload the date/time stamp on the upload tmp directory changes but no file is present (presumably it's deleted after the upload).
Turning on debugging show a temp file created like /srv/www/htdocs/mantis/tmp/php2FF4g and file size is 0.
No errors in the apache logs.
Can anyone help ?
It's for a bunch of windows devs to submit bug reports so it would be good to get it going ;o)
File upload to DB
Moderators: Developer, Contributor
-
damian742
OK. What do I need to do to upgrade to 1.0.0a3 ? I'm not conversant with CVS (yet).
I'm selecting a file and it shows in the upload field prior to hitting "upload".
As for errors, I see:
APPLICATION ERROR #500
File upload failed. This is likely because the filesize was larger than is currently allowed by this PHP installation.
- even with a 20 byte file.
I'm selecting a file and it shows in the upload field prior to hitting "upload".
As for errors, I see:
APPLICATION ERROR #500
File upload failed. This is likely because the filesize was larger than is currently allowed by this PHP installation.
- even with a 20 byte file.
1.0.0a3 has been released. It should be available in the normal download places as shown on http://www.mantisbt.org. The new code overlays the old. Please run the admin/upgrade.php script before trying the new code.
-
damian742
OK. I unpacked 1.0.0a3 over the top os 0a2 and ran the upgrade script successfully.
Log in as a manager user and the following fills the screen ....
APPLICATION ERROR #401
Database query failed. Error received from database was #1064: You have an error in your SQL syntax near 'on cft.id = cfpt.field_id
JOIN mantis_project_table as pt on' at line 3 for the query: SELECT distinct cft.id as id, cft.name as name
FROM mantis_custom_field_table as cft
JOIN mantis_custom_field_project_table as cfpt on cft.id = cfpt.field_id
JOIN mantis_project_table as pt on cfpt.project_id = pt.id
LEFT JOIN mantis_project_user_list_table as pult
on cfpt.project_id = pult.project_id and pult.user_id = 3
JOIN mantis_user_table as ut on ut.id = 3
WHERE pt.view_state = 10 OR
( pt.view_state = 50 and pult.user_id = 3 ) OR
( pult.user_id is null and ut.access_level >= 90 )
ORDER BY name ASC
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
The database is up and was working before I upgraded.
Log in as a manager user and the following fills the screen ....
APPLICATION ERROR #401
Database query failed. Error received from database was #1064: You have an error in your SQL syntax near 'on cft.id = cfpt.field_id
JOIN mantis_project_table as pt on' at line 3 for the query: SELECT distinct cft.id as id, cft.name as name
FROM mantis_custom_field_table as cft
JOIN mantis_custom_field_project_table as cfpt on cft.id = cfpt.field_id
JOIN mantis_project_table as pt on cfpt.project_id = pt.id
LEFT JOIN mantis_project_user_list_table as pult
on cfpt.project_id = pult.project_id and pult.user_id = 3
JOIN mantis_user_table as ut on ut.id = 3
WHERE pt.view_state = 10 OR
( pt.view_state = 50 and pult.user_id = 3 ) OR
( pult.user_id is null and ut.access_level >= 90 )
ORDER BY name ASC
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
The database is up and was working before I upgraded.
-
damian742
Next stage, a clean install of 1.0.0a3.
mysqldumped the mantis DB and tar gzipped the /srv/www/htdocs/mantis directory.
Create a new mantis mysql DB and a fresh install of 1.0.0a3.
Try to log in as administrator and get the same error message 401 as above (with all accompanying text).
I'll try going back to 1.0.0a2.
mysqldumped the mantis DB and tar gzipped the /srv/www/htdocs/mantis directory.
Create a new mantis mysql DB and a fresh install of 1.0.0a3.
Try to log in as administrator and get the same error message 401 as above (with all accompanying text).
I'll try going back to 1.0.0a2.
-
Guest
Back to 1.0.0a3 and the fix at http://forums.mantisbt.org/viewtopic.php?t=379 works.
It doesn't work however on 1.0.0a2 upgraded to 1.0.0a3.
Back to the fresh install of 1.0.0a3 and imported the existing users from a2 to a3 using mysql commands.
All working now. Thanks for the tool!
It doesn't work however on 1.0.0a2 upgraded to 1.0.0a3.
Back to the fresh install of 1.0.0a3 and imported the existing users from a2 to a3 using mysql commands.
All working now. Thanks for the tool!