Forums | Mahara Community

Support /
Problems with file uploads


anonymous profile picture
Account deleted
Posts: 1643

03 March 2009, 19:11

Hi Jez - this is interesting too - I have added a note to the bug report I created to remind us to investigate this.
anonymous profile picture
Account deleted
Posts: 1643

03 March 2009, 19:09

Hi - Mahara also defines clam_scan_file, so I think we have another instance of a function name conflict.

The clam extension for PHP used to be abandoned and unused, but maybe it has been revied, and ubuntu has now packaged it, thus bringing this problem back.

I think the solution here is to rename that function in Mahara, then there won't be any conflicts. I have filed a bug for it, hopefully we can fix it before 1.1.2 Cool

anonymous profile picture
Account deleted
Posts: 91

05 March 2009, 6:19

Thank for looking at that... it was a bit of a pain that one!
anonymous profile picture
Account deleted
Posts: 18

17 March 2009, 9:35

Hi,

I have upgrade mahara from 1.06 to 1.1.1 and I was having same problem with file upload.

Error was not related to clamAV.

First error was because we didn’t have php_exif extension which is required by lib/file.php (func. is_image_file, line 360). After that file upload was working under My files but not if attaching file to blog post.

After looking in our Apache error log we have found that we were missing mahartefact_blog_blogpost_file_pending table. So I have created new clean mahara 1.1.1. install and copied the structure of the table in to active database and now everything is working.

Question: Is this upgrade error? That is why upgrade process didn’t create that new table. And what is this table used for? 
anonymous profile picture
Account deleted
Posts: 1643

17 March 2009, 16:11

Hi - the exif thing sounds like we need another check in the installer for that extension.

As for the table, I don't know. I bet you're using MySQL, some people have reported that for some strange reason, MySQL simply doesn't create tables sometimes - yet it can't be causing an error which is annoyingly MySQL-ish behaviour. There's nothing complicated about that table, it's just used for recording temporary info about files uploaded to blog posts.

45 results