Please create at your vBulletin board directory a folder called: imgcache and give it the following access rights: CHMOD 777 (read/write/modify to all users)
Create an empty index.html file in this folder to avoid file exploring and direct download on some systems.
Copy the y2kswimgcache.php file to your vBulletin board (forum home) directory.
Close your forum temporarily to the public.
Install the product product-y2kswimagecache.xml to your board (allow overwrite if already present).
The installer will add a table called '[prefix]y2ksw_imgcache' with one field (int ID AUTOINCREMENT) to your board database.
Please note: Although the uninstaller is provided, it is commented out. By removing the table, and reinstalling the plugin later, the cached images would be overwritten, because of the field counter restarting from 1.
By leaving the table in your database, you may reinstall the plugin later without collision problems.
Test the product: New thread, reply, edit. If errors occur (or white pages), make sure your imgcache/ folder has the required access rights.
Reopen your forum to the public.
DONE!
How it works
When a board user opens a new thread or message, or edits an existing one (all advanced, quick-reply and ajax), and pastes an image from all but the local cache directory (or by copy and paste, or by specifying [IMG] tags), upon submission the image is read from the external url and written to the local (server) image cache folder.
This avoids to show a placeholder image when the source link is dead or temporarily unavailable.
The link to the image is accordingly replaced.
The script scans first all image references and creates a table of unique images in the current message. It creates a new database table entry in y2ksw_imgcache for each image, reads the new ID and creates a sequence of new images for each url it happens to be readable, and creates for each successful read an imgcache/<id>.png file.
After this sequence, the files are cached locally and may disappear from their sources without leaving an unreferenced image pointer at the local board.
Known bugs
When an image link contains dynamic data, vBulletin would show the image in preview, but change also the IMG tags to URL.
This causes to loose the reference and the plugin will not attempt to recover. A possible solution is to allow dynamic contents for IMG tags on your board.
Version history
1.0.3.0 2007-08-19 Repaired browser (IE 7) issue for images of a different file extension than the officially recognized types. For this issue, newly cached files have now the *.png extension.
1.0.2.0 2006-08-27 Image caching of signatures ([IMG] tags for signatures must be enabled); added a donation button inside readme.htm for specific user requests, which will help us to keep this product always up-to-date.
1.0.1.2 2006-08-07 Release changes for vbulletin.org
1.0.1.1 2006-08-06 Image size verification to avoid caching of invalid images
1.0.1.0 2006-07-17 Collision-free unique cache ID's
1.0.0.0 2006-07-17 Product creation
I haven,t looked, but if the number of images in a single directory is the concern, you should be able to modify the code to start placing images in a new directory and leave the existing intact. All existing cached images will still be accessible in their original path and all new ones will go to the new directory? Set a reminder to change things again next year ...
Yes, the number of images in a single directory is my concern. I just don't want it to stop working.
Focus2's suggestion in post #150 is for v1.0.3.0 I think, because I saw the 'png' in the code referenced.
I'm not a coder at all, but given direction I can usually find/replace small segments of such and not tear things up.
Thanxx for the answer though, because I was unsure what the MOD would do with old/existing images in the cache. Now at least I sort of know a work-around is possible for v1.0.2.0 if I can find code similar to what Focus2 was referring to. I just don't want to start renaming all my images (from this point forward) to png, if I don't have to.(i.e. the simpler, the better for me)
I'm running v1.0.2.0 on vB3.8.6 and it's run flawlessly since I installed it w-a-y back when.(i.e. vB 3.6) My only concern is how many images can I hold in just ONE directory, before it blows up on me?
And along those lines, is there any way to patch/modify the version I'm running to keep-it-going?(i.e. as Focus2 suggested in post #150 of this thread)
If your system is Linux, it won't blow quickly
The new version does divide the images.
You may try to change the folder from code and create a new one respectively to this change. But, please test it before
Image Cache Details »»
About Developer
Visit Web Site
DB Changes 
No support by the author.
08-17-2013, 02:01 AM
