Version: 1.0.5, by y2ksw
Developer Last Online: Feb 2023
Category: Administrative and Maintenance Tools -
Version: 4.x.x
Rating:
Released: 11-06-2010
Last Update: 02-13-2011
Installs: 300
DB Changes Uses Plugins
Additional Files Translations
No support by the author.
This vBulletin 4 product imports external images in your posts from external servers or paths into a specific path, normally your forum's image folder.
Differently than the previous product Image Cache for vBulletin 3.x., it parses the posts at regular intervals for new images and replaces the external references in the background. Also, instead of using only a single folder, it creates folders for years and months, making it much easier to handle large quantities of images. The source and destination image URL's are stored into database, too, avoiding unnecessary duplicates.
It moves and optionally converts images from one place to another. It is a handy tool in order to keep your images local to your forums.
Version 1.0.4 is temporarily in BETA stage until the users have confirmed the newly requested features.
Version 1.0.5 is still in BETA stage. It adds a new bunch of additional features, one of which allows you to test your mathematical understanding ... and a few other to fine-tune CURL and socket timeouts, and resizing on the fly of too large images. If you don't know what these options do, please leave them at their default values.
Well, one idea could be to attempt to download the image prior to examine its size, but then eventually you have other problems, such as streams, which could never finish.
You could always limit the size of a file to be uploaded to be <8Mb (or whatever the nominal size of the image is)?
It sounds easy, but isn't.
It would require a raw socket connection and manual reading of the file, and stop reading if it has reached 8 MB. Then however, it would be possible to add a timer, too, and abort slow files as well. Also, it would allow to examine the file header before downloading the whole file and thus discard no-image files efficiently. But it would take a bunch of code and yet more options.
Then we remove the CURL code, but we'll loose the redirect features and SSL. Thus, it'll fail with Facebook, Imageshack, Google images, just to name a few.
How about an option to save to a cloud service such as OneDrive as a CDN and pull the images from there?
You may use on Linux an external service as a mount for saving, for example curlftpfs or sshfs, and a redirect for showing those images. All other methods (such as using PHP ecc) go too far off the road, because there is never one system identical to another. I have had solutions like the above, but in the end I came up with Dropbox for some cases, and for all the rest, a larger local storage
Import External Images Details »»
... and a few other to fine-tune CURL and socket timeouts, and resizing on the fly of too large images. If you don't know what these options do, please leave them at their default values.
About Developer
Visit Web Site
DB Changes 
No support by the author.
03-10-2015, 01:47 PM
