in the options of imagebrowser there are 2 ways to include images.

What are these things and what does each of them imply? I saw that the urls are different in the node and during the inclusion of the image. I understand that somehow in dynamic mode the image is retrieved via imagebrowser ... What is this giving us actually? Flexibility?

Comments

jdelaune’s picture

jdelaune commented
Title: dynamic and static » dynamic and static

Yeah: Choose between dynamic URLs that will mirror changes made to the "Image Node" and static URLs that will be served through Apache and therefore will be faster if performance is an issue.

rsvelko’s picture

rsvelko commented

> Yeah:

= yes to what exactly of the above questions ? :) Dynamic mode gives us defense against future changes of image - you say yes to that, right?

> ... will mirror changes made to the "Image Node" ...
= so the static option wont change when the image node changes its picure? It is just a static link text that will stop to work if the name or the preset of the image changes ... Right?

With dynamic mode I have 2 issues -
1. Yslow shows that images from imagebrowser have no expires header (not a big deal, but is this resolvable)
2. print module does not retrieve the picture if it is dynamically served and dies ugly ... (maybe should post it as a bug to the print module or its pdf printing 3rd party plugin ... )

jdelaune’s picture

jdelaune commented

Right.

Feel free to post patches for issues 1 or 2.

rsvelko’s picture

rsvelko commented
Status: Active » Fixed
jubalkessler’s picture

jubalkessler commented
Status: Fixed » Needs work

The issues in comment #2 are not "fixed". I'm changing the status to "needs work" because I ran into the same issues, and I am curious whether the _maintainer_ of this module will express an interest in fixing the issues, or will explicitly decline to fix them.

Maintainer: If so inclined, please change the status of this bug to one of the following:

"needs work" - this is likely the state in which the issue should remain until a patch is submitted.

"won't fix" - maintainer is: (1) not willing to fix these issues, and declines to state the reason why, (2) is not willing to fix these issues, and states the reason why, (3) is unable to fix these issues, and declines to state the reason why, or (4) is unable to fix these issues, and states the reason why.

"postponed" - the maintainer may or may not deal with those issues later for reason X, or reason Y.

"closed" - in this case, the maintainer is not interested at all in dealing with the issues raised in this report.

Yes... one could say I'm not hopeful about the long-term viability of this module after reading the curt and disinterested reply by the maintainer in comment #3. But at least please, please use this issue tracking system in the way it was intended to be used.

jdelaune’s picture

jdelaune commented
Status: Needs work » Postponed

Cheers jubalkessler. Some of us don't have all the time in the world to support issues for modules we don't get paid for. I'm very busy at the moment and frankly this isn't high on my list of to-dos.

jubalkessler’s picture

jubalkessler commented

Yeah, I was annoyed this morning regarding this particular issue report, and I came off badly. For that, I do apologize.

rsvelko’s picture

rsvelko commented

Hi, since this is a support request (not a bug report) I have put it to fixed cause got all the answers.

The yslow/expires issue ( created one for it http://drupal.org/node/438550 ) :
- is not sth that will kill your site

- (applies to print related issue too ) will be resolved if you use the static insert method - but it will make updating your images hard. So you have one last choice use the

>>> [...] tags and input filters to translate them to images on each page load <<<

insert method - the way img_assist guys do it .

This module here will have these [] tags in v2 which will come up at some point.

The print related issue may be looked upon as print's module or its pdf generating 3rd party tool's bug - since the images are accessible at the dynamic url .

So this issue may be marked fixed now. And note - it was me that marked it before - I am just a user.

jdelaune’s picture

jdelaune commented
Status: Postponed » Closed (fixed)

Like you said [] tags which are coming in v2 should fix this. So I'm marking this as closed.