File

Scottmoa:

Images uploaded are being converted from nice pretty jpegs to crunchy gifs, making them HUGE files and ugly.

Does making the following change in the extension code help? Change From:

if(@imagegif($dst_img, $dst) !== false) {}
else if(@imagejpeg($dst_img, $dst) !== false) {}
else if(@imagepng($dst_img, $dst) !== false) {}

Change To:

if(@imagejpeg($dst_img, $dst) !== false) {}
else if(@imagegif($dst_img, $dst) !== false) {}
else if(@imagepng($dst_img, $dst) !== false) {}

Excellent! That appears to have solved the jpeg/GIF conversion issue. thank you!

Now I only have one issue - it’s still resizing it to the maximum image size set in the upload prefs. Ideally, it shouldn’t touch it at all if the image is within those parameters. This resizing is both increasing the file sizes and, as you know, with each manipulation there’s a drop in image quality.

Any guesses?

In the mean time, I’ve simply removed the maximum dimensions to prevent any resizing.

thank you for your assistance.

Wow this thread is really long eh? (If this question has already been answered on this thread I apologize)

It sounds like when a file is uploaded using the ‘file’ extension, that it automagically creates thumbnails for those images. Mine doesn’t seem to be doing that, is there a setting that I need to set? I imagine that in my upload directory there should be the image I uploaded and a thumbnail of it. (I’m not seeing any thumb files)
It shows thumbs when I am editing weblog entries, but when I call the {file_thumb_url} variable, it doesn’t link to anything. Does it matter what kind of image file I upload, jpg or gif?

Here’s some code I use to call the thumb image: {exp:weblog:entries weblog="portfolio" limit=1 dynamic="off" status="Featured"}

{portfolio-main-image} {file_thumb_url}<br> {/portfolio-main-image}

{/exp:weblog:entries}

Sorry if this is really obvious and really long winded.

-kev

Why can’t I get this multi file to work?

I have multi images enables in the prefs my code is

{exp:weblog:entries weblog="missions" category="7"}
{missiongallerys}{missiongallery} </a>{/missiongallerys}
             {/exp:weblog:entries}

missiongallery is my custom field.

when it is outputted only the first image appears as well as in the browser {missiongallerys} {/missiongallerys}

ie: this is the source or the outputted page

{missiongallerys} <img src="http://domain.org/images/uploads/1.jpg" alt=""  />{/missiongallerys}

If I upload 4 images and I use this code below everything works except I just get the same first image 4 times.

{exp:weblog:entries weblog="missions" category="7"}
{missiongallery}{missiongallery} </a>{/missiongallery}
             {/exp:weblog:entries}

So it appears adding the “s” to make it plural which I thought was the trick in using multiple images breaks everything.

I wanted to discuss improvements and customizations but this thread got a little too long.

I created this new thread for discussing advanced use of Mark Huot File Extension.

Please come over if you have feature requests, customization tips, etc

I read about 50% of this thread and didn’t find a problem or solution similar to what I’m experiencing on a client site. During development on our own server File worked like a charm. However, we moved the dev site to production on the client’s server last week and now File doesn’t work. Specifically, the file/image doesn’t get uploaded to the server. I confirmed this by looking via FTP.

Of course, I checked, double-checked and triple-checked all settings. Everything is correct. Previous images that were uploaded on the development site are showing just fine on the live/production site. I should mention this live site is hosted at GoDaddy (yeah, I know…).

Also, I checked the regular file upload that comes with EE and that works as its supposed to. It’s definitely something with File. Can someone please help? I have no idea what the difference may be or where to start troubleshooting.

.angie

Previous images that were uploaded on the development site are showing just fine on the live/production site.

Usually when this happens, your paths are still pointing to other server. So you move the files over, move the database, but unless you change the upload paths, the images are going to come from original server.

I move databases from dev, to staging, to production, and vice versa all the time. I have no problems.

What we choose to do is: never move DB from dev to production. Always from production to dev. So when I custom fields for example, I create them on production, export the DB and import it into dev. Then I go over the paths to point at dev. This way you can never break production.

Take a look at the images I uploaded. One is production settings and the other one is dev settings.

The third is the custom field settings.

Hope this helps.

Usually when this happens, your paths are still pointing to other server. So you move the files over, move the database, but unless you change the upload paths, the images are going to come from original server.

Very true. And I checked that thoroughly because I’ve had that little bit bite me in the rear before. But apparently something wasn’t right… I just checked things today and everything’s working. In all the checking and editing I must have changed something to the right setting. Guess a good night’s sleep is better than anything after all. 😊

Mark,

I really like the nice interface and ease of use. Is there anyway to leverage this to associate files on the server that have been uploaded by ftp? If not, are you aware of any other options for doing so?

Thanks,

Forrest

Is there anyway to leverage this to associate files on the server that have been uploaded by ftp? If not, are you aware of any other options for doing so?

Totally something needed. I thought about it many times but always forget to post it. Thanks for pointing this out.

I will post it here too.

Mark Huot File Extension

Hi,

What if you have multiple SAEFs? Has anyone successfully used Jermain M’s ext.saef_enctype.php extension with multiple paths to saefs?

Thanks

Hi,

I wonder if anyone has had a problem with the file extension and Safari. Whenever I try to submit the pub/edit form or the saef with a file custom field on it the form doesn’t get submitted–it just hangs up and the data isn’t submitted. Both the cp and the saef work fine with firefox and camino.

Thanks

I’m using Safari 312 with File Extension 311 and EE 165. Everything works fine.

Huh, really. Strange. I cannot get it to submit with Safari. Everything else works fine. I’m using the same version.

I am running a mysql server version 4.0.20 It seems that the extension requires features that is only on 4.1

Does anyone know if there is there an older version of the extension that will work on 4.0 ?