Hi, I'm testing the version 2 of imagebrowser and it ROCKS! So much that I'm pretty much using it on clients website and they are already very happy with it. The only thing that I would change about it is that ALL the imagcache profiles are shown in the list of available profiles.
Is there a way to restrict this already ?

If not, it would be a great feature, as we create imagecache profile for many things like views, user profiles, galleries, and much of them shouldn't find there way to the client UI. Best case scenario I would create a LARGE, MEDIUM and SMALL profile that I would expose to the client in imagebrowser, so they can only choose from these 3 profiles only, and not any other that might screw up the layout.

We know how clients like to do exactly what they shouldn't :)

I also wanted to share a little trick I use : adding an empty imagecache profile (that I call FULL) can be used for the link so when clicking on the image, the user can see the full image.

Thanks!

Comments

Anonymous’s picture

Title: Select which imagecache profile to expose » Select which imagecache profile to expose in imagebrowser
jdelaune’s picture

Assigned: Unassigned » jdelaune

You were able to do this in IBv1 by setting permissions but I've removed it for some reason in v2. I'm really busy at the moment and I'm off to Kenya for two weeks next week so I don't when I'll next get a chance to work on Drupal stuff. But this shouldn't be to hard to port back in.

Anonymous’s picture

Assigned: jdelaune » Unassigned
Priority: Normal » Minor

Awesome, take all the time you need, and enjoy Kenya ! I loved the beach there, and of course, the wildlife !
Am not worried, no rush here.

Thanks !

jdelaune’s picture

Status: Active » Fixed

Didn't get to see any beaches or wildlife unfortunately, a bit gutted about the wildlife. Will have to go back there. Met a nice lady out there though so the trip wasn't a total loss :P

This one is fixed and go in the dev version to be released in the next 24hrs. Cheers

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.