PhotoQ WordPress Photoblog Plugin v1.1b – Now Including Batch Uploads

Update: PhotoQ v1.6 is a newer version of the same plugin but offering more features. Please check out and download the new version instead of this one, you won’t regret it.

This is the first major update of PhotoQ, a WordPress photoblog plugin that makes your photoblogging life easier. PhotoQ is most suited for “one photo a day”-style web pages i.e., classical photoblogs.

This new version makes maintaining a photoblog even easier. Instead of uploading your photos one by one you can now mass upload several photos at the same time thanks to the new batch 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. In short, 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.

An example of a photoblog running on WordPress and PhotoQ can be found at

Feature List

  • Queue-based photo management
  • Batch upload photos to your photoblog
  • Hassle-free, fully automated posting of photo posts
  • Possibility to add custom metadata to photo posts
  • Automatic thumbnail generation
  • Automatic posting through cronjobs


PhotoQ WordPress Photoblog Plugin - Screenshot “Mass Upload”
PhotoQ WordPress Photoblog Plugin - Screenshot “Enter Info”PhotoQ WordPress Photoblog Plugin - Screenshot “Queue”PhotoQ WordPress Photoblog Plugin - Screenshot “Options”


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.


The latest version of PhotoQ has been tested successfully under WordPress 2.3.1, 2.3 and 2.2.3. However, it should run without problems under most WordPress 2 versions. One exception is the WordPress 2.0 branch: if your WordPress version is 2.0.x, you can use PhotoQ but only with batch uploads disabled (this has been tested with WordPress 2.0.11). The reason is that PhotoQ’s mass upload functionality makes use of the WordPress JavaScript loader that was only introduced in WordPress 2.1. If you are able to successfully run PhotoQ under other versions, it would be nice to let me know.

From version 1.1b on, mass uploading in PhotoQ makes extensive use of JavaScript and Ajax. So I guess from here on, I also have to include a list of tested browser/platform combinations. PhotoQ has been tested under Firefox 2.0/MacOSX and Safari/MacOSX. There is, however, no reason to believe it won’t also work with common browsers under Windows. 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.

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.

Version History

  • 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.


  1. Get version 1.1.5b of the PhotoQ WordPress Photoblog Plugin.
  2. Unzip the downloaded file, you should end up with a folder called “whoismanu-photoq-plugin”.
  3. Open this folder, you should see a folder called “whoismanu-photoq” and a file called “wimpq-cronpost.php”.
  4. Upload the “whoismanu-photoq” folder to your “plugin” directory (wp-content/plugins).
  5. If you plan to use the automatic posting capability, save the file “wimpq-cronpost.php” in the same directory as your wp-config.php file.
  6. You now have to create a directory on your web server where temporary image files, corresponding to the photos in your queue, will be stored. By default this is the directory “/wp-content/qdir” (called “qdir” directory from here on).
  7. Make sure that the file permissions of the “qdir” directory are such that the plugin is allowed to write to it (otherwise, uploaded photos cannot be stored).
  8. Once posted, photos are moved from “qdir” to another directory. PhotoQ organizes posted photos by year and month. Photos posted in January 2007 are consequently moved to an automatically generated directory with name “2007_01″. We call the directory that contains these “YYYY_MM” subdirectories “imgdir”. By default “imgdir” equals “/wp-content”. If you want to use some other directory as “imgdir”, you have to create it now.
  9. Make sure that the file permissions of the “imgdir” directory are such that the plugin is allowed to write to it (otherwise, the “YYYY_MM” directories cannot be created and posted photos cannot be moved there from “qdir”).
  10. If your web hosting provider enabled the mod_security Apache module on your web server, you need to add the following directives to your .htaccess file in order for batch uploads to work:
    <IfModule mod_security.c>
    SecFilterEngine Off
    SecFilterScanPOST Off

    See the Troubleshooting section for more information.
  11. You are almost done. Just go to the “Plugins” WordPress admin panel and activate the Photoq plugin.

Using PhotoQ – The Basics

