how about crop, crop postion & zoom? any vulnerablilities?
1.) cropping and zooming will be in one of the next releases
2.) it’s 100% secure:)
Awesome im developing a premium wp theme for release here in a month or two so may consider inclusion after some testing and comparison with other scripts currently emerging
so how exactly does this work? I don’t see any documentation in the download. Does it prevent wordpress from changing any images?
it resize images through the WP functions and store them in the directory, listed in the first post. It also create a unique hash for every image, so you can be sure that there will be no collision. And it clear the resized images every 7 days, so you can have always the fresh one
This won’t work on multisite - check your getRelativePath() function.
Also, since you rely on getimagesize() function to verify the images, it would be imperative to add a @ to it.
Another thing, hashing could be made more unique, although i’m not sure what it does exactly? I thought when you mentioned about it on the Aqua Resizer thread you were referring to hashing the cropped image instead of the original image?
Oh, and running through the whole fresh dir to check for expired images for every instance of image resizing is not really a good idea. You could probably make the check to be separate from the class, and instantiated at a scheduled period, if you ever want to go that route at all.
after doing some deeper testings I can recommend this script without any restrictions. Easy to implement, very fast Image scaling (did a re size for about 40 large scales images 1920x1080 down to 45x45 which takes a heartbeat to complete).
Any plans for future update with the script? I really love your work, hope it stays free. I’m going to test this on an actual server right now i’m testing it locally hope it wont cause any problems. I’ll give my thoughts on how it goes later.
After testing, found out that it won’t work with multisite, it seems that it can’t create the dir called freshizer, but instead it created the folder in wp-content/blogs.dir/2/files/freshizer so when i fetched the url of the image it returned nothing cause the file was stored in a different dir.
But it works perfectly with the regular wordpress installation, few questions that’s been bothering me since the wordpress’s function add_image_size creates a copy of the image in a different size what difference does it make if this script also does the same thing except it stores the image in the folder freshizer, i thought those images were created temporarily then later automatically deleted after a certain time like timthumb does.
thank you for your interest. I will fix the multisite bug when I will have a time Anyway I’m now heading to final exams at my university, so I will not be available about a week or so
thank you for your interest. I will fix the multisite bug when I will have a time Anyway I’m now heading to final exams at my university, so I will not be available about a week or so
Additionally this url is safe, because it baypasses any rewrite rule on server.
The only thing I’m not sure about, is what happens when sub blogs are not in sub folders, but in sub domains… it should work, because I think that when you select sub domains for blogs the only thing that changes is the rewrite rule in the .htaccess file, so the files are always in the same folders.
To make it clearer, this is how I use my functions to use timthumb with mu installation:
This function builds the image URL, if is a sub blog it changes the URL to the correct one, otherwise if it’s the main blog ($blog_id == 0) it doesn’t do anything.