This is kinda strange. I was getting a error every time I tried to upload a image in FireFox. After checking file permissions, paths and anything else I could think of I tried to do a upload in Internet Explorer. Everything worked perfectly fine in IE, no errors at all. I then switched back to FireFox and now the uploads are working with no errors of any sort. Odd....

So to recap: Uploads were not working in FireFox until I tried them in IE. Once I did a successful upload in IE, uploads in FireFox started working.

The error I was getting in FireFox was a pop up that listed the html code for my site. Checking the error logs I was getting the following error:

page not found 08/08/2008 - 10:23 imagefield/js

Everything seems to be working now, just posting this as a FYI.

Comments

cornernote’s picture

cornernote commented
Title: Error when uploading in FireFox » Popup Error when Uploading

I have the same issue. I get an alert() style popup that tells me an error has occured, and then it shows the HTML for my 404 page.

When I check the logs I see:
page not found: imagefield/js

Looking for a seemingly random fix I tried in IE7, however I had the same issue there.

I have recently upgraded from imagefield 5.x-1.1, however there seems to be no schema change so I guess this should not matter.

cornernote’s picture

cornernote commented

ok, the problem was the menu cache... i cleared the menu cache and this issue was solved...

now onto the next issue. :)

albert_philly’s picture

albert_philly commented

I get the same error in both Firefox and Safari when uploading, but only when I'm on the edit node page, not when creating a new node.

The funny thing is, after the error pops up, if I go ahead and submit the node anyways, the image shows up completely fine when I view the node.

@cornernote, how do you clear the menu cache?

albert_philly’s picture

albert_philly commented

Well, I found the solution to my issue with it. It turns out Apache's mod_security2 was being overzealous in it's protection. Adding the appropriate drupal paths to it's whitelist fixed the problem.

quicksketch’s picture

quicksketch
he/him
commented
Category: bug » support
Status: Active » Fixed

Thanks for the follow up albert_philly.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

zzolo’s picture

zzolo commented

I ran into this problem as well. I think it has more to do with menu caching. I was able to just flush the cache (manually) and have my error disappear.