Geeklog Forums

Since upgrading to geeklog 1.3.7sr2 I'm getting this error message when I attempt to add an image to an article: Mime type, image/pjpeg, not in list of allowed mime types This happens on two different sites on two different commercial servers. This is NOT php related since I can upload to Gallery. I am just not able to upload images to Geeklog.

Sorry I have to ask that question: You did replace admin/story.php, didn't you? Also, which browser are you using and what is the extension of the file that you're trying to upload? bye, Dirk

When I upgraded my sites I did not run the install script. All I did was copy over the files. I went back to each site having this problem and ran the install script and that "fixed" the problem. The reason I had not run the script was that there was no option to upgrade from 1.3.7 or 1.3.7sr1 to 1.37sr2. Since I was NOT running 1.3.6 or any of the other earlier versions, I worried that the install script might produce unwanted results.

Hmm, interesting. You shouldn't have to run the install script since there were no database changes from 1.3.7 to 1.3.7sr1 and 1.3.7sr1 to 1.3.7sr2. It shouldn't do any harm if you do, though - but it should also not have anything to do with the image upload ... bye, Dirk

I have five Geeklog sites on three different commercial servers. (All *nix, Apache) One site has not been upgraded to sr2; the other four were upgraded from sr1 to sr2. Three of the four upgraded sites experienced the problem. The fourth had the problem and then did not, and I can't remember if I did something to the site between when the problem occurred and when it did not. At all three sites where I had the problem, running the install script fixed the problem. Why? It is all magic as far as I am concerned.

Just as an FYI--I had the same problem. It actually stemmed from missing the system files.

I had the same problem when uploading images afeter upgrading to sr2. The problem was fixed after I replaced the file /system/classes/upload.class.php using the new one, so probably I forgot to replace it in the first time I upgraded. Good luck. rs

i got the same problem after upgrading to forum 2.3.1 without running the upgrade script.

here is what i did to solve it.

on line 429 of usersettings.php, look for this



replace that line with this one.



hope this helps.

---

we are just shadows of our hidden identities