Veqa Image Resizer - Version 1.5
Released June 24, 2007
About | View Demo | Features | System Requirements | Version Changes | Get Free Updates | License Agreement
FAQ stands for "Frequently Asked Questions". A FAQ is generally used to find out a answer to potential common questions. On this page you will see a list of questions. Simply click on a question link in the listing below to find out its answer. If the answer does not help you, you may alternatively contact us for support.
General
Could you give me a clear idea what the software actually does?
What does "on the fly" mean?
What do you mean by it having an "interface"?
How do I find out if I have the necessary requirements?
Why does no image show?
How can I make this work along with different software?
May I modify this software?
How do I get generated images at the original image file location instead of by the script?
Features
What about getting images by URL?
What about saving images as files?
What about image cropping?
What about image bordering?
Can you keep proportion and assign a maximum width and height?
ImageMagick MagickWand for PHP
What is ImageMagick MagickWand for PHP?
Is ImageMagick MagickWand for PHP included in the software?
Is ImageMagick MagickWand for PHP free?
How do I know if I have ImageMagick MagickWand for PHP?
Do I have to have ImageMagick MagickWand for PHP?
GD
What is GD?
Is GD included in the software?
Is GD free?
How do I know if I have GD?
Do I have to have GD?
How do I make GD's image quality/resolution better?
Veqa Image Resizer resizes Web images on the fly by parameters in the script's URL. For example, the text in bold would be the parameters: http://www.yoursite.com/veqaimageresizer/?image=images/myimage.jpg&size=200. By this, images do not have to be actually saved as a file - it simply gets it by the script's URL and automatically generates the image on the fly. This makes having different versions of the same image a lot easier to manage.
It is a term used to express something dynamically created. The creation is not stored for future use (ie, a computer file), so it is instead created at every moment it is called. For computer use, this would mean for a lesser need in disk space, however, a greater need in processing.
The interface is the form page shown on the script. This makes it easier to get the correct parameters and values for the URL of your generated images. However, it is not necessary to have in order for the software to work. The interface may be disable if needed, but you would then have to manually figure out the URL locations yourself.
What you can do to see if the Web server you are on meets the requirements of the software is to upload a PHP file that retrieves PHP information. To make this, create a new file and name it as "phpinfo.php" and edit the file inputting the following code:
<?php phpinfo(); ?>
Save the file and then upload it to your root Web site directory and call the script at - for example - http://www.yoursite.com/phpinfo.php .
On the page of the "phpinfo.php" script, check if the following are true:
If all of the above are true, then the software should meet the system requirements for your Web server.
This most likely means that it is not finding the image for the location you gave it. A common problem in relation to this could be due to a simple slash character (/). You must make sure that any ending slashes in the location are correct in the configuration and via the script's image parameter of the URL.
As default, the configuration has an ending slash for its image directory location - actually, there's nothing else other than that slash. If you were to make a more specific location for it, you should do - for example: "/stuff/myimages/". But you do not want to do "/stuff/myimages" - notice no ending slash.
However, either of those locations could work, but not both of them. For example, for the script's image parameter of the URL if you input "/myimage.jpg", then the directory "/stuff/myimages" could work. And if you do it as the standard method with no starting slash as "myimage.jpg", then the directory "/stuff/myimages/" could then work. Although, "/myimage.jpg" with the directory as "/stuff/myimages/" might work also, but technically it is incorrect as it comes up with having double slashes before the file.
Other than slashes, other problems could simply be other kinds of location mistypes, such as misspelling, or just the plain wrong directory. You should always just take some decent time to review and check if your locations are clearly accurate. But also, a more unique problem could be .htaccess source conflictions. You should as well check any .htaccess files under the related directories along with the software's directory and see if you spot any problems with them.
We're sorry, we may not have knowledge to support you on this, as we can only provide support based on our software only.
Yes. However, please read the License Agreement for more details.
If you want the actual images with their locations intact and not showing the standard script URL parameters of the software, you would have to use the mod_rewrite tool of Apache HTTP Server. If you have Apache as your Web server and mod_rewrite enabled, you should be able to do this.
To give an example on how this is done, you would first make a file called ".htaccess" having that placed in the root directory of your Web site. Here is an example of what to input:
RewriteEngine on
RewriteRule ^myimages/(.*)/(.*)/(.*).jpg$ veqaimageresizer/?image=$1/$2/$3.jpg&size=medium
This rewrites the URL "http://www.yoursite.com/veqaimageresizer/?image=*/*/*.jpg&size=medium" to be accessed via "http://www.yoursite.com/myimages/*/*/*.jpg" - the (*) character would serve as random values. This would be how to keep your image files intact with their original locations.
You can learn more about Apache mod_rewrite here:
http://httpd.apache.org/docs/2.0/misc/rewriteguide.html
We're sorry, this feature is not included. Veqa Image Resizer only gets images by Web server directory locations.
We're sorry, this feature is not included. Veqa Image Resizer only generates images on the fly and does not save them.
We're sorry, this feature is not included.
We're sorry, this feature is not included.
We're sorry, this feature is not included. However, you can be able to limit the width and height sizing to a specific amount so the image won't display above that amount for the purpose of saving bandwidth of unneeded, excessive, large images. For example, in the online demo of the product, sizes are limited to 1280 x 1024.
It is image drawing software like GD, but not originally included in PHP distributions. Due to this, it is a lot less popular than GD, but it surely makes up for it in its vast amount of features and great image drawing quality. ImageMagick MagickWand for PHP is our personal recommendation over GD. We've done a lot of work in image drawing programming, and overall, ImageMagick MagickWand for PHP stands out to us to be better than GD through our experience.
However, ImageMagick MagickWand for PHP is not as well documented on the Web as GD is. And installation of it of course as well is more trouble than GD would be, since GD originally comes with PHP. Finding a Web server installed with ImageMagick MagickWand for PHP would be a rare occurance, but most should have GD.
Visit http://www.imagemagick.org/ to find out more details.
No. It supports ImageMagick MagickWand for PHP, but does not actually have the software.
Yes.
See "How do I find out if I have the necessary requirements?".
No. Alternatively, you can use GD instead. ImageMagick MagickWand for PHP is only our recommendation.
GD is a popular PHP image drawing software that is originally included in most PHP distributions.
Visit http://www.boutell.com/gd/ or http://www.php.net/gd to find out more details.
No. It supports GD, but does not actually have the software.
Yes.
See "How do I find out if I have the necessary requirements?".
No. Alternatively, you can use ImageMagick MagickWand for PHP instead. ImageMagick MagickWand for PHP is our recommendation.
The image quality is most noticeably less with the GD image drawing of JPG images. The best quality you can get is if ImageMagick MagickWand for PHP is used instead of GD.
However, to increase the image quality with using GD, you may modify the following code in "index.php" of the software:
imagejpeg($image);
And change that to:
imagejpeg($image, '', 100);
The value of "100" is the quality value. The quality ranges from 0 being worst to 100 being best. "75" is the default quality value when this is not set. However, setting it to "100" is the best you can get for JPG quality in GD - and ImageMagick MagickWand for PHP can still output better quality.
Also, the file size may become an issue due to this. For example, if the quality is set at "100" for JPG images in GD, the file size may double the amount of the original image file size (ex. from 4224 bytes changing to 11024 bytes). In ImageMagick MagickWand for PHP the file size may only be increased by a little bit (ex. from 4224 bytes to 4567 bytes), and at the same time, looking better than GD. The file size for the default quality value of JPG images in GD is more less though (ex. from 4224 bytes changing to 3272 bytes), but of course, not that great of quality.
But it's up to you on how to have this. In most cases the file size shouldn't be much to worry about - unless you're trying to save up bandwidth.
