I've noticed some odd behavior in my report log, a warning of: FileField was trying to display the file files/imageX.JPG, but it does not exist.

Why is this odd? Well, the page (main index) causing this error doesn't call that image and appears nowhere in the html source.
I can replicate the issue by renaming any another image associated to the nodes linked on the index.

- Images in the 'files' directory are the original and shouldn't be loading as imagecache handles the resized image.

Does anyone have some insight to this?

Comments

jh3’s picture

jh3 commented

I'm having the same exact problem. No idea why it's happening at the moment. I'll let you know if I find anything out.

rewted’s picture

rewted commented

I've discovered this is just how imagecache works. Apparently you NEED to keep the original image in the files dir, otherwise if you delete them the cached version of the image will not work.

In my case, the original img was missing, in turn causing the resized images called from your imagecache dir to not work and triggering the error. Give it a try, rename an original image and then view a page that uses that resized imagecache image and let me know if your page displays as broken. Rename back to the original file name and see it work again.

quicksketch’s picture

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

Right, you can never move the original file through FTP or some other mean without updating the corresponding record in the database. In the case of ImageCache, it's important to note that derivative images are not permanent (hence the "cache" part of imagecache) and may be deleted and regenerated at any time, meaning the original image needs to remain in order for the derived images to work in the future.

Status: Fixed » Closed (fixed)

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

xjm’s picture

xjm
she/her
Primary language English
commented

I've been having the same problem. See also #794910: Log filled with "FileField was trying to display the file but it does not exist." for this error message.

jmseigneur’s picture

jmseigneur commented

Subscribing. Same problem.

Rhino-new’s picture

Rhino-new commented

....OK!

"never move the original file through FTP or some other mean without updating the corresponding record in the database."

Where is this corresponding record? I'll be happy to update it, as I now have tens of thousands of FileField was trying to display the file ... issues due to moving files to Amazon s3.