Again, this is a good looking module, but the necessity to have the eei_ prefix on any usable imagecache previews seems completely pointless and actually very detrimental to the usability.

Imagine the scenario of a site with an existing set of imagecache presets - is the site admin going to have to recreate all his presets just to have this meaningless prefix, or create a whole new set??

Surely there must be a way around this - I have marked this critical because I think (despite it not rendering the module unusable) it is a serious usability bug.

Comments

pcambra’s picture

Status: Active » Postponed (maintainer needs more info)

Hi

The eei_ prefix on the imagecache previews is required because if you have a *lot* of presets and all of them are shown in the select, it would be very unusable. Could you suggest a better workaround?

niklp’s picture

I don't see your point - why would you make imagecache presets and then NOT have them available? If I create a preset initially, before installing this module, then I have to DUPLICATE it with a new name to use it here?? THAT'S poor usability.

Just take the prefix requirement out - it's completely unnecessary. If someone has lots of imagecache presets, then they have that problem all across the site - there's absolutely no point in "trying to do them a favour" in this way, because it's confusing, leads to duplication, and is basically poor practise and the opposite of the behaviour that people would expect.

I also suggest you read the coding standards, because although this module looks like it could be helpful, everyone I've pointed it out to so far has looked at the code and run away screaming.

"Tough love", I'm afraid....

carlitus’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

Thanks for you suggestions, you helped me a lot. I think i'll put your name in the README appreciation list.

niklp’s picture

Surely if you're agreeing with me, that's a WILL fix??