Support/Comments for DirectResize

It is incorrect that you can use chunk name in $tpl parameter. In last version of plugin $tpl is html code with own placeholders, not chunk or file name - only html code. All configuration is in config file in direct resize folder.

Cheers for this plugin - it’s really great

My only problem so far is that images with .jpeg extension (not .jpg, those are fine) don’t seem to be parsed by the thumbnailer.

Changing the extension to .jpg and re-uploading them doesn’t seem to work either.

Any ideas?

EDIT: Seems to be only pictures with either an ampersand (&) or the word "and" in the title. Is some part of the code trying to parse these bits as literal PHP?

I noticed that the thumbnail images and the "wysiwyg..." images stay in the drgalleries folder (for each doc) even after they are removed from the doc in the RTE. This means that my client will end up with hundreds or even 1000s of redundant image files in the drgalleries folders over time as they keep editing their docs. Is there any way to delete the removed images automatically?

Thanks,
Anton

@AntonL Just look in readme for &clearCache option in plugin configuration.

You have to put this anywhere on the download page and maybe it is not a good idea to make the example using a ’semi-commercial’ script:

Redistribution: You are allowed to distribute Highslide JS with non-commercial packages given that you a) emphasize on your download page that Highslide JS is not free for commercial use, and b) provide a link back to this web page on your download page.

@metaller: Thanks for the fast reply! I changed the &clearCache parameter to = 1 and that seemed to do the trick.

Anton

@Jako Maybe you are right. I paste this redistribution in readme.

I really like this plugin,

But what I like to see is that you can user the directresize plugin with differed configs depending on the div thats in

I like to use it small in my sidebbar (product images) but bigger in the content between introtext and content using a tv.
but now I can only use one config that does not look at the container div but processes all images entered in the manager.

would it be posible to make it more flexible? so that you can set a div name in the config and when image is in that div it wil be treated another way?

or is it possible to use the allow_from parameter to run the plugin twice? using lets say in the first plugin the config=highslide and in the second highslide2?

Ok this last part worked we made a copy of the plugin and a copy of the config and this worked like a charm.

As you can read in readme, ToDo section:

* The ability to make different sets of configuration parameters for use in various documents of a site.

I’m agree with you that it will be very useful feature.

I hope there will be time this summer to resume work with plugin.