PhotoQ 1.5.1 – Repacked 1.5, Hope this Solves Auto Upgrade Problems

Only upgrade if you have problems with installing PhotoQ through WordPress auto upgrade.

I repacked PhotoQ 1.5 in a different folder structure on the WordPress plugin directory. I hope this will solve the auto upgrade problems some people are having. I also added a placeholder file to the cache directory hoping that it now gets packed by the plugin directory (empty directories obviously don’t). Sorry for those who had inconveniences with auto upgrade.

Comments (28)

  • 1

    Brandon thinks:

    We are having a problem with once we post a photo with description if we try to change the description it deletes most the text, except the first line. It only does it when we post using the plugin, normal posts work fine? any ideas on what this may be?

  • 2

    thm says:

    I finally gave in to WordPress’s nagging and did the upgrade to 2.6.2, and at the same time upgraded to PhotoQ 1.5.1. I had a bit of a scare, but got everything to work.

    First I did the WordPress upgrade to 2.6.2, using the Automatic upgrade plugin. Then I did the PhotoQ upgrade, following the directions in this blog. For my particular hosting company and blog, it took three tried to get all the photos converted, but it all did work.

    The problem was when I went to do a batch upload. I’d click on the “add photo to queue” button, and when the uploading page loaded there was an error message at the bottom. (I use Safari). Looking at the error message in the activity window, it said that it couldn’t find the file wp-includes/js/swfupload/swfupload_f9.swf. I did find this file in the old whoismanu-photoq (version 1.2.2) directory under wp-content, and copied it over to the wp-includes spot, and now the batch upload appears to work.

    It does seem, though, that I might have an incomplete or outdated version of SWFUpload–any idea what went wrong, or if I should do anything else?

  • 3

    whoismanu says:


    just checked, it’s a bug. thanks for the note. i will look into this and try to fix it one of these days.

  • 4

    whoismanu says:


    as of 1.5 photoq no longer uses its own swfupload file but uses the one from wordpress which resides under wp-includes/js/swfupload/swfupload_f9.swf. if it isn’t there it means that something went wrong when you installed/upgraded wordpress (probably this upgrade plugin didn’t upload all the files properly), i.e. doesn’t look like a photoq problem to me.

    now you placed the file where it should be (i guess the one you found is the same as the one included in wordpress, but to be sure i would download wordpress again and put the file that you find included in wordpress instead of the file from the old photoq) and it works again. still my advice would be to redo the wordpress update manually by ftp as there could be other files missing.

  • 5

    whoismanu says:


    i sent you a patch by email. please tell me whether it solves your problem so that i can include it in the next update. thanks.

  • 6

    Brandon writes:

    It looks like the patch you sent works fine now. Thanks for the quick fix. The plugin is great.

  • 7

    Ivan says:

    hi could you customize photoQ plugin for $ ? Please contact with me if you are interested.

  • 8

    Klaus writes:

    I am running into a problem since updating to 1.51 on WP 2.6.2.
    If I try to edit a PhotoQ post – it always returns to the former state – no matter what I do.
    Any idea?

  • 9

    Klaus says:

    Another problem is the resizing. I did set Photoq to resize to maximum values. In my case max width of 720 px. However it didn’t resize a 1024 px image.
    (which was the reason for my previous attempt to edit the post.

  • 10

    Klaus writes:

    And my last problem is more a request. Is it possible to have the images centered, when posted?
    If so – where can I make the changes?

    Thanks in advance!

  • 11

    whoismanu says:


    if you edit any of the image tags inside a photoq post the change will not be applied. this is not a bug but wanted as it is assumed that you change images through the photoq settings (which looking at your second post is exactly what you tried to do in the first place). this allows you to maintain a consistent look throughout your blog (so if you change a photoq image setting it is applied to all of your posts).

    this leaves us with the resizing problem you have. can you tell me exactly what your settings are? which of the radio buttons is checked for the image size in question? what are the corresponding height/width values? what is the original size of the image? what is the size of the image photoq produced?

  • 12

    whoismanu says:


    on centering the images: yep, sure. but strictly speaking how things look is not a photoq issue i.e., you don’t control stuff like this from within photoq. it is rather a html or css matter that you define in your theme. now, elements created by photoq have css attributes so that you can style them to your liking. every image tag created for example has a css class “photoQImg”. so you should be able to center the image by adding something like


    to your css file.

  • 13

    Klaus says:

    Thanks for the CSS snippet.

    I was able to make the changes I needed for the post in the database. I don’t believe that it is
    a good idea to lock the post in the way it is. There are always possibilities of mistakes on the posters side – like spelling errors, or size problems, that I ran into etc.
    Consistency should be achieved by the initial settings – but the user should be able to make changes after posting. While editing entries in the DB is possible – it is not convenient.

    Now for my settings. I think I found the culprit.
    I had the view set to original instead of main, which slipped my attention. (If however you think that this is not responsible – please let me know!)

    Thanks again!
    Cheers, Klaus

  • 14

    whoismanu says:


    you got me wrong on the thing with locking posts. you CAN edit everything related to a post after it has been posted (and of course without hacking the database – don’t even think about this!). only you cannot directly edit the <img> tags or image links created by photoq. these you can only change by changing the photoq settings.
    but you can change the description without problems (ok in some cases there is a small bug right now with this, see brandon’s comment above, but i should get the next update fixing this out next week) directly in the visual editor if you use the inline description or by changing the “photoQDescr” custom field if you went for not inlining the description. hope this clarifies things a bit.

    so if you are having problems other than the ones described by brandon while editing the description of the post, then yes this would be a new bug…

  • 15

    Klaus writes:

    That is what I meant. In some case I couldn’t even change the text. But still – why lock the content of the image tags – from time to time I have to make changes – may it be just a problem of the image size or quickly change the image entirely…
    So what are the settings in PhotoQ, I have to change to enable making changes?

  • 16

    whoismanu says:


    ok, so as i already told you, you should be able to change the text otherwise it is a bug. you still have this problem? if so can you give me some more detail as to when it happens? do you inline the description or not? did you try to change the text in the visual editor?

    concerning locking the content of the image tags here is my line of thought:

    first and foremost, if i had to name one single reason why i would like to have photoq it would probably be the fact that as a user i don’t want to edit html img tags. the image the tag points to has a certain size and a certain location on the server. this is also more or less the only information you will find inside the img tag: obviously the two locations (src) have to match exactly. the same goes for the size given in the img tag: it should exactly reflect the size of the image, otherwise the browser will resize the image and i will end up with blurry thumbs. so as a user i don’t want to bother with the img tag as all its content is anyway dictated by the image it points to. the img tag should be updated if the image it points to changes e.g. in size. photoq lets you manage the size of your images from one single point, the photoq settings page. you want to change the way your blog looks (e.g. because the design of your site changed and you now want your thumbs to be bigger), you can do so with one single click, photoq rebuilds the downsized images and updates all your posts (read the corresponding img tags inside) for you to match your settings.

    according to this reasoning (and if i am not mistaken ;-)), a “problem with an image size” can only mean one of two things: 1. the image the tag points to does not have the size you desire. in this case you should not try to force the image to have the size you want by changing the size settings in the tag (because you will end up with bad quality thumbs) but rather have photoq rebuild the image by changing the image size setting. 2. the size of the image does not match the size given in the tag. this should not happen and if it does it is a bug and i would be happy to fix it.

    concerning changing the entire image: photoq builds downsized versions of the image from the original image you uploaded. you want to do some additional post processing on some image and thus want to change it entirely, replace the original image and have photoq rebuild the downsized versions from the new original (agreed, there is currently no feature yet to update the original image other than replacing the file on the server manually, but this update capability is one of the next things you are likely to see coming to photoq, i promise ;-) )

    this is my point of view on this subject right now. but i am always very glad to hear any other arguments as well. if you guys can convince me that something in photoq should be changed for the benefit of most users i am always glad to reconsider. in the end i am only one user of photoq among many others…

  • 17

    Klaus writes:

    Hmm – why I follow your train of thoughts – that’s exactly why I use and love PhotoQ.

    Locking it still does not really make sense. It’s my blog for crying out loud (no offense to you :)) – and if I want to delete an image in a post (PhotoQ or not) I want to be able to do that. Example – I deleted the image in question in the visual editor and re-uploaded a new one. Saved it – but on reload it was reverted to it’s original state. That is – what makes no sense to me. Maybe that’s something that was not intended by you? (By the way changing the text did work).
    So the locking thing is a bother, if you have to correct a mistake – maybe mistakenly uploaded the wrong image.
    I guess the image size problem was a mistake on my end – having set the size to original instead of main.

  • 18

    whoismanu says:


    i see your point and that is exactly why i am planning to have this photo update feature i talked about in my last comment. imagine that you want to change the photo on a certain post (or certain photos on certain posts, after all we like batch processing don’t we?). imagine you upload these new photos like you would upload any regular photoq photos. imagine photoq then tries to match these with already posted photos based on e.g. the file name. imagine it then gives you the option to replace the matched photos with one click.

    would something like this make you happy? would something like this make your urge to mistreat photoq <img> tags go away? ;-)

    joking apart, i now understand where your pain comes from. but until i come up with a solution like the one described above, don’t change the image in the database table but just overwrite the original image file on your webserver. Then go to Manage->Posts and rebuild the images of the corresponding post by hitting the rebuild button in the last column.

    For every post, PhotoQ creates a custom field “photoQPath” with the path to the corresponding original file. It uses this field to identify which posts are photoq posts and which are not. Now if you edit the database directly this can create a mess in several respects: the “photoQPath” field may not be correct anymore (will not match the image displayed), the image you uploaded without photoq will probably not be at the expected location inside the imgdir, the alternative image sizes are not created etc. etc.

  • 19

    Klaus writes:

    I’m not quite sure if that would be, what I need.
    By the way – I just went into the database wp_post table and changed the image dimensions there. ;)

    I still can’t get my mind wrapped around the locking thing. Is it a side effect of something else? Why does it revert back – even after I deleted the img tag entirely? That is my main issue – for unless there is something “controlling” the posts content, that should not happen at all.

    By the way – I inserted the CSS snippet into my main CSS File , but portrait format images stay left aligned.

    Thank you for the time you take, to get this sorted out! :)

    Cheers, Klaus

  • 20

    whoismanu says:


    my mistake for the css. sorry. try this it should work:

    margin-left: auto;
    margin-right: auto;

    aargh, don’t touch the database, it is not meant to be touched… ;-). and i still don’t get why you would want to change the width/height attribute of an <img> tag (through the database or visual editor). again, to me resizing should be done by changing the actual image file not by having the browser resize it.

    concerning locking:
    1. yes it is a side effect and it reverts back because photoq reverts it back. photoq does so because it tries to keep the img tag in the content in sync with the image file on the server (see comment 16). it knows to which image file on the server a post belongs through the photoQPath custom field (see comment 18).
    2. it puts it back after you delete it because it assumes that a photo post without a photo doesn’t make a lot of sense and that you thus deleted it by mistake. to replace a photo with another one the way to go is what i describe in comment 18 until i come up with a better way (along the lines of what i also describe in comment 18, or sth different if anyone has a better idea).
    3. yes, if you want photoq is controlling, see above under 1. and 2.

  • 21

    Klaus says:

    :) Ok – CSS works now! Thanks for that!

    Well – for the database meddling – the main reason for me was, that I re-uploaded the image in the main folder, not aware of the original Folder, something that has been changed since the last time I actively looked closer at PhotoQ. So nothing changed and because the image was basically cut in it’s display, my last resort was editing the wp-post entry for that post.
    Now, that everything is set to work correctly, I probably will not encounter that problem again anyway.
    For the locking issue – I hope you will find a way around that, because it’s way too restrictive, or better said – a control that I really don’t care for or want to see.
    If I wouldn’t get quite a lot of comments, I otherwise would have deleted the post entirely and reposted it.
    Not being able to delete whatever I want, when I want is truly bugging me. Fortunately that issue comes up very rarely.
    For now – all major issues are resolved I guess.

    Thanks a bunch!
    Cheers, Klaus

  • 22

    Jesse writes:


    Great plugin. I am customizing it on my local machine. I have a question, How to batch post? e.g. post 10 photos or 20 photos at one time. I have lots of photos, post one by one is too slow.


  • 23

    whoismanu says:


    the next update of photoq that i am currently testing for release (i.e. it won’t be long until it is published) has the option to post the entire queue at once (however, no option yet to post say, only 10 photos).
    otherwise what you might be able to do right now is for example set up several cronjobs to run one after the other, each posting one photos.

  • 24

    Jesse writes:

    I am wating for this feature. After adding this, the PhotoQ will be perfect.

    I tried cronjobs on a live site, I set post a photo every 5 minutes. Then I got host company’s warning, it takes too many server resources.

    So the best way is to add a post option.

    P.S. I’d like to test your beta code, can you send it to me? my email: [removed by whoismanu]

  • 25

    dave writes:

    My upgrade went smoothly and the new features are fantastic! Thanks for all the hard work.

  • 26

    whoismanu says:


    you are welcome and thanks to you too: it is always nice to have some comments that are not bug reports ;-)

  • 27

    Paula says:

    I’m using Lightview Plus at the moment and I would love to generate different galleries with PhotoQ.
    But the best thing I could achieve, was one big gallery with all the images from all articles I’ve published with PhotoQ so far.

    Will it be possible in some future version to post several images into one article? Or is there some kind of workaround?

    I love this plugin, but I dont know if it’s the solution for my problem.

  • 28

    whoismanu says:


    right now photoq is one photo per post. so no, at the moment there is no way to have several photos in the same article.
    i have it however on my wishlist for some future version. but this will require quite some changes to photoq and i have not yet decided how to do it. this means that i cannot promise you anything about when photoq will have this feature.

    now, you say that you can have a gallery with all the photos ever posted with photoq. in this case i guess that you could also in a similar way have a gallery per category or per tag to have something more fine-grained.


serving fresh homemade photographs