Version: 1.00, by Steve St.Lauren
Developer Last Online: Mar 2013
Version: 3.0.8
Rating:
Released: 07-28-2004
Last Update: 09-09-2004
Installs: 111
No support by the author.
Having trouble with large images in [img] or <img src> tags in your posts causing your templates to go too wide causing a horizontal scroll bar for all posts? I have many users that attach large images to their posts either through vB img or html img src tags. In vB2 it wasn't that much of an issue because it only caused their post to go wide causing a horizontal scroll bar. In vB3 it causes all the posts on that thread to go to that width.
This hack uses the img src width="xx" tag to resize the picture to whatever max size you wish. It also adds a link to the full size image in it's original location and retains any extra formatting the user puts in the tag. In addition it checks to see if the picture actually exists and if not show "Image link is broken" where the picture would have been. Please click install if you install it and please give feedback so I can go full release with it if it's bug free.
Updated on 07/30/2004 - R0.9
Updated on 08/06/2004 - R1.0 - Identical to R.9, no need to upgrade just changing to full release from beta
Updated on 08/10/2004 - R1.1 - Added max_imgsize to the 2nd section of code (and removed global max_imgsize line from both), some users had problems with the code grabbing the max_imgsize from the first section - this fixes that.
Updated on 09/09/2004 - R1.2 - fixed problem with duplicating the resize notice when using wysiwyg editor
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
This hack saved us a lot of trouble thanks so much!! It's working perfectly. I do have a question however. At the end of your install notes you say:
"That's it. Set the max_imagesize at the beginning of the each of the large edits and that will be your max image size."
Where can I set the max_imagesize?
Look in the hack text file and you'll see two instances of "$mag_imgsize=560;" - just change the 560 in those two instances to whatever size you want. Before the first one it says " // set max_imgsize to the max size you want pictures to be"
I installed this hack it worked nicely but for all our signatures that involved images
they were replaced with a message that said "Image link is broken"
any ideas what might cause this, is there a way to turn this off for signatures?
Where are those signature images coming from? The server they are on may be restricting your server from opening a file from their server which will cause that error. Give me a link to a page showing a signature doing that and I will take a look.
I heard that "client side" would be faster. Can we mod this hack to load the html page as its resizing the images.
I seen some sites that says "loading images" then the photo appears. Can we implement something like that. just so the page loads first then the photos.
I really love this hack over the others but I do understand people removing because of the lag.
No, there's no way to do that because the server has to have loaded the images so that it knows the size of the image so that it can decide if it needs to be resized or not. If it needs to be resized then it generates the html code to make that resize happen on the client side - if the html was already loaded there wouldn't be any way to modify that. The only other option would be to resize all pictures to the size you specify but that will make images smaller than that size look horrible. If you did that there would be no need to check the image size.
This hack was so promising , and was my favorite. I don't know what happened, but 2 days after this hack was installed, it took longer and longer to load pages with images, so like many others i had to remove it and made another one work 100% (minus the text at the bottom as i liked about this one)
Thanks though. I hope someday this can be revised to be more friendly to larger image forums.
This hack was so promising , and was my favorite. I don't know what happened, but 2 days after this hack was installed, it took longer and longer to load pages with images, so like many others i had to remove it and made another one work 100% (minus the text at the bottom as i liked about this one)
Thanks though. I hope someday this can be revised to be more friendly to larger image forums.
The more images you have on a post the longer it will take because every image has to be loaded. If there are images on a server that is down or that the server blocks access to it will take even longer because it will have to hit the timeout before continuing. If you have a forum where people put LOTS of images in each thread then it isn't going to work out well for you until I (or someone else) have time to add the optimization recommended by BRC2 above. It'd take me most of a day probably and I just don't have the time right now .
The more images you have on a post the longer it will take because every image has to be loaded. If there are images on a server that is down or that the server blocks access to it will take even longer because it will have to hit the timeout before continuing. If you have a forum where people put LOTS of images in each thread then it isn't going to work out well for you until I (or someone else) have time to add the optimization recommended by BRC2 above. It'd take me most of a day probably and I just don't have the time right now .
Don't sweat man, you got a top family priority, I hope to have your experience someday with my wife to be
It seems to work great, but on some large images, i get, Image link broken. If i got to edit the post, the images are there, but wont show on the forum. Any ideas?? Maybe it cant handle large images?
Images are 1280 x 960 and were already posted before the hack. I tried to edit the post and redo the links but still no good.
????
Actually, its just images that this one user is posting. Some of smaller images coming from cardomain, they show Image Link Broken too.
Well, I rehosted the images myself as a test and they came up fine. It was just with this one user. Large or small images, but its fixed now and working great.