what is the exact mechanism of this dynamic style of serving images? Explain it in a few words.
What about the way image_assist guys use - a [image ... ] input filter. This makes things dynamic too - do you have sth against it that kept you from using it?
Comments
Comment #1
jdelaune commentedThis will be solved in v2 of ImageBrowser. The main issue was with [] tags you wouldn't see the actual images in WYSIWYG editors. But the alpha version of v2 has solved that.
Comment #2
rsvelko commentedimg_assist had the same problem and since months it got resolved.
1. When you adopt [] tags will you throw away the now-used dynamic serve method? Just curious.
note: using [] tags resolves the issue with print module not finding images too . Although it seems that it is their bug not yours .
Comment #3
jdelaune commentedrsvelko mind testing this out for me and letting me know what results you get. Seems to be working ok for me.
I was using an Image (module) function to return the images but I realise this may not be ideal with the issue above.
If you go to the imagebrowser_view_image() function in imagebrowser.module (line 545).
Replace the line:
image_fetch($nid, $size);with:
Let me know if this helps with your YSlow stats as well.
Comment #4
rsvelko commentedYes, that fixed the Yslow part. +1 for us :)
A patch to come would be great:
here is the image_fetch func
and we want to substitute the call to it by:
$node = node_load(array('type' => 'image', 'nid' => $nid));
$file = $node->images[$size];
header('Location: '.base_path().$file);
probably we need to check for access??
Please review and commit the patch. Seems simple enough.
Comment #5
rsvelko commentedbump.
Comment #6
jdelaune commentedPatch updated with permission checks and committed to the dev branch.