Only one of the blogs in the installation - blog id 3 is throwing this error - we get this when we try and upload an image or hit the manage assets link:

file not found: /kunden/homepages/3/d145009620/htdocs/blogpirecontent/bpcontent_mt_two/netpbm/topnm at lib/MT/Image.pm line 255

However uploading or managing assets on the 2 other blogs ID1 and ID2 works. Is there something messed up with the assets of the blog?

We do use the NETPBM library for image thumbnail stuff - but it's working great on the other blogs.

Any help would be great.

It will also throw the exception when I view the manage assets and include blog 3 in the master list...

file not found: /kunden/homepages/3/d145009620/htdocs/blogpirecontent/bpcontent_mt_two/netpbm/topnm at lib/MT/Image.pm line 255

Also - commenting out the use of NetPBM in the mt-config.cgi - results in the blog manage assets working and we can upload files on all blogs - no image resizing.

#ImageDriver NetPBM
#NetPBMPath /kunden/homepages/3/d145009620/htdocs/blogpirecontent/bpcontent_mt_two/netpbm

Any thoughts? Is some thumbnail thing in the assets_c thing messed up? etc?

Also - now with the netpbm driver commented out - I uploaded an image.

Then I uncommented it - made it live and now I can upload images on that blog again.

What? Did I somehow fix the database or something else that was hosed?

However - I can upload now - but manage assets global and on that blogs manage assets throws this:
file not found: /kunden/homepages/3/d145009620/htdocs/blogpirecontent/bpcontent_mt_two/netpbm/topnm at lib/MT/Image.pm line 255

So it's not working but we can upload images again.

Must be something messed up...

Okay - we now can't upload via the post upload file - meaning on the entry screen - but we can upload using Create Upload File.

Hitting Manage Assets still throws the error above on both the blog 3 and on the main manage assets.

Okay - so it's one of the last 25 images posted.

If I do this:

http://www.blogpirecontent.com/bpcontent_m...3&offset=25

Offsetting - the manage assets screen works. So if I take away the offset:

http://www.blogpirecontent.com/bpcontent_m...d=3&offset=

It throws the error.

Do I just delete the assets_c

Is movable type trying to find something that is missing? Unsure of how to fix.

Well - we tracked it down to this asset:

media.nl.jpeg

Looks like removing that from the database makes it work.

Is it the extension?

Wow - bad bug.

Yes, I suddenly had a similar problem today. I have not made any updates / changes / alterations to my database or templates in quite a while.

So, I cleared the asset table and everything seemed to be normal until I noticed that the resizing function had vanished.

If I upload a file and do not resize, it does not create the preview image, but it continues to allow image uploads.

If I upload a file and try to make it a link to the full size image, this breaks the uploading process every time.

Any ideas apart from constantly clearing the asset table?

NetPBM has caused a few hiccups like this in the past for me. Simply, NetPBM isn't near as robust as is really needed and just can't work reliably with certain image types and file extensions (for me, it was PNG files and less common extensions like "jpeg" and "tiff"). IMO. That's where ImageMagick really shines as a better tool to do all this stuff, and probably the best choice.