Now that you successfully installed PhotoQ, you are ready to go. First you need to setup some of PhotoQ’s options:

  1. In the “Options” panel of the WordPress Administration you should now have a subpanel labelled “PhotoQ”. Go there.
  2. The first two fields tell PhotoQ where to look for the “qdir” and “imgdir” directories. If you did not stick to the default options during installation, you need to specify these directories here.
  3. For now skip the “Meta fields” options
  4. For every uploaded photo, PhotoQ automatically generates a thumbnail. With the “Thumbnail size” option you specify its size. PhotoQ always keeps the proportions of the generated thumbnail the same as in the original photo. To fit in with a wide range of photoblog templates, PhotoQ gives you three possibilities to define the size of the generated thumbnails:
    • “Maximum Dimensions”: you define a rectangle of maximum width and maximum height. Whatever constraint is met first determines the value of the other dimension. You can also use this option to mimic the “Fixed height” or “Fixed width” options of earlier versions of PhotoQ (e.g. to mimic “Fixed height” you can set the “height” to the desired value and the “width” to some huge value such as “99999″. For “Fixed width” you of course do the same but the other way round). The “Largest Side” option of earlier versions can be mimicked by setting “width” = “height” = “Largest Side”.
    • “Smallest Side”: you fix the smallest side of the thumbnail to some value and have PhotoQ adapt the other side
    • “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. Note that this is not the same as “Fixed width” in earlier versions of PhotoQ (check the comment under “Maximum Dimensions” to see how you can mimic the “Fixed width” option of earlier PhotoQ versions).
  5. “Image size” specifies the size in which uploaded photos are shown on your photoblog once they are posted and works essentially the same as “Thumbnail size”. If you check the option “Resize only in web browser”, the actual image file stays untouched i.e., it is not resized. The new image widths and heights are only used as “width” and “height” attributes of the HTML <IMG> tag and resizing is thus left to the web browser. If you don’t check “Resize only in web browser”, PhotoQ resizes the photo according to the “Image size” settings. Last but not least, you have the option to keep the original image size by checking the corresponding checkbox.
  6. If you are all confused now, I suggest that you set “Thumbnail size” to “Fixed height: 80px” and “Image size” to “Keep original image size” for the time being and play with the other options later.
  7. You might want to check “Deleting Posts: Delete image files from server when deleting post”, otherwise the image files associated with a post are left on the server if you delete the post.
  8. There are two more new options in PhotoQ v1.1. “Show thumbs in post management admin panel” allows you to see a preview of the photo in the list of already posted posts. “Enable Batch Uploads” allows you to toggle the new batch upload capability on and off.
  9. As of version 1.1.5b, there is another option “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 “photo_description” to allow for easy styling via CSS. If you do not check this option, the description is placed in a custom field with name “descr”. 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.
  10. Skip the cronjob options for now and you are done. Click on “Update options” to save the changes.

Now comes the fun part, you are ready to manage your photo queue:

  1. In the “Manage” panel of the WordPress Administration you should now have a subpanel labeled “PhotoQ”. Go there.
  2. As you have not yet uploaded any photos the queue is empty. To upload a photo click the button “Add photo to queue”.
  3. 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. You then have the possibility to add more photos to the upload queue, delete individual photos from the upload queue, clear the entire upload queue, or upload the queued photos. Once the upload is completed you can start entering information on the uploaded photos by clicking on the “Enter Info” button that should have appeared.
    Choose the categories for this 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.
  4. 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.
  5. Each entry in the queue can be edited by clicking on “Edit”. This gives you the possibility to alter all the fields and also to reorder your queue by changing the “Position” value.
  6. You can remove photos from the queue by clicking on “Delete”.
  7. To publish the photo at the top of your queue on your photoblog, hit “Post top of queue”. PhotoQ then automatically generates a post where the photo is placed in the content part and the thumbnail is placed in the excerpt. The description is stored in a custom field called “descr”. You have thus access to the photo and the thumbnail in any of your templates via the template tags the_content and the_excerpt, respectively, and you can access the description via the custom field “descr”. Note that as of version 1.1.5b you also have the option to directly include the description in the content part of the post in a <p> tag with CSS class name “photo_description”.
  8. The entry at the top of your queue should now be removed from the queue and appear as a new post on your photoblog.
  9. Check the result directly on your photoblog or in the “Manage->Posts” section of the WordPress Administration panel.

Meta Fields

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:

  1. Go to “Options->PhotoQ” in the WordPress Administration Panel.
  2. Click “Add Meta Field”.
  3. Give it a name, e.g. “place” and hit “Add Field”.
  4. 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.
  5. The list of Meta Fields can be edited by clicking on “Rename” or “Delete”.
  6. 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:

  1. Set the frequency at which the posts should occur. This can be set in “Options->PhotoQ->Further Options”.
  2. Remember where on your web server you saved the file “wimpq-cronpost.php”.
  3. 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.
  4. 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.
  5. 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”.
  6. 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).
  7. A neat alternative solution to the above has been brought to my attention by Phil from If your webhost does not allow cronjobs you can alter the WordPress index.php file in the following way:
    /* Short and sweet */
    define('WP_USE_THEMES', true);
    This then emulates a pseudo-cron executed every time a user visits your website. Thanks Phil, for pointing this out.

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.

  1. Did you check the requirements?
  2. Did you check the PhotoQ options? Especially, are the paths to your “qdir” and “imgdir” correct?
  3. Are you sure “qdir” and “imgdir” file permissions are set correctly?
  4. 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″.
  5. Does it work with batch uploads disabled? If not, try to make it work with batch uploads disabled first.
  6. “Everything seems to work but even if I enable batch uploads, I only get the option to upload one file at a time!” Is JavaScript enabled in your web browser?
  7. “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.
  8. “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.
  9. 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 version of wordpress 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.

Making PhotoQ 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.

Also, should you decide to make a photoblog using PhotoQ, please let me know. I would be more than happy to let the world know by linking to your site.


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 Manu from for the helpful comments and suggestions. Many thanks to the guys at Without their great SWFUpload script, there would be no batch uploads in PhotoQ.

