Symphony.

I know the Symphony team is thinking about core fields and the file upload field is one of those that everyone has different wants/needs.

Anyway, I just noticed Plupload, by Moxiecode, the same guys who are behind TinyMCE. I thought it looked nice and allowed for a variety of situations.

Ooooh nice :) this looks very promising indeed.. for a non coder like me!

Looks great, very user friendly interface.

This thing sounds more suitable for a multi upload tool than a core upload field.

It has image resizing on upload function too methinks! or at least the abilit yto limit size on upload.. something I think is greatly missing at the moment.. i.e limit upload size of files that clients can use..

@moonoo: I agree!

I don’t agree. Actually file size is limited, and image size doesn’t need to be limited. Since Symphony 2 is caching resized images, even very large digital camera files are not a big problem if you use the JIT extension to resize them.

It might however be a problem if your clients want to use Symphony to “layout pages”, i.e. place images everywhere in their articles. Some clients expect this, because some CMSs encourage this. I don’t. If clients want to do this, they must gain some knowledge about image formats/size and about (Markdown) semantics.

As most of you will know, I am not fond of a “bloated core”. And Plugload has too many dependencies to be a good choice for Symphony.

Maybe I reacted too soon: for a lot of projects I’ve done, the filesize didn’t matter, but the image size did.

If the image uploaded was too big, too much details would be lost if the image was resized to something small, and vice versa: if the image is too small, it would look like crap when it’s enlarged. In these cases, putting limits on image size would be really handy. (as long as there’s a min and a max size!)

As far as the core extension goes, I agree with you michael, if it’s not needed for EVERY project, it shouldn’t be a core extension.

:-) Thanks.

no problem ;)

Gosh, I like this forum… alot.

I like what it’s trying to do but agree that integration is not necassary to the core.

Horses for Courses as we say! Clients may still try to upload 10mb files in upload fields though.. which I find annoying and JIT is good for front end presentation of the images and sizing.. it’s manipulating the files to a limited max dimensions before it even reaches symphony is my biggest gripe that would love to see tackled.

Not being a hot on code, I can only offer experience of how I have found using symphony from a clients point of view which on the whole is awesome.. it’s just those little niceties that would seal it for me.

EDIT @creativedutchmen

Beat me to it eh! same issues we’re both experiencing?

@moonoo: do you mean like client side resize before it gets uploaded to avoid huge uploads? If plupload can do that, wow.

EDIT: @moonoo: pretty much, yeah.

@creativvedutchmen..

It’s one of those situations that effects the loading of an entry if I’m using mediathek etc.. 8mb file was the culprit for an image that displays at 400px wide on the front end! so for me it’s essential to limit max file dimensions on an upload field basis for images if possible. And if plupload is offering solutions to this then I’m intreagued and will be looking into it as an option for adding into an install or two!

@moonoo2

Have you tried my Advanced Upload Field? It Let’s you define maximum image dimensions and a cropper version gets saved in the server. Please let me know if you run in any problems.

Oooh never noticed this one! wil check it out :-)