user should not have choices of all preset since admin chooses preset to be applied

This is not a bug. It is up to the webmaster to choose which imagecache preset should be displayed. In this case default preset is displayed.

You can choose wich imagecache preset to use in your display at www.example.com/admin/content/node-type/story/display . You'll find here the default choice for "full node" and "teaser".

EPSA Crop is there to choose the coordinates of the crop made to those presets, nothing more.

Thanks for your feedback !

1) Restrict the preset list to those currently used in teaser/full node : If you only have these two displays, you'd only need two presets. Other presets could be used in the templates, you can't have a list of that.
2) If there's no coordinates set with EPSA Crop, the default imagecache cropping mechanism applies.
3) Why wouldn't you allow the user to resize the cropping area ? The ratio is important, the resulting image will be resized.

This is not a bug :) as yvmarques said EPSA Crop is there to choose the coordinates of the crop made to those presets, nothing more.

But yes this could be a nice feature request since this module doesn't integrate with WYSIWYG editors. You have to use http://drupal.org/project/filefield_insert

Perhaps I am missing a point, but isn't the idea for the full image to display and no cropping to occur in the main story, while the thumbnails are cropped? In the story I uploaded the system crops the pics to a default square, in this case the picture contains a copyright notice which is crucial to display once a user clicks on it.

In this case the copyright information is lost due to the cropping.

http://www.aswissidea.com/node/30

On the front page however it displays as intended after the user crop was affected.

http://www.aswissidea.com/

Is there an override on the automatic cropping at admin level?

The image displayed in "full node" mode is a preset (240x240), hence the cropping/missing parts.

Hi bas.hr,

you say, EPSA does not integrate with WYSIWYG editors.
In my case EPSA doesn´t work at all when FCKeditor is active on the page where I crop an image.

The new coordinates are of course there - until I press "Save".
Going back to edit mode and looking for my new coordinates: they are gone.
I don´t know yet what to change in the configuration of FCKeditor so that it doesn´t (maybe) strip those coordinates when I save the page.

My solution now is to have FCKeditor deactivated by default for the purpose of cropping the image.
After I have saved the coordinates (in this case it works) I go back to edit the page, activate FCKeditor and start writing or editing title, text and all that stuff on the page.

But anyway I should not forget to say: very useful module!

4kant

Problem with FCKeditor solved:

It´s just this little line in the FCKeditor´s visibility settings (fields to exclude): edit-epsacropcoords.

4kant

Regarding the list of presets on the imagefield...

I was under the impression that I could have a bunch of custom cropped images to use in other areas of my site.
But the only preset that works is the one displayed on the node page.
I'm interested in getting this module to use all the presets if needed, not eliminate the list.

I've been able to regenerate the correctly cropped image by changing the cck display setting for the content type.
Next, I want to figure out how to make ALL the presets generate the EPSAcrop coordinates.

I post this to get feedback on if this is the way the module is going.
The only difference I see between this and image crop is the ability to post crops for each imagecache present.
Perhaps there is a way to preserve this 'feature' instead of eliminating it.

peace,
michael

changing to beta2, as it is current.

GiorgosK:

I don't think it is misleading, this is exactly how the module should work. The point is to create content aware crops of the image. Ie. The user selects the best crop/scale for each preset, because the presets are there and being used somewhere.

Another point is that I have made a media field where all media is uploaded. The cropping is very clearly in its place there, it is an image, and the uploader decides the correct representation of the image for different crops, thus conveying the right artistic representation of the whole, or the correct representation of the scene if it is a documentary picture.

The solution to your problem is using something like imagebrowser, img_assist or imagefield_assist. Those let you choose the imagecache preset to use to insert the image into a text area.

There also is a module for the Frace24 moduleset which is used to select how content is rendered in the nodereference, it might be similar to the problem you are describing.

If the maintainer changes the behaviour, please make any changes in the behaviour be optional. Keep it as it is, it is simple and beautiful and does the job the right way :)

AFAIK there is no image upload module, perhapc except imce, which lets you override the settings of what the admin has decided. This is a valid request for creating a module where the uploader could select the preset.

pelicani:

The thing is that the one uploading the image is the one who can make the best decision of how to create different crops of the image. To make this decision all the available crops should be there, so that the decision can be made when the picture has been uploaded.

Even though the image is used in the same node only in some use cases, in my use cases the node just holds the image, while other nodes are the content. I also use linodef module to insert the links to the image, including custom_formatters which use imagecache tokens to insert the correct size of the image for the current formatter.

above bas.hr suggests using insert, there is a pretty recent module called Wysiwyg Imagefield that expands the usability of "Insert" and "ImageField" even more.

I like how EPSA crop solves this image cropping challenge.

A developer, no doubt, could handle these solutions.
The solution I crave is for my clients.
Secretaries, Interns, Journalists, etc.
Too many cropping options confuse the casual visitor.
The ability to limit the options would be useful.

The only epsa crop setting that consistently works is the one that is set for the node display.
All of the other setting options, sometimes, fail.

We want to give the visitor who uploads the image the chance to crop the image correctly.
Sometimes they don't need access to all the crops I need to use on the site.
See similar request ... http://drupal.org/node/904932

I suggest that for every place an image is used there is an manage this crop link for the owner of the image and any admins withe the correct permission, or anyone the owner delegates rights to via nodeaccess user reference, nodeaccess role reference or similar.

There should be a few epsacrop permissions:

epsacrop create crops
epsacrop edit all crops
epsacrop edit my crops
epsacrop delete all crops
epsacrop delete my crops
epsacrop view all crops
epsacrop view own crops
epsacrop edit my crops in place (for showing links)
epsacrop edit all crops in place (for showing links)
epsacrop edit my crops with all presets (for current use case)
epsacrop edit all crops with all presets (for current use case)
epsacrop administer available crops (to cover use case where admin limits access for crops, the one asked for in #16)

With the above this module could cover all the suggested use-cases in #16 + add one which lets the owner of the image edit the crop "in place" or in "context", which is often when you see that you cropped wrong.

I wonder if the maintainer likes this, and if anyone else in the thread believes this is ok?