[Plugin: Query Wrangler] Error after Update

Updated again. Hopefully that resolves the issue.

Yes now it works again. ?? But as I see, all my queries have changed and need to be edited and saved anew. Also all my CSS has to be edited again. ?? So I have to do some hard work now, but that’s ok as long as I don’t have to do it now after every upgrade of Query Wrangler. ??

Yeeeah, Sorry about that. I realized after releasing 1.3 that I wasn’t really following View’s templating methodology very well and have been trying to correct it.

My update script should have altered the query data appropriately for any filters and settings in a query. Could you tell me what about the queries required you to reedit and save them?

As I develop more hooks for other plugins to use, I keep finding it necessary to alter the data structure. I’m trying to make sure the upgrade script handles this automatically for everyone, but may have missed something.

In 1.4, the Post Status filter has been moved to Basic settings, because it has a default value in a WP_Query of ‘published’, so it didn’t make sense as an optional filter.

Btw. I have this issue again, that the links in the settings and fields boxes are not linked in FF. In IE it looks fine. But works nevertheless in booth.

Here some Screenshots to illustrate the bug…

…in Firefox 10:
https://img822.imageshack.us/img822/7120/qwff.jpg

…in Internet Explorer 9:
https://img826.imageshack.us/img826/6966/qwie.jpg

Hmm.. that is really weird. It’s like FF isn’t finding the css file. But it clearly is, because it has columns and background images.

Have you cleared your browser cache? That’s very strange. I develop primarily in FF.

It seem to be temporary, because now it looks like in IE. Preview sometimes doesn’t seem to work too. But at last it works after all! ??

Could you tell me what about the queries required you to reedit and save them?

In most of my queries these two…

Row Style: None
Posts Settings: None

…and the tag filters

Ok, I’ll review my upgrade script.
Thanks!

Let me know if you run into anything else.

.. and now you know why this is still in beta. ??