Disabling remote option not working
pabloid - October 27, 2009 - 11:10
| Project: | Image Resize Filter |
| Version: | 6.x-1.5 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
Even if I've checked only "Locally" option, if I include a remote image and then I resize it, the input filter downloads the image in /files/resize/remote folder resizing it.
I don't want input filter to resize remote pictures, 'cause (as help says) it imply downloading the remote image every time.
#1
> 'cause (as help says) it imply downloading the remote image every time [the image is edited]
If this feature is broken, of course it should be fixed if possible.
However, as I understand it, if you don't download the remote image, then every time the page is viewed, the image has to be downloaded from the remote website, which can take several seconds. Not only that, the other webmaster can do nasty things like serve you a porn image or something really sick, to teach you a lesson about stealing his bandwidth by hotlinking. Or sometimes the site is just deleted, or the url changes, so the image disappears.
But if remote images are transferred to your server, then it is served as a local image in the normal way when viewed, with only the penalty hit of the filter itself (which you would have for any page, regardless whether the page has images in it or not, or whether they are local or remote).
As far as I understand, the performance hit you are referring to is only whilst editing the node.
#2
Everything -Anti- says is true, the hit only comes when you initially create or edit a node, it's actually faster to have the image locally when a node is being viewed.
However I've also confirmed that this bug exists and we should have the option to disable external resizing it if desired.
#3
This patch corrects the behavior. I've committed it to CVS.
#4
#5
Automatically closed -- issue fixed for 2 weeks with no activity.