PhotoQ WordPress Photoblog Plugin 1.5 Brings Tons of new Features to Your Photoblog
PhotoQ is a WordPress plugin that turns your blog into a photoblog. If you have a lot of pictures to post, PhotoQ is your ideal companion. With PhotoQ you can mass upload several photos at the same time thanks to its batch image upload functionality. PhotoQ places uploaded photos in a queue which gives you a convenient way to manage photos to be posted. The plugin then gives you the possibility to have the top of the queue automatically posted at a given interval. PhotoQ was designed to automate and simplify your photo posting process as much as possible. It takes away the hassle of browsing uploaded image files and embedding them into posts: You simply upload your photo to the queue and enter desired information about the photo. PhotoQ then automatically generates the post based on this information.
To make a long story short, “WordPress + PhotoQ = Photoblog”. With the latest PhotoQ version this formula is more valid than ever: PhotoQ v1.5 brings tons of new features to your photoblog. It now includes EXIF support, watermarking, batch editing and multiple image sizes in addition to all the features you have come to love from earlier versions.
An example of a photoblog running on WordPress and PhotoQ can be found at http://www.whoismanu.com.
- Convenient queue-based photo management
- Bulk uploading of photos to your photoblog
- Hassle-free, fully automated posting of photo posts
- Support for EXIF metadata (new)
- Photo Watermarking to protect your photos (new)
- Possibility to add custom metadata to photo posts
- Automatic generation of thumbnails and alternative image sizes (new)
- Updating of all your posted photos with only a few clicks (new)
- Automatic posting through cronjobs
- Integration with Lightbox, Shutter Reloaded and similar libraries/plugins
PhotoQ is somewhat experimental and I consider it nowhere near of being perfect. Still, I think that PhotoQ can be useful to someone who tries to set up a photoblog with WordPress and that’s why I decided to make it public. However, I take no responsibility of what might happen if you choose to use it: You use PhotoQ at your own risk. On the other hand, do not hesitate to ask questions concerning PhotoQ if you get stuck – I would be glad to help.
PhotoQ 1.5 requires at least WordPress 2.6. PhotoQ has been tested successfully under WordPress 2.6 up to 2.6.3.
If you insist in using an older WordPress version, please look for older PhotoQ versions (of the v1.2 branch) that are compatible. Note however that I stopped developing the 1.2 branch, so there will be no updates in this case.
PhotoQ 1.5 requires a web browser with at least Flash Player 9 (note that currently the swfupload script used by WordPress is not compatible with the new Flash Player 10, so if you plan to use bulk image uploads in PhotoQ you should wait with updating your Flash Player until this is fixed) installed and has been successfully tested under Firefox 3 and Safari under MacOSX; Firefox 3 under Windows XP. There is, however, no reason to believe it won’t also work with other common combinations. It would be nice if the first people who test it with other browser/platform combinations could drop me a line or post a short comment. This would allow me to extend this compatibility list.
PhotoQ has been tested with both, PHP4 and PHP5. At the moment PhotoQ only runs on web servers with PHP safe_mode turned off. If your web hosting provider has safe_mode turned on you can try to ask them to turn it of. Most web hosting providers will disable safe_mode for your web page on request. In addition, PhotoQ needs either GD or ImageMagick to be present on the server for image manipulation.
- Get the latest version of the PhotoQ WordPress Photoblog Plugin.
- Unzip the downloaded file, you should end up with a folder called “photoq-photoblog-plugin”.
- Upload the “photoq-photoblog-plugin” folder to your “plugin” directory (wp-content/plugins).
- If you plan to use the automatic posting capability, move the file “photoq-photoblog-plugin/wimpq-cronpost.php” to the same directory as your wp-config.php file.
- You now have to setup a directory on your web server where your image files will be stored (called “imgdir” directory from here on). By default this is the directory “wp-content”. If you do not stick to the default one you have to create your directory now.
- Make sure that the file permissions of the “imgdir” directory are such that the plugin is allowed to write to it (otherwise, uploaded photos cannot be stored).
- PhotoQ also needs a “cache” directory to store temporary files. This is the directory
‘wp-content/photoQCache’. If PhotoQ has the permissions to write to ‘wp-content’ the “cache directory will be created automatically. Otherwise you have to create the ‘photoQCache’ directory now and make sure that the file permissions are such that the plugin is allowed to write to it.
- If your web hosting provider enabled the
mod_securityApache module on your web server, you need to add the following directives to your .htaccess file in order for batch image uploads to work:
<IfModule mod_security.c> SecFilterEngine Off SecFilterScanPOST Off </IfModule>See the Troubleshooting section for more information.
- You are almost done. Just go to the “Plugins” WordPress admin panel and activate the Photoq plugin.
Upgrading from PhotoQ 1.2.6
PhotoQ 1.5 is the most important upgrade PhotoQ has seen so far. A lot has changed behind the scenes, especially also the way in which PhotoQ stores and manages your photos. If you used earlier versions of the PhotoQ WordPress Photoblog Plugin and want to upgrade to version 1.5 it is therefore for once not enough to just copy the new version over the old one. Some additional upgrading steps are required:
- (Optional but recommended) Clear your queue.
- Write down your PhotoQ Settings, some of them might be changed by the upgrade process.
- Save your WordPress database. This is the most important step when upgrading. Really. It ensures that you can rollback if something went wrong. You will find instructions on how to do this on the WordPress Codex.
- Install PhotoQ 1.5 as explained above (thus replace your old PhotoQ plugin folder). Don’t use the WordPress auto update feature.
- Clear the cache of your browser. This makes sure that cached files from your old PhotoQ don’t interfere with the new one.
- Go to “Settings->PhotoQ” and make sure that no errors and warnings are displayed. If you have errors, try to correct them.
- Adjust the “Image Sizes” and “View” settings to your liking. See “Using PhotoQ – The Basics” below for details. Also readjust other settings that were changed in the upgrade process.
- Hit “Upgrade from PhotoQ < 1.5″ under “Settings->PhotoQ->Further Options”. Quickly check whether the information about photos that will be imported makes sense. If it does, hit “Upgrade” and go for coffee. Do not interrupt the upgrading process, it may take a while depending on the number and size of your photos, the power of your server and your PhotoQ settings (for the 150 photos of size about 700×500 pixels on my own blog it took roughly 10 minutes).
- If for some reason the process is interrupted (e.g. because the script times out) and only part of the photos are imported, you can repeat step 8. Only the remaining photos should be shown as photos that will be imported.
- Scan through your blog and check whether everything looks like it should. You can also check under “Manage->Posts” if all your photos got imported. Those that didn’t will show “No Photo” in the “Photo” column. If a photo post did not get imported correctly, you can hit on “Rebuild” in the “PhotoQActions” column to manually rebuild the post.
- PhotoQ 1.5 stores photos in a structure different from earlier versions. Instead of “imgdir/year_month_folders” the photos are now storead according to “imgdir/image_size/year_month_folder”. While upgrading, PhotoQ creates the new folder structure and keeps the old one to give you the possibility to go back if something goes wrong. Once there are no more photos to import you get the option to remove the old folder structure under “Settings->PhotoQ->Further Options->Upgrade from PhotoQ < 1.5″. Note that this will delete the folders listed as well as their content from the server and cannot be undone. Also note that search engines might have indexed your photos and stored their location in the old folder structure. It might thus be wise to keep the old structure for some time at least.
Using PhotoQ – The Basics
Now that you successfully installed PhotoQ, you are ready to go. First you need to setup some of PhotoQ’s settings:
- In the “Settings” panel of the WordPress Administration you should now have a subpanel labeled “PhotoQ”. Go there.
- If you did not stick to the default “imgdir” during installation, you need to specify your choice under “Further Options->Image Directory”.
- If you missed anything during installation or if your web server is missing some requirements you will see a warning at the top. The warning is there for a reason, so if you see it please try to fix it before going on ;-)
- For every photo you post, PhotoQ can automatically generate alternative image sizes. Per default it generates two image sizes called “thumbnail” and “main” in addition to the “original” photo. With the “Image Sizes” option you specify their respective dimensions as well as the desired image quality. Unless you decide to crop the photo PhotoQ always keeps the proportions of the generated image sizes the same as in the original photo. Also note that PhotoQ will not generate images bigger than the original. To fit in with a wide range of photoblog templates, PhotoQ gives you three possibilities to define dimensions:
- “Maximum Dimensions”: you define a rectangle of maximum width and maximum height. Whatever constraint is met first determines the value of the other dimension. If you check the “crop” checkbox, the proportions of the original image are not kept but the photo is cropped to the exact width and height given.
- “Smallest Side”: you fix the smallest side of the thumbnail to some value and have PhotoQ adapt the other side accordingly.
- “Fixed Width”: you fix a maximal width. If your thumbnails orientation is “landscape”, it will have this width. If your thumbnails orientation is “portrait”, its height will be adjusted such that it matches the height of a photo with “landscape” orientation.
- “Original Size”: the photo is not resized.
- If you think that the three provided image sizes “original”, “thumbnail” and “main” are not enough for you, you can add further image sizes by entering a name under “Name of new image size” and clicking on “Add Image Size”.
- If you are all confused now, I suggest that you leave the default options for now and play with the other options later. Also forget about the “Watermark” and “Hide original folder” options for now, they will be explained later.
- PhotoQ uses the two built-in WordPress template tags
the_excerpt, that are also present in any regular WordPress post. Under “Views” you tell PhotoQ what to place in the content part of a post and what to place in the excerpt. For now we stick to the “Single Photo” option. The dropdown menus show the image sizes that are available and that we defined in the steps before. I suggest that for now you choose “main” for
the_contentand “thumbnail” for
the_excerptto place your main image in the content part and a smaller thumbnail version in
- In the section for
the_contentyou have an option to “Include photo description in post content”. If you check this option, the description of the photo is included in the content part of the post, just after the photo. The description is then placed in a <p> tag with class name “photoQDescr” to allow for easy styling via CSS. If you do not check this option, the description is only placed in a custom field with name “photoQDescr”. In short: if you do not know how to or do not want to tweak themes, check this option. If you know how to access a custom field from a theme and want greater flexibility, don’t check this option.
- “Further Options->Enable Batch Uploads”: Allows you to toggle the batch upload capability on and off.
- Skip the other options for now and click on “Save Changes” to, well, save the changes you made so far.
- Note that whenever you change a setting that affects the way a photo post looks (e.g. changing an image size, changing a view, changing the watermark), PhotoQ will update all previously posted photos to maintain a consistent look throughout your blog. Depending on the settings you changed, the number and size of your photos (“do I really need to upload a twelve megapixel original photo to my blog? wouldn’t a downsized version do the job as well?”), this update process may take a while. So once you click on “Save Changes”, do not interrupt the process, rebuilding all your photos might take a while. If a photo post does not get rebuilt properly, you can rebuild it manually by clicking “Rebuild” in the “PhotoQActions” column under “Manage->Posts”.
Now comes the fun part, you are ready to manage your photo queue:
- In the “Manage” panel of the WordPress Administration you should now have a subpanel labeled “PhotoQ”. Go there.
- As you have not yet uploaded any photos the queue is empty. To upload a photo click the button “Add photo to queue”.
- I think that the upload process is pretty self-explanatory. If you have batch uploads enabled, click on “Select photos…”. You can then choose several photos (via the standard cmd-click on MacOSX and ctrl-click on Windows) in the “Select Files” dialog box that pops up. The selected photos are queued for mass upload. Once the dialog box is closed, uploading starts automatically. Once the upload is completed you are presented with a panel where you can enter information that is common to all the photos you just uploaded. This batch editing is especially useful for entering tags and categories. Once you entered the common information (if any) click on the “Enter Info” button. You now get the chance to add information that is specific to a single photo. Choose the categories for the photo, add a title, a short description and some tags if you want. If the title is too long you might want to enter a shorter slug. Sometimes it is nice to see a photo in detail when entering information about it. PhotoQ easily allows this: if you click on a thumbnail, the corresponding photo will open in all its beauty in a new window. Once you entered the desired information, hit “Save Batch Info”. Don’t worry all the information can still be changed at a later stage. If you have batch uploads disabled, the process is similar only that you choose the file to upload via the “Browse” button.
- If everything went smoothly, you should now see the photos you just uploaded in the queue. You can add other photo to the queue if you like.
- Each entry in the queue can be edited by clicking on “Edit”. This gives you the possibility to alter all the fields.
- Entries in the queue can be easily reordered via drag-and-drop.
- You can remove photos from the queue by clicking on “Delete”.
- To publish the photo at the top of your queue to your photoblog, hit “Post top of queue”. PhotoQ then automatically generates a post according to your settings and the information you entered.
- The entry at the top of your queue should now be removed from the queue and appear as a new post on your photoblog.
- Check the result directly on your photoblog or in the “Manage->Posts” section of the WordPress Administration panel.
More on Views and Themes
The laziest option when it comes to WordPress themes for PhotoQ is to use the ready-made iQ2 photoblog theme. iQ2 comes with full PhotoQ integration out-of-the-box and instructions on how to configure PhotoQ. iQ2 might also serve you as a convenient starting point if you decide to build your own theme.
The rest of this section explains how to use PhotoQ with existing themes and what you need to know should you decide to build your own. PhotoQ only relies on custom fields and standard WordPress template tags like
the_excerpt. It should therefore not be too difficult to use virtually any WordPress theme with PhotoQ. Often you might not even have to adapt the theme at all, just choosing the correct PhotoQ settings might be enough.
With the Views Setting, you define which image size and what information PhotoQ places in the content and what it places in the excerpt of a post (we’ll call content and excerpt views from here on). In your theme you can then use the
the_excerpt template tags to show the respective view. We are now going to have a look at the different view options:
- “Single Photo”: A single photo is placed in the view. You choose the image size to be used from the drop-down menu. The corresponding <img> tag has the CSS class attribute “PhotoQImg”.
- “Photo Description”: For the content view you can inline the photo description. If you choose to do so, the description is not only stored in the “photoQDescr” custom field but a <p> tag containing the description and having a CSS class name “photoQDescr” is added after the single photo (image link, respectively).
- “Exif Meta Data”: For the content view you can also inline EXIF information. If you choose to do so an unordered list with selected EXIF tags is displayed at the end of the post. See the EXIF section for more information.
With every post, PhotoQ also stores a number of custom fields that you can use in your templates. We have already seen some of them like “photoQDescr”. To display a custom fields in your theme you can for example use the WordPress function get_post_meta. Example:
<?php echo get_post_meta($post->ID, 'photoQDescr', true); ?> Here is a list of custom fields provided by PhotoQ for every photo post:
- “photoQDescr”: Contains the description of the photo.
- “photoQPath”: Contains the path of the original image. Never remove this, it is crucial for the functioning of PhotoQ.
- “photoQImageSizes”: Contains an associative array (key = name of image size) with info on the image sizes. This allows easy access to the different image sizes from a template. For every image size there are the following fields: ’imgTag’, ‘imgUrl’, ‘imgPath’, ‘imgWidth’, ‘imgHeight’. I guess the names are pretty self explanatory. To output the <img> tag of the “main” image size you could do something like:
$sizes = get_post_meta($post->ID, 'photoQImageSizes', true); echo $sizes['main']['imgTag'];
- “photoQExif” and “photoQExifFull”: See below under “EXIF Support”.
- One custom field per “Meta Field”, see below under “Meta Fields”.
PhotoQ now has built-in support for displaying EXIF metadata added to your photos by your digital camera. Whenever you upload a photo, PhotoQ learns about EXIF tags present in the photo. For every photo posted, PhotoQ stores two custom fields along with the post.
- “photoQExif”: This custom field contains an unordered list with EXIF information. You can select which EXIF tags to include in the list by checking the corresponding checkboxes under “Settings->PhotoQ->Exif”. When selecting tags to include you can see a value in parentheses next to each tag. These values are example values found in one of the photos you uploaded and are simply there to give you a better idea of what the corresponding EXIF tag is about. The resulting unordered list is ordered alphabetically by tag name and has the following structure allowing for easy CSS styling:
<ul class="photoQExifInfo"> <li class="photoQExifInfoItem"> <span class="photoQExifTag">tag name</span> <span class="photoQExifValue">tag value</span> </li> </ul>
- “photoQExifFull”: This custom field contains an associative PHP array (with keys corresponding to EXIF tags) containing all the EXIF data present in the photo. You can use this in your theme if you wish to have more flexibility than with the unordered list in “photoQExif”.
To protect your photos, PhotoQ gives you the possibility to add a watermark. Watermarking settings are found under “Settings->PhotoQ->Watermarking”. I think that the options are quite self-explanatory:
- Upload an image file to be used as watermark.
- Select position, opacity and margin from edges.
- For each image size defined under “Settings->PhotoQ->Image Sizes”, decide whether it should show the watermark or not via the “Add watermark to all images of this size” checkbox.
- Note that watermarks are not applied to the original images you uploaded. If you want to show a watermarked version of your photos in original size, you have to create another image size where you check both the “Original Size” radio button and the watermarking checkbox.
- If you don’t want people to have access to your non-watermarked original photo, you can check the “Hide original folder” option under “Settings->PhotoQ->Image Sizes”. PhotoQ then places original photos in folder with a name that is hard to guess instead of the standard ‘original’ folder, hiding your original photos from unwanted access.
If you want to add more information to your photo posts than just the title and description provided by default, you have the possibility to do so via “Meta Fields”. Assume you want to associate each photo with the place where the photo was taken:
- Go to “Settings->PhotoQ->Meta Fields” in the WordPress Administration Panel.
- Click “Add Meta Field”.
- Give it a name, e.g. “place” and hit “Add Field”.
- For every photo you upload you will now have an additional field called “place” where you can enter the desired information. Once posted, the field is saved as a custom field with the same name.
- The list of Meta Fields can be edited by clicking on “Rename” or “Delete”.
- The three options “Upon Add/Delete/Rename” define whether changes you make to a Meta Field are also applied to the corresponding Custom Field of already posted photos. Example: Assume you already posted 20 photos and only then decide to add a new Meta Field called “place”. If you check “Upon Add, Add to already posted as well”, a Custom Field named “place” (with an empty value) will be added to all of the already posted photos as well.
Automatic Posting Via Cronjobs
PhotoQ allows you to have the top of your queue posted at regular intervals. This is especially useful if you go on a vacation and still want your photoblog to go on. Just fill up the queue before you leave and have PhotoQ do the rest. To set up automatic posting, you need to do the following:
- Set the frequency at which the posts should occur. This can be set in “Settings->PhotoQ->Further Options”.
- Remember where on your web server you saved the file “wimpq-cronpost.php”.
- Setup a cronjob to execute “wimpq-cronpost.php” at your desired interval. Don’t worry, most often your webhost will set this up for you if you tell him/her the URL of your “wimpq-cronpost.php” file and when and how often you want the cronjob to be executed.
- Upon each execution of “wimpq-cronpost.php”, PhotoQ checks whether the last post occurred more than X hours ago (where X is the value you set in the PhotoQ Options panel). If so, the top of your queue is posted automatically.
- It might thus be a good idea to set the “PhotoQ Cronjob Frequency” slightly lower than the interval of the actual cronjob. E.g., assume you want a post once a day. Setup your cronjob to execute the “wimpq-cronpost.php” file once a day at the desired time and set the “Cronjob Frequency” in the “PhotoQ Options” to “23h”.
- Note: If your webhost does not allow you to setup your own cronjob you might be able to do something similar with a WordPress plugin such as WP-Cron (I have not tested this, so should you be able to make PhotoQ work together with such a plugin, please drop me a line).
- A neat alternative solution to the above has been brought to my attention by Phil from halfmad.com. If your webhost does not allow cronjobs you can alter the WordPress index.php file in the following way:
<?php /* Short and sweet */ define('WP_USE_THEMES', true); require('./wp-blog-header.php'); ob_start(); require('./wimpq-cronpost.php'); ob_end_clean(); ?>This then emulates a pseudo-cron executed every time a user visits your website. Thanks Phil, for pointing this out.
The following options are not explained elsewhere in this post. They can all be found under “Settings->PhotoQ->Further Options”.
- “ImageMagick Path”: Here you can set the path to the ImageMagick convert binary on your webserver. If you set this path, PhotoQ will use ImageMagick instead of the GD library. A note shows you whether the path you entered is correct. Depending on the amount of memory assigned to PHP and the size of your photos, you may have to configure ImageMagick for PhotoQ to work properly.
- Import photos uploaded via FTP. The option “FTP Upload” lets you enable importing photos from a specified directory on your server. Once enabled, you get a new button “Import from ftp directory…” when adding photos to your queue. A click on the buttons leads to the FTP import screen where you can choose which photos from the ftp directory PhotoQ should import and where you can also enter common info for the photos to be imported. Note that depending on whether PhotoQ has write permissions to the ftp directory it will copy (if it doesn’t have write permission) or move (if it does) the selected files from the ftp directory to the queue.
- Publish several photos from the queue at once. In the PhotoQ management panel (“Manage->PhotoQ”) you will now find a second post button to the left of the “Post Top of Queue…” button. With the “Second Post Button” option you can specify how many photos are published at once if you hit this button.
- Lists of categories can be folded away throughout the plugin which is convenient if you deal with a lot of categories. The “Fold Categories” option lets you decide whether you want category lists to be open or closed by default.
- “PhotoQ Post Author”: Posts generated by PhotoQ will be published under this author.
- “PhotoQ Default Category”: Here you can choose the default category for PhotoQ posts.
- “Deleting Posts: Delete image files from server when deleting post”: If not checked, image files associated with a post are left on the server if you delete the post.
- “Show thumbs in post management admin panel”: Allows you to see a preview of the photo in the list of already posted posts. You can also define the size of the thumbnail you would like to see there.
Troubleshooting – Help it doesn’t work!
Here is a short checklist in case something doesn’t work as expected. Please go through this before asking me for help.
- Did you check the requirements?
- Clearing your browser’s cache can work wonders.
- Did you check the PhotoQ options? Especially, are the paths to your “imgdir” correct?
- Are you sure “cache” and “imgdir” file permissions are set correctly?
- Do you have other plugins installed? If so, disable all other plugins and check whether it works now. Should you find any incompatibilities with other plugins please let me know. So far I know about the following plugins that are not compatible with PhotoQ: “Lighter Admin Drop Menus v2.3″.
- Does it work with batch uploads disabled? If not, try to make it work with batch uploads disabled first.
- “I get a HTTP 403 error message when trying to do a batch upload?” Most probably, your web hosting provider enabled mod_security on your web server. Batch upload makes use of Flash and Flash is known to send malformed http headers which are rejected by mod_security. The only solution seems to be to turn off mod_security by adding the directives given above to your .htaccess file. Anyone having a better solutions is most welcome to let me know about it.
- “I am getting a ‘Warning: set_time_limit() has been disabled for security reasons…’ or similar”. Some web hosting providers limit the execution time of PHP scripts and do not allow you to change it. PhotoQ tries to remove the limit because if you have a large batch upload, it might take some time. If you get warnings like the one above, you can comment the line
set_time_limit(0);in the beginning of the whoismanu-photoq.php file by replacing it with
//set_time_limit(0);Huge batch upload jobs might then however sometimes be aborted if they take longer than the maximum execution time allowed by your web hosting provider.
- “In the admin section I get light blue images with a red warning like ‘… All attempts to create GD image source failed …’ instead of the thumbnails”. You hit the memory limit with the GD library. This leaves you with three options in order of preference:
- configure ImageMagick (see under “More Options”)
- increase memory allocated to PHP by adding something like
php_value memory_limit 16M(and where you replace 16M with the amount of memory you want to allocate) to your .htaccess file.
- upload smaller, down-sized images.
- “When I click on ‘Select Photos’, nothing happens!” Probably you are using Flash Player 10. Batch uploads in WordPress 2.6 are not compatible with Flash Player 10. See the requirements for more information.
If nothing helps, don’t hesitate to ask – I would be glad to help. In order to be able to help you, I need to at least know the versions of WordPress and PhotoQ you are using, your browser/platform combination, whether it works with batch uploads disabled and of course the potential error message you are getting. If you get an error message of any kind, it might also be helpful to know what you were trying to do just before you got the error message. But please check the points above before writing about a problem. At least double-check the requirements. It will save me (and you!) a lot of time that is better spent improving PhotoQ than looking for imaginary problems. Thanks.
Support PhotoQ – Help to Make PhotoQ Better
You like PhotoQ? Here’s what you can do to support PhotoQ and help making it better:
- Any comments, suggestions, bug reports, feature requests, contributions to future versions, compatible themes, etc., etc. are highly appreciated. Any help to improve PhotoQ is more than welcome. I cannot fix/improve anything if I don’t know what is wrong.
- You use PhotoQ? Why not give PhotoQ credit through a backlink on your website?
- You think PhotoQ is the greatest plugin out there? There are many ways to promote PhotoQ: Tell your friends, or even tell the world by writing a blog post, …
- You made a photoblog using PhotoQ? Let me know. I will soon include a list of the best PhotoQ based blogs.
- You made/saved money thanks to PhotoQ? Due to repeated request I set up a donate link to give you the chance to give some of it back ;-)
- 13.11.2008 – 1.5.3: Fixed problem with identical post dates when batch posting.
- 04.11.2008 – 1.5.2: Introduces FTP uploading, batch publishing, category folding and nicer default titles. Cache folder is no longer inside plugin folder to prevent problems with auto upgrade. Database changes include new id for the main table and WordPress charsets and collations for all PhotoQ tables. inline description moved from <p> tags to <div> to prevent problems with the WYSIWYG editor.
- 24.09.2008 – 1.5.1: Repacked PhotoQ with new folder structure on WordPress plugin directory to overcome auto upgrade problems. Root plugin directory is now “photoq-photoblog-plugin” instead of “whoismanu-photoq”.
- 22.09.2008 – 1.5: Major Update, most code rewritten. New libaries used: phpThumb and Exifixer. New features include: multiple image sizes, exif, watermarking, easy update of posted photos.
- 15.07.2008 – 1.2.6: Compatible with WordPress 2.6.
- 06.05.2008 – 1.2.5: Category handling adapted to WordPress 2.5.1. Two new settings to choose default category and author of PhotoQ posts.
- 22.04.2008 – 1.2.4: Bugs fixed: Problems with filenames containing special characters; Disappearing Media Library update links in Write panel caused by PhotoQ.
- 16.04.2008 – 1.2.3: Bugs fixed: PHP4 compatibility restored, no more lost settings; Now compatible with localized WP versions, no more “swfu not defined”. Now also compatible with IE7; SWFUpload updated to 2.1.0b2.
- 04.04.2008 – 1.2.2: Bugs fixed: Ajax queue ordering did not work if dashes present in filenames; Header of queue no long sortable; Correct authentication of Ajax queue manipulations; Cookies no longer sent during Ajax calls.
- 15.03.2008 – 1.2.1: Fixes a bug that could under some conditions provoke empty width and height attributes
- 09.03.2008 – 1.2: Compatible with WP 2.5. Migrated batch uploads to SWFUpload 2 for greater stability. Ajax Queue Management. Lightbox Integration. Runs on Reusable Options.
- 25.11.2007 – 1.1.5b: PhotoQ is now able to truly resize photos. It now also integrates with existing themes more easily because of the new option to directly include the description in the post content. Category display bug when updating queue has been corrected.
- 07.11.2007 – 1.1.4b: PhotoQ is now again retro-compatible with WordPress versions that do not have built-in tagging support. Only update if you use a WordPress version prior to 2.3.
- 04.11.2007 – 1.1.3b: PhotoQ now supports WordPress’ native tag handling introduced in WordPress 2.3. Please read this post to see how to import tags from meta fields to the new structure.
- 20.10.2007 – 1.1.2b: changed require_once statements so that the plugin also runs on web servers that don’t like relative paths in these statements. Update only if you encountered problems with version 1.1.1b.
- 17.10.2007 – 1.1.1b: “Largest Side” image/thumb-size option is now a “Smallest Side” option. “Largest Side” can still be mimicked by setting both values in the “Maximum Dimensions” option equal to the desired value.
- 14.10.2007 – 1.1b: first major update. Features mass uploads via SWFUpload. New options for image/thumbnail sizes. Better photo preview in admin section. Enhanced security due to use of wp_nonces. Under the hood, big parts of the code have been restructured.
- 07.10.2007 – 1.0.2b: patch to make it compatible with WordPress 2.3.
- 22.01.2007 – 1.0.1b: fixed a bug that caused PhotoQ to handle some paths and urls improperly. Anyone wanting to use PhotoQ should update to this new version.
- 11.01.2007 – 1.0b: first public release.
Thanks to all the PhotoQ users who help to keep up my motivation to continue this project. Thanks for all the kind comments and helpful bug reports. Special thanks to all the people who volunteered to beta test this update. Many thanks to the guys at http://swfupload.mammon.se/. Without their great SWFUpload script, there would be no batch uploads in PhotoQ. Sames goes for James Heinrich who wrote the phpThumb Library and Jake Olefsky who wrote the Exifixer library. Without their great work PhotoQ would not be where it is today.