wpseek

sc0ttkclark, thanks. ?? I’m already working on a 2.7 version. There’s just so many stuff to do apart from wordpress plugin development… I’m planning to release it this week still though.

Dunno yet. Not before 2009 at least…

In the plugin I’m working a lot with the DOM, and with 2.7 this has changed quite much with the new interface. Some features still work as users report; those who are not working at the moment, might find their way into a 2.0 sometime.

Hey baptiste,

thanks for your kind words. The message came from my plugin, since there are some known issues while using 2.7. Maybe sometime I’ll continue maintaining it for 2.7+. ??

edit. Added an option in v1.9.1 to use the plugin anyway.

Thanks a lot, MooseToga! Glad to hear my work does help you guys out there. ??

Hey Saberj,

I’m going to stop maintaining the plugin with 2.7 being released, so there’s no chance to offer mass editing for custom fields with my plugin. Maybe there’s another plugin that does this already?

Great. ??

wRAR, try using this: https://www.ads-software.com/extend/plugins/https-for-wordpress/ and report back please. ??

Another user having the same problem solved the issue with that handy plugin.

wRAR, thats weird. I’m not doing cross-site ajaxing, but simply using the wp-sack library released with every WP package.

Are you using https secure links?

Well, I do have some workarounds in mind, but those are either performance-killers or a plus of dozens of extra code lines or both.

But thanks anyways for the clarification on this issue. ??

Well, sadly no. In my case I guess I’d have to use
'category__not_in' => array(3)
to exclude posts that only belong to category 3. Still it excluded ALL posts with category 3, even when the post belonged to multiple categories.

Thanks for your quick response and clarification, MichaelH. Sadly.

Version 1.0.3 fixes that issue.

Thanks for the notification (and the e-mail).

I’ve added these two lines in order to make my plugin run on IIS servers, which a user reported via e-mail some time ago. The restore_include_path() call was meant to set the include path to default afterwards so other plugins wont be affected, however I’ll fix this ASAP.

Could be a spelling mistake of yours, but you have to use jQuery, not jquery.

ps. Nice beard, dude. ??

Hey mecky,

using WP MU 2.6.1? A login would be very very nice, preferably admin account, so I can see the source code. Please to scripts at schloebe dot de

Thanks. ??