Thread

I am having some issues with the file manager on a site running EE2.1.3.

The first problem occurs when uploading images in a channel entry via a File fieldtype.  The file manager initiates and goes through the upload process as expected, but when I return to the publish screen the file appears with a broken image.  If I leave it at this and then publish, the image appears in a post.  If I then return to edit the post, remove the file and then browse for it in the upload directory, I can see the file name for the previously uploaded image, however, if I select it the file appears in the publish window as “undefined” with no image thumbnail and no longer displays in a post once I select “publish”

The upload paths are correct and are writeable.  I can find the files on the server via FTP, and if I download them to my computer they open correctly with no corruption at all.

Also if I use Content>File Manager, I can see the uploaded files everything seems to be working fine there.  However, if then go to create a new post in a channel, and browse for the file via the pop up file manager it appears with no thumbnail preview and the file will not work if attached to the entry.  It just appears as “undefined”.  Once again if I browse via FTP and download the image there are no problems with the file.

Some of the things I have looked into so far:
• Tested with XSS filtering to uploads both on and off.
• No apparent MIME type issues

Any suggestions would be great!

cheers,
Jeff

Hi Jeff,

What kind of image files are they and how were they generated? Also, how big are they? Was your site upgraded from a previous version?

Cheers

Greg

Hi Greg,

The images are pretty much all JPG file, originally created in photoshop, they are all quite small–ranging from 4KB-150KB.

The site was first created in EE2.1.0 It was upgraded to 2.1.2 and then reverted back to 2.1 when bugs appeared. After a few days it was upgraded to 2.1.3.

I am happy to provide CP access if it will help resolve the issue.

cheers,
Jeff

Jeff,

has a _thumbs folder been created in your specific upload folder?
Can you see the thumbnails in there?

In your upload destination preferences do you have a relative or an absolute path for your destination directory?

Can I confirm you did a version update as opposed to a build update when moving to 2.1.3?

John,

All of the upload directories I have created have a _thumbs folder and I can see images in there, however, I am seeing now that when I upload new content, it does not appear that new thumbs are being generated–so I can only assume that somewhere during the upgrade process something has happened.

All of the upload destination preferences use absolute paths.

I did a version update, not a build, when updating to 2.1.3

cheers,
Jeff

What permissions does your thumbs folder have? Do you have an image manipulation library (such as GD2 or IamgeMagick) installed and configured correctly? Are you using any extensions?

Ingmar,

When I created each upload directory, I gave them 777 permissions.  The _thumbs folders are automatically created by EE and are currently set to 755 which I am guessing is correct.

I confirmed with the hosting company that ImageMagick is installed and configured.  I am using extensions, I have; CP Analytics , Low Variables, Matrix, NSM .htaccess Generator, NSM Better Meta, P&T Field Pack installed.

I have tried disabling all extensions and this made no difference to the problem. I am more than happy to PM with CP login/FTP if it will help troubleshoot this quicker.

cheers,
Jeff

Looks like I have this resolved now – I stumbled across this post (http://ellislab.com/forums/viewthread/174760/).  It seems my issue was that my development server used GD2, but the live server had ImageMagick–so my image sizing preferences were out of whack.

Updating the paths in the preferences, clearing caches and manually setting permissions to 777 has everything running smoothly again.

Feel free to close the thread!

cheers,
Jeff

Glad you were able to figure out what the problem was. Don’t hesitate to post again as needed.