Comments (108)

  • 1

    Weblog Tools Collection » Blog Archive » WordPress Plugin Releases for 10/16 says:

    [...] PhotoQ makes your photoblogging life easier by allowing batch uploads and nearly-automated posting. [...]

  • 2

    Fernando Costa thinks:

    Hi Manu,

    I have a question for you… Is there any way to set photoQ to make thumbnails giving it a value for the smallest side of the image instead of the largest one? That would be really great for what I`m trying to do.

    Thank you very much…

  • 3

    Cody thinks:

    I have just started using this plugin at and I have to say it’s great. My only suggestion, though, is some way to create new categories when adding pictures through the queue. As it is, when you come to the enter info page after uploading the pictures, you can only select existing categories but you can’t create a new category on the fly. It’s nothing that important, but it would be useful.

  • 4
  • 5

    whoismanu says:


    thanks for your comment. with the current version of photoq this is not really possible. if you only have photos of a fixed width/height ratio, e.g. 3:2, you could of course achieve this by setting largest side to 3/2*smallest_side.
    until now it did not occur to me that it could make sense to fix the smallest side of a photo. however, it would not be a big deal implementing it, so if you can give me more details and convince me ;-) that this would be a useful feature, i might think about it and replace largest side (which can anyway also be achieved by setting both width and height in the maximum dimensions setting to the same value) with smallest side.

  • 6

    whoismanu says:


    great that you chose to use photoq! you are absolutely right. i also sometimes wished i had this functionality, especially in the beginning when i started setting up my blog. so this is already somewhere on my to-do list but it was one of the features that didn’t yet make it into this version. thanks for the input.

  • 7

    Fernando Costa says:

    Thanks for your reply! That’s exactly why I was looking for this feature. You see, I’m making a website with images of various sizes and aspect ratios, but I want to make cropped thumbnails so they are all square, just for my design’s sake. I figured that if I could set a smallest side of x, and put the thumbnail in an x by x div with hidden overflow that would do the trick… If you could help me with this one I would REALLY appreciate it… thanks a lot man..

  • 8

    whoismanu says:


    interesting argumentation. well, i guess in this case the cleanest solution would be to have the thumbnails themselves cropped (which will be a bit more complicated but i will definitely put this one on my radar), what do you think? in the meantime the smallest side option might be a temporal solution. I’ll let you know…(no promise on the time-frame, however ;-))

  • 9

    Fernando Costa writes:

    It would be really great if the thumbnails were cropped but it does indeed sound more complicated. That temporal solution sounds nice though… maybe a tweak I could add myself directly to the plugin’s code… Well man, nothing left to say but thank you very much, let me know if you think of something ;)

  • 10

    whoismanu says:


    you can download the new version 1.1.1b which has the smallest side option instead of largest side. as mentioned above, largest side can still be obtained through the max. dimensions option. happy photoblogging…

  • 11

    BlogBroker » WordPress Plugin Releases for 10/16 writes:

    [...] PhotoQ makes your photoblogging life easier by allowing batch uploads and nearly-automated posting. [...]

  • 12

    Chris writes:

    I am getting a blank options page. No errors. I made sure safe_mode is off. The PhotoQ link shows up in Options, it just gives me a blank body/page under the options header. Any ideas?

  • 13

    whoismanu says:


    no idea. are you sure you uploaded all the files to your webserver? especially, is there a file with path panels/options.php in the whoismanu-photoq folder on your webserver? what about the photoq manage page? does it show up? what version of photoq are we talking about, 1.1b or 1.1.1b? What version of WordPress are you using?

  • 14

    Chris thinks:

    1.1.1b and I extracted the zip on the server, the panel/options.php file is there. I am using v2.3 of wordpress. After I activated, I went to options, then clicked on PhotoQ in the admin section, that is where I’m getting the blank page. Hope this helps, I’m not ruling out I’ve missed something simple.

  • 15

    whoismanu says:

    We finally fixed Chris’ problem. It looks like his server didn’t like php require or include statements with relative paths. changing all require_once('folder/file.php'); statements to require_once(dirname(__FILE__).'/folder/file.php'); did the trick. so i guess it would be a good practice for all plugin authors to adopt to the above practice to make plugins more robust to things like this. the new version 1.1.2b of photoq does exactly this. thanks chris.

  • 16

    Wordpress Themes and Plugins 1 | Ehab Mehedi writes:

    [...] Visit the Plugin Page [...]

  • 17

    parisxv writes:

    I tested your plugin and it worked.
    But it created a new directory at the root called 2007/10.
    I now want to do a reular post with an image.
    Now, all my image uploads in regular posts are directed to this new directory instead of wp-content/uploads/2007/10
    I deleted the new directoty. desactivate photoq.
    still the path is to the new directory.
    So I have to change manually the path to my images in my posts or they won’t show.
    Any idea ?

  • 18

    whoismanu says:


    the year/month folders are created in the directory that you define in the imgdir option. by default this is not root but wp-content. you can also define this to be wp-content/uploads if you want.
    the imgdir path should not affect the upload path of your regular posts. regular uploads and photoq normally coexist without problems.

    i can however think of one thing. photoq uses wordpress’ built-in upload functions. before uploading something it thus changes the upload path to imgdir and after the upload it changes it back to what it was before. now, the only explanation i have is that when you first tried photoq it crashed for some reason and never reached the point where it changes the directory back. however, you tell me that photoq worked for you. did it always work, or did you have some problems in the beginning?
    anyway, you can see and change the current upload path in ->options->misc in your wordpress admin area. just set it back to what it should be. hope this helps.

  • 19

    parisxv thinks:

    Hi Manu,
    Thank you. You saved my life.

    The field in upload options was blank, and I just had to re-enter “wp-content/uploads” and save. Everything is back to normal.

    I don’t remember why I had changed it.

    Sorry for the confusion and thanks for the help.

    By the way, congrats for your plugin but I was looking for something different : I would need a batch upload plug in for multiple images in one post.


  • 20

    Evan thinks:

    This is a great plugin! Thanks for making it. I was wondering if anyone has gotten it to work with the theme viewfinder grain? From what I can figure out, the images that are uploaded aren’t recognized in the post unless they are uploaded with YAPB, but I would really love to use photoq if possible… Thanks again!

  • 21

    whoismanu says:


    thank you very much for your comment. photoq uses the standard wordpress content field to store the main photo and the excerpt to store the thumbnail version. so to wordpress, once posted, posts posted via photoq or via the standard mechanisms look exactly the same. from what i know, yapb on the other hand stores photo information associated with a post slightly differently and you thus need the yapb specific functions to retrieve the information. the theme you are trying to use does exactly this. so if you don’t use it in conjunction with yapb it does not work.

    what can you do? well, if you know some php it shouldn’t be too difficult to change the theme such that it uses standard wordpress functions like the_excerpt and the_content. otherwise, you could also bug the theme author and ask whether he might be willing to release a photoq compatible version (;-)). finally you can of course look for other themes that use the standard wordpress functions mentioned above or you could even make your own theme (hey, this could be a good occasion to get started ;-) ).

    i know that photoq is at the moment a bit short on the “themes side”. i might want to invest some time soon to look around and see what themes can easily be used with photoq and how. if anyone has some suggestions concerning this, is developing or has developed a theme, please let me know.

  • 22

    craig says:

    I was wondering if a future version of photo-q was going to have lightbox/greybox support.

  • 23

    whoismanu says:


    good question. my answer will somewhat go in the same direction as my answer to the comment just before (comment no 20).

    i am actually not yet sure whether things like this are the job of photoq. the thing is that right now photoq is “silently” working in the background. it gives you a convenient way to post your photos. decide to disable photoq one day (no idea why you would do this ;-) ), and your whole blog will still look the same. now to me things like lightbox are more theme related, they deal with how your posts are presented. consequently they should be implemented by the theme you are using. as i see it today, it seems to be good practice to separate the two things. as soon as i’ll start to intermingle the two by providing advanced templating functions in photoq, i’ll also start to create a strong dependence on photoq (ok, i know this might be smart from a business perspective ;-)) because themes that work with photoq will then no longer work without.
    but as i said, i have not yet decided, so things like this are still an open question. i am also open to all the input you people might have on this subject. is it important to you that we stick to the modular “philosophy” we have today? or should we sacrifice some of it for more features? or is there even a way to have both?

    hope anyone understands what i am babbling about…

  • 24

    Evan writes:

    hey manu,

    thanks for the response. I actually contacted the author of the theme to see what he thinks and I am waiting for a response. If i come up with anything I will let you know. thanks again and really this plugin is great, I really wish I could use it in my theme…

  • 25

    わーどぷれすっ! » PhotoQ writes:

    [...] PhotoQ WordPress Photoblog Plugin v1.1b – Now Including Batch Uploads [...]

  • 26

    whoismanu? photoblog - PhotoQ Wordpress Photoblog Plugin Update 1.1.3b - Now Supporting Wordpress tags says:

    [...] uploading your photos to the PhotoQ queue. For more details on PhotoQ please check out the post “PhotoQ WordPress Photoblog Plugin v1.1b – Now Including Batch Uploads”. If you already used PhotoQ and entered tags by using its Meta Fields functionality, please read on [...]

  • 27

    Monika writes:

    Hi thanks a lot for this plugin.

    “Great” is the simplest word for it. :-)
    Because you give us a wonderful simple method to post photos and to feed search enginees ;)

    It looks like you are a man who works proactively and follow a line of thought.

    kindly regards

  • 28

    Matt Bee writes:

    can’t…get.. it… to… work:

    File is empty. Please upload something more substantial.
    Manage PhotoQ – Enter Info

    WordPress database error: [Table 'pbaste.wp_photoq' doesn't exist]
    SELECT * FROM wp_photoq WHERE q_edited = 0 ORDER BY q_position

    using: WP2.011, php4, mysql4.

  • 29

    whoismanu says:


    i am not sure which WP version you are using: 2.0.1 or 2.1.1? if it is 2.1.1 you should urgently do a complete fresh install because WP 2.1.1 is considered dangerous. Also if you use 2.0.1 i would upgrade, as it is quite old.

    Concerning your errors: what version of photoq are you using? it might actually be that the latest photoq version (1.1.3b) is no longer compatible with WP versions < 2.3. Honestly, i completely forgot to check this; i thus obviously also did not update the requirements section of this post after the last photoq update. sorry about this, i will do it as quickly as possible.

    Now independent from this, in your case the database tables needed by photoq do not seem to be created. If you update to WP2.3 and still encounter similar problems, could you please look at your database using something like phpmyadmin and tell me what tables there are?

  • 30

    whoismanu says:


    just noticed that you are most likely using 2.0.11. didn’t know that this stable legacy branch of wordpress existed. sorry for my ignorance. i will check whether the plugin is compatible with it.

  • 31

    whoismanu says:


    i just upgraded PhotoQ to a new version (1.1.4b) that is somewhat compatible with WP 2.0.11. Somewhat meaning that it will run but you cannot use mass uploads (in fact you need to disable them in the photoq options panel), because they need the wordpress javascript loader that is only available in WP 2.1. Sorry, that’s all i can offer you unless you upgrade your WordPress install to a newer version.

  • 32

    Pete in Midland thinks:


    works great and looks good … but now I have a question. Is there a way that I can direct the output to a specific page instead of the general blog? I’d like to have a photopage, without having to set up a separate photoblog.


  • 33

    zenandjuice says:

    great plugin ! I’m trying it out on my blog, and everything works great, except it’s not publishing the description in the post.

    is this normal ? how do i get the description to appear ?

    thanks !

  • 34

    whoismanu says:


    the description is stored in custom field called ‘descr’. An easy way to access its value (and the way i do it on my page) is to use the get custom field values plugin.
    once you have the custom fields plugin installed you can print out the ‘descr’ custom field by placing the following piece of code in the template file (e.g. single.php) at the place where you want it displayed:

    < ?php echo c2c_get_custom('descr'); ?>

  • 35

    whoismanu says:


    well it is possible, as you can see, i do it on my webpage ;-). but the only way i see to do it right now is to tweak and customize your templates. so you will have to have some knowledge about the wordpress templating system and know some php. the way i do it is to discriminate between photoblog posts and text based posts based on their category. i have a root category ‘photos’ for all photoblog posts. and another root category ‘blog’ for all text based posts. now, in the single.php and category.php templates i then decide on which root category a certain post has and display it accordingly. so what you see when you visit is the category page for the category ‘photos’, if you visit, what you see is the category page for the ‘blog’ category.

  • 36

    thm thinks:

    Thanks for the wonderful plug-in! I haven’t launched my photoblog yet–I neeed to build the Queue up a bit–but PhotoQ is fantastic.

    A couple of things I learned while getting the cronjob posting to work, at least on Bluehost serving, which might be useful to others:

    First, it’s a good idea to put wimpq-cronpost.php in the same directory as wp-config.php. I have wp-config.php in a subdirectory of public_html, and mistakenly put wimp-cronpost.php in public_html, and the way my php is configured, the subdirectory wasn’t in php’s search tree and it couldn’t find wp-config. Putting wimpq-cronpost.php in the photoblog subdirectory, with wp-config.php, solved that problem.

    Second was that I modified wimpq-cronpost.php so that the first line was:
    #! /usr/bin/php -q
    because otherwise it was being interpreted as a bash script.

  • 37

    whoismanu says:


    thanks a lot for your helpful comment. let us know when your queue is full, we would be glad to see the result ;-)

  • 38

    Monika thinks:


    one of my friends told me that he can’t use your plugin with Safari /Mac .. Do you know this problem?

    He can see the link:Add photo to..
    he can choose a photo and than he isn’t able to do anything..

    no photo no link nothing

    kindly regards

  • 39

    whoismanu says:


    i just tested it once more with the latest version of safari (3.0.4) on mac os x (10.4.11) and it worked like a charm. so, no problem here. i guess your friend has another problem somewhere. does it work when batch uploads are disabled?

  • 40

    Monika writes:

    Hi whoismanu

    I have disabled this feature and hope it would work.

    I’ll come back with my feedback. ;)



    ( oh! your comments underline my typos .. beautiful!
    But it can’t underline my grammar mistakes…….



  • 41

    Monika writes:



    batch uploads are disabled and your plugin works like a charm for him.

    do you know why?

    batch uploads is a nice feature but not absolut necessary, but I would like to know why?

    thanks for your patient ;)


  • 42

    PhotoQ Wordpress Photoblog Plugin Update 1.1.5b thinks:

    [...] This post only covers changes in version 1.1.5b. For a full picture and more details on PhotoQ please check out the post “PhotoQ WordPress Photoblog Plugin v1.1b – Now Including Batch Uploads”. [...]

  • 43

    Dade thinks:

    i get this error when i went to the cron file Fatal error: Call to undefined method PhotoQ::cronjob() in /home/dnaksha5/public_html/ on line 5

  • 44

    whoismanu says:


    is your wimpq-cronpost.php file in the same directory as your wp-config.php file (see also thm’s comment no. 36 just above)?
    from your error message i conclude that you use v1.1.5b but just to make sure: can you check whether you have the file whoismanu-photoq/classes/photoq.php on your server?

  • 45

    Dade says:

    yes the file is in the same directory as the wp-config.php file and no i dont have the classes folder at all

  • 46

    Dade writes:

    hey ok i got it working i just redownloaded the package and tested it and it works thanks for bringing that to my attention

  • 47

    Dade writes:

    hey there ok well when i run the wimpq-cronpost.php i get this

    Testing Cron JobCron frequency: 4
    Last post: 1199134630
    Current time: 1196299988
    Diff: -787

    i run the cron job every hour and set the photoq to post every 4 hours however its not posting any suggestions

  • 48

    whoismanu says:


    am i right with my assumption that you have no posts posted so far? the output you see tells you the difference in hours between your last post and the current time. if this difference is bigger than your frequency setting, the post will be posted. Now in your case it is negative and i noticed that the cronjob function in photoq doesn’t check whether there are any posts. so if you don’t have posted anything, i guess you get a wrong value for last post (in your case in the future) and this is why it doesn’t work. Until the next version that will fix this, you can just post your very first post manually via the “post top of queue” button under manage->photoq. hope this solves your problem and if it does sorry for this bug and thanks for pointing this out.

  • 49

    Dade says:

    hey there ya nothing has been posted yet so i just do the manual way which is still fine i love the batch import feature it makes LIFE WAAAAY EASIER ;) but im glad i could help out by finding a bug ;) thanks for the great plugin and i cant wait for the update ;)

  • 50

    Dade writes:

    oh sorry i also had a request perhaps the buttons add photo to queue clear queue and post top of queue is it possible to have those buttons located at the top of the page? when i have alot of photos in queue i hav eto scroll down to the bottom it would be cool if that could be moved up thanks again

  • 51

    Dade says:

    would it also be possible to have a switch to not show thumbnails when i goto manage>photoq because i have over 1000 pics in queue and it takes quite a while to load that page

  • 52

    Googlebot writes:

    Hello, I’m Googlebot

  • 53

    thm thinks:

    thm here again; I’ve launched my photoblog which is happily running with PhotoQ: it’s the Matthew Picture of the Day which is pictures of my now 4-month old son. All of his grandparents live thousands of miles away and they all really like being able to see a new picture of their (first) grandson each day.

    One other interesting behavior I’ve noticed (I’m still using 1.1.2b): Even though cron runs every day at 6am, give or take a few seconds, it’s always reporting the difference between posts to be 22 hours. It was easy to fix this; I just set the frequency to 20 hours and it works fine. I don’t know if this has anything to do with the fact that the time zone I use for WordPress is different from the one that the host computer uses.

    A sample cron output:
    Testing Cron JobCron frequency: 20 Last post: 1197291609 Current time: 1197370808 Diff: 22

  • 54

    whoismanu says:


    congratulations on your site (and your son of course, both look lovely ;-) ). another thank you for linking to photoq.

    thanks also for your input on the cronjob feature. you are probably right and there are definitely some issues with the accurateness of the posting time. there were also some other bugs with this feature (cf post 47 above) that are already fixed. the fixes will be included in the next update. so in this respect you will gain nothing by updating to 1.1.5b. if you are happy with what you got, i propose you stay with your version for now.

  • 55

    houserocker says:

    thanks so much for this great and easy to use tool!!!

  • 56

    Idetrorce says:

    very interesting, but I don’t agree with you

  • 57

    d’orange » Blog Archive » nuevos plugins writes:

    [...] como ahora entre otras cosas, las imagenes que saco las voy publicando en flickr a saco, y en mi blog al estilo “una imagen al dia” (un photoblog, vamos) voy a probar un par de plugins para agilizar el trabajo y hacerme la vida mas facil. estos sonYAPB photoQ  [...]

  • 58

    MilleSabords writes:

    Hi! I’m trying to test PhotoQ on WP2.3.1.
    The install semms OK but i get the same “PhotoQ Options” screen, even if i go to Manage/PhotoQ menu.
    So i’m not able to have an “Add Photo” Button.
    The URL are:
    when i use Options/PhotoQ
    when i use Manage/PhotoQ
    my WP is in French. Dis i miss something ? Thanks

  • 59

    John says:

    Great plugin but is there a way to import images already on the server into the que??

  • 60

    whoismanu says:


    right now there is no import/update feature available. it is however planned for one of the coming versions.

  • 61

    whoismanu says:


    hmm, the normal url for the manage/photoq page is:

    so there is definitely something wrong there. i’ll try to check the french version. did you check whether you have the same issues with the english version?

  • 62

    Erik says:

    Hi. This seem to be a great plugin. I’m having trouble because PHP Safe Mode but my ISP will take care of that.

    My question is if you would like to share the theme you are using for your own photo blog. Especially the functionality of clicking on the image to view the previous one (and also put the small thumbnail links in the bottom.)

    Kind regards, Erik

  • 63

    Phil says:

    Just wanted to say how much I like this plugin, works a treat and great setup and config instructions (makes a change for a WP plugin!).

    I’m hoping you continue to develop it – really is fantastic :-D

  • 64

    Phil says:

    A couple of requests after using this for a while:

    1. Separate post image size and actual image size. So you could have a size of say 400×500 on your homepage, which links to a full sized imaged.

    2. image linking – clicking the picture takes you to the post.

    I really can’t think of any others at the moment, works a treat!

  • 65

    Ed writes:

    Hi there, just wanted to point out that PhotoQ doesn’t seem to work with Firefox. Kept getting “File is empty. Please upload something more substantial. This error could also be caused by uploads being disabled in your php.ini.”

    Drove me crazy until I tried IE!

  • 66

    Phil writes:

    Hmm I’ve only ever used Firefox with this plugin and without any issues Ed!

  • 67

    whoismanu says:


    thanks a lot.

    concerning your two points above, 2. is already implemented but not yet published because i am still thinking about how to best implement 1. ;-)

    (so right now it only links the thumb to the image, but i guess many people would like to have at least one more image of a different size, so i prefer to wait with an update until i have this ready)

  • 68

    whoismanu says:


    thanks for your comment. like phil i have never ever used photoq with any other browser than firefox (except for some testing of course) and yes, it works like a charm!!! ;-)

    which version of firefox? which version of flash player are you using?

  • 69

    whoismanu says:


    hope you got rid of the safe mode by now :-). i am sorry but i am somewhat reluctant to share my theme, hope you understand this. i’ll see however what i can do about the thumbnail links. you’ll hear from me.

  • 70

    Site update - plugins and theme info at .:Halfmad:. writes:

    [...] Whoismanu PhotoQ – Allows me to queue posts and bulk upload photos for posting later. [...]

  • 71

    Phil thinks:

    Hi Whoismanu, Just thought I’d let you know that I’ve got this plugin working without cron jobs on my site (my hosting package doesn’t allow them).

    I just use pseudo-cron, follow the setup instructions and edit the index.php in the root of my site, so each time a visitor looks at the site it checks to see if it should run the fake cron job.

    My index.php now looks like this:

    PS – I’m suppressing any output from pseudo-cron just incase :-)

    It’s working for me so far without any issues.

  • 72

    Niels says:

    Very nice plugin!
    But, is there a way to store and use the exif data of a photo?

  • 73

    Niels writes:

    Ok, adding the exif was quite easy afterall :)

    in the table ‘wp_photoq’ add in the end a field called ‘q_exif’.

    in photoq.php in the upload_photo function:

    below ‘$file = wp_handle_upload($_FILES['Filedata'], $overrides);’

    $exif = exif_read_data($file['url'], 0, true);
    $ser_exif = serialize($exif);

    add the fields and the value to the inser query
    $wpdb->query(“INSERT INTO $this->QUEUE_TABLE (q_title, q_imgname, q_position, q_slug, q_descr, q_tags, q_exif) VALUES (‘$title’, ‘$filename’, ‘”.($q_length+1).”‘, ‘$slug’, ‘$descr’, ‘$tags’,'$ser_exif’)”);

    in the post_next() function below the ‘insert meta (custom fields)’ part:

    //insert exif data
    $result = $wpdb->query(”
    INSERT INTO $wpdb->postmeta
    VALUES (‘$post_ID’,'exif’,'”.$wpdb->escape($photo_post->q_exif).”‘)

    And at last in the template where you want to see the exif data

    $exif is now a array, you can do with it what you want.

    for the c2c_get_custom call you need the ‘get custom field values’ plugin
    just like to get the description.

  • 74

    Niels says:

    hmmm forgot to add this is the above:

    And at last in the template where you want to see the exif data

    $exif = unserialize(c2c_get_custom(‘exif’));

    $exif is now a array, you can do with it what you want.

    for the c2c_get_custom call you need the ‘get custom field values’ plugin
    just like to get the description.

  • 75

    whoismanu says:


    thanks for sharing this with us. i might integrate something like this in one form or another in a future version. but i guess you already did the biggest part of the work for me, so thanks again for your input ;-).

  • 76

    Niels writes:

    Your welcome!
    I’m happy to do it.
    If there are other stuff I add or change I will let you know. The other way around, if you need someone else for developing, you know how to reach me.

    Ow grmbl, just noticeed that i replyed this exif custom update in an old post.

    I copy/paste it in the newest one at this moment.

  • 77

    Alex writes:

    WordPress database error: [Table 'b20170_wpress.wp_photoqfields' doesn't exist]
    INSERT INTO wp_photoqfields (q_field_name) VALUES (‘Location’)

    WordPress database error: [Table 'b20170_wpress.wp_photoq' doesn't exist]
    SELECT q_imgname FROM wp_photoq WHERE 1

    how to fix this?

  • 78

    Josh thinks:

    I installed the plugin and the upload process works fine for about a half hour and then when I go to add a photo to the queue it gives me a directory box with the ‘browse’ button next to it instead of the search link. Then once the file is selected, I click the upload button that now appears and it gives an error.

    So once it changes to the filename box, ‘browse’ button and ‘upload’ button it doesn’t work. It’s wierd though since it does work after a fresh install for a few batch uploads, then changes to this wierd configuration for no reason.

    Any input would help since this is a very easy to use plugin but seems to be buggy on this installation.


  • 79

    whoismanu says:


    could you please give some more details? when do you get this error? wp version? photoq version? thanks.

  • 80

    whoismanu says:


    weird indeed. so what is this installation? can you give some details? also, what system/browser combination are you using?

  • 81

    Monika says:

    Hi Alex I have the same error, because the directory was not writeable. I delete all fieles, upload new – make the directory writeable and the install was find without any error.


  • 82

    Amir writes:


    Thanks for this awesome plugin. I am able to upload a batch of photos and when I click the “Enter Info” button once the uploads appear to be completed, I just get a blank page that says “Manage PhotoQ – Enter Info” and no images actually upload to my server.

    I am running WordPress 2.3.2
    ‘wimp-conpost.php’ is in the correct DIR and the queue and image directories are both pointed at the correct folders with the permissions set so they can be written to. I also did the .httpaccess work around. Can’t get it to work. Any ideas?

  • 83

    Amir thinks:

    In addition, it appears that our server is not able to create the photoq table in our database. What do we have to do on our end to allow your plugin to create the table? Or how can we manually create it? Thanks so much.

  • 84

    Alex thinks:

    1.1.5b – plugin
    2.3.2 – WordPress
    I made copy of plugin to /Plugins, activate plugin and when I opened “Options -> PhotoQ”
    I got: “WordPress database error: [Table 'b20170_wpress.wp_photoqfields' doesn't exist]
    SELECT * FROM wp_photoqfields WHERE 1 ORDER BY q_field_name”

  • 85

    Alex writes:

    Monica – i’ll try again, but before I tested in on Denwer – suite for webmasters on local machine under Windows, so no write permission problems should be

  • 86

    Thème WordPress pour photoblog : my photo blog | WordPress tuto thinks:

    [...] plugin indispensable est PhotoQ de Manu. Pas très facile à installer et à configurer (créer un répertoire /qdir – utiliser le [...]

  • 87

    tabela thinks:

    just noticed that you are most likely using 2.0.11. didn’t know that this stable legacy branch of wordpress existed. sorry for my ignorance. i will check whether the plugin is compatible with it.

  • 88

    Veerasundar says:

    Good tool. Even, I would like to try it on my photo blog.

  • 89

    Monika writes:

    ich habe WP 2.5 im Test

    Unable to move cyx.thumbnail.jpg, posting aborted.

    alle Einstellungen wie vorher dennoch kommt dieser Fehler, den ich mir nicht ganz erklären kann..wirst Du Dein Plugin WP 2.5. ready machen?


  • 90

    Monika writes:

    ah..das neue WP 2.5 macht beim Hochladen keine Thumbs, sondern ich finde

    xyz-176×132.jpg als kleine Thumbs im Ordner–kann es daran liegen?


  • 91

    whoismanu says:


    yes, if wordpress 2.5 comes out i will also make the plugin compatible. but right now i have not yet undertaken any steps in this direction, so honestly at the moment i have no clue as to what errors you might get using photoq with wordpress 2.5.

  • 92

    Monika says:

    Hi your plugin try to find a thumb with the word “thumbbnail” but wp 2.5 doesn’t create thumbs with this word–the name of the new thumb is incompatible to your plugin -so your plugin can’t find them.

    10.03 and WP 2.5 is ready …..


  • 93

    Ken thinks:

    Hello – I’m using WordPress 2.3.3 and I love the plugin. Everything works great until PhotoQ creates the blog post. It keeps inserting html code for the large image only, with the large dimensions and everything, but nothing at all for for the thumbnail. I know PhotoQ is creating the thumbnails and moving them to their proper folders, because I can see them on the FTP. Am I overlooking something?

  • 94

    whoismanu says:


    photoq creates the code for the thumbnail in the post excerpt, not in the post content.

  • 95

    Ken writes:

    Oh, I feel so clueless. Thank you!

  • 96

    Monika says:


    your new version 1.2(b) works like a charm with WP 2.5 – thanks a lot :-)

    the versionnumber seems to be false it shows me 1.2.b – or is it 1.2b because the plugin ordner shows the upgrade info although I have upgrade this time

    but this is *cosmetics* it works … :-)

    great work


  • 97

    Monika says:


    IE has problems because img tag is without width and height but only the large image has no width and height



  • 98

    whoismanu says:


    thanks, i’ll look into this.

  • 99

    Instantaneous Instances » Blog Archive » Photoblog writes:

    [...] installed a plugin called PhotoQ that puts an image on the blog every 12 hours or so. I’ve loaded it with 4 days worth of [...]

  • 100

    Leopard on my tail at Sean Yeomans Consulting thinks:

    [...] also, this looks promising: PhotoQ WordPress Photoblog Plugin [...]

  • 101

    Man nehme: PhotoQ und Wordpress = Photoblog! « Batch-Upload, Thumbnail-Gernerierung, Photoblog, Installation, Wordpress, Plugin und, wordpress, blog, video, youtube, blogbox « beat 's writes:

    [...] dem PhotoQ – Plugin und einer WordPress Installation lässt sich ein toller Photoblog zusammenstellen. Das Tolle [...]

  • 102
  • 103

    theworldin35mm: photoblog template per wordpress e YAPB | says:

    [...] Necessità di installazione di plugin ad-hoc per il photobloggin (YAPB o photoQ) – Pochi template in circolazione o comunque in minor numero rispetto a [...]

  • 104
  • 105
  • 106
  • 107

    Wider den Abmahnwahn: dieses Foto einer Orange schenke ich her writes:

    [...] wenn Du dieses Foto der Orange als Nachspeise haben magst, bitte greif zu. Nutze das Plugin PhotoQ und Du brauchst keine Datenbank;) So als Praxistipp für [...]

  • 108


serving fresh homemade photographs