Module [mod_flexicontent] image Processing method: none

In Display parameters for ITEMs (used by some Layouts) --> Image parameters is Processing method eather Scale or Crop but not use original which would help to keep the image quality high and server load low.

That is weird, what you want is,
IF the user puts an image with 100px than it shows with 100 pixels
but if the user puts an image with 2000px it will show with 2000 pixels.


Is this what you want? How are you going to control the design/template so the user does not break it?

Can you share a link? I have a few ideas how to help, by I need to know where you need this change if it is in the category, module, rss, etc.

Thank you for your offer. The layout can easily be controlled via css (img{max-width:100%}), there is no hassle.

The site is still local on my machine. This feature would be needed in Module [mod_flexicontent] image Processing (as stated in the subject )

Cheers

I had an idea but it didn't work, I think like you said I has to be in the filter

Went to see the template news and nothing there so it had to be at the field.

Layouts depend on having a specific size, so this option is not available

Layouts depend on having a specific size

What do you mean by that? I can still specify the thumbs to be 2000x2000 which could ruin the layout as well. But as I said earlier the img size can easily be controlled via css if necessar at all.

I think the administrator of the website should have the choice rather than the coder of the extension. Don't you agree?

Ever desicion have pros and cons this one I think it has more cons let me explain why you need the size or crop always:

1-if the user upload an image to big in size FC will change it to meet the field needs so it isn't to big, i am talking about megabites.

2-this forces the user to think about the images they put about to put, they cannot upload a thumnail for a slideshow or vice-versa.

3-there are 3 types of images, vertical, horizontal and square. again you cannot all of them for the same purpose.

this are some of the reasons a think that feature is not necessary.

but if you may explain your purpose i can understand.

It is really bad practice:

1. Resizing an image via CSS will make it have broken look depending on browser,

and if the user uploads multi-megabyte pictures.

2. You risk making your web pages very slow, particularly category view but also item view

3. You risk eating up your web space fast


IT IS BETTER to have multiple sizes per picture (with a logical upper limit for the "big" picture) instead of using CSS to stretch the image to different sizes for category / item / tags / favs / module / etc view

Your points are all valid - if your site is open to a broad variaty of users. But there are other use cases too. In my case a photographer will upload his images. He knows exactly what he is doining. I simply cannot present him his images badly compressed by a php function.

Resizing images via css is common in responsive design. A very contemporary and elaborate practice

Why is the FC risize function not working properly anyway? Is this a relict from older days?

mmm, which resize function is not working? where?

image field?
flexicontent module?
blog layout for category view?

somewhere else?