This question may be related to a resolved thread.

Hi all,

I lost front-end (and back-end) access to a lot of JPG images on a site I recently updated to 2.4.0. After synchronizing each file upload directory, I noticed that the system would go through the motions of synchronizing 300+ images, but it would only show a handful if you viewed them through the File Manager. Upon closer inspection, the images that were visible were GIFs and PNGs only.

This is a single-site LAMP implementation running Apache 2.0 (20051115) and PHP v5.3.11. I looked through a legion of forum posts about what could be the problem, so I’ve gotten the following stuff taken care of:
* all files, subfolders, and subfiles of /images/upload/ are set to chmod 777
* /expressionengine/config/mimes.php file is up-to-date and allows for JPG, JPE, and JPEG
* the fixes in both https://support.ellislab.com/bugs/detail/17392 and in https://support.ellislab.com/bugs/detail/17588 to be able to see the files listed in the File fields again (they came up blank right after completing the update)

Is there anyone who might be able to help?

Thanks,
Keith

Hi FluidMedia LLC,

Thanks for posting your question and welcome to the Forums!

I’m sorry for your trouble after the update!

Can you give me any more details about your installation? Any third-party add-ons? If so, are those updated as well?

I found one other relevant bug report. It is also worth double checking the URLs and paths for your upload destinations.

I look forward to your reply!

Cheers,

Thanks for the reply, Dan!

I also tried the fix in the bug report you just mentioned (though I’m not running an MSM usage), and it seemed to do nothing good or bad.

I have updated all third-party plugins (Solspace Freeform, ED Image Resizer, Low Seg2Cat, NSM TinyMCE) and quadruple-checked the paths and URLs.

In fact, here’s a detail I forgot to mention: after applying the two previous bug fixes I mentioned, I was able to return the File fields in my entries from blank to what they were previously—though there is no conversion of the {filedir_x} path shorthand into an actual path. HTML sees it as an invalid file location, of course, and so the data exists but is incorrect.

Front-end rendering of the same data fails in a different way: where the file data might be {filedir_x}imagename.ext, it only shows up as an empty string. I’m afraid that if I go into the database and hardcode those fields with full URL replacements, the image code would come up blank anyway on the public pages.

Any ideas? Is there more info you might need from me? Thanks in advance!

Hi FluidMedia LLC,

It’s time we get in and have a look first hand. Be looking for an email from me.

Cheers,

Hi Dan,

We have discovered the issue, and it was not an ExpressionEngine issue (at least not directly). After a recent PHP rebuild that was meant to open up FreeType support in GD, EE was still viewing the old JPEG library version (6 versus 8). The system administrator of the web host was able to fix this issue, and after a good synchronization of all the folders and a flush of the /images/cache/ directory (for ED-ImageResizer’s sake), everything worked out nicely.

Please consider this issue resolved and closed.

Thanks,
Keith

Hi Keith,

Excellent news!

Thanks for sharing your experience with us!

If you need anything else, just let us know.

Cheers!