absalom

Forensic code analysis shows this to be an almost line for line rip from Tweet Old Post, with the bugs that Tweet Old Post have addressed not delivered here.

I get the same issue. Is there a release date for 1.6.1?

It happened when I upgraded the edition of Socialise that I was using. Screenshot available here

I’ve been running comparative WordPress builds between JanRain and Gigya and even at the free/educational/NFP level, Janrain offers around another 1500 or so OpenStack registrations before payment cycles start.

Gigya, at least on WordPress, doesn’t seem to provide the same level of mature login integration that I’ve seen elsewhere.

As an aside I found a bug of sorts in the Gigya build today. One of my customers moved their FB email account / page integration and since the Gigya account is linked to that (now) archiac email, it broke the entire authentication sequence without telling me – basically disabling all social media functionality.

In 1.0.0a I can see the widget, install it into a specific widget area, but it won’t display.

Confirmed this behaviour as well. It seems the 0.3 and 0.3.1 releases by Janrain have been more buggy and incomplete than a fully polished product.

Confirmed bug. It was happening on builds between 2.9.2 up to 3.0.1. Something seems to have broke severely at their end..

It’s a semi-random image stack that’s hooked into the categories, not into each individual article. Thumbnail logic is complex, to say the least.

I’m using a heavily customised version of The Morning After.

Regarding the aggregation/reproduction, the closest legally binding licence is the Creative Commons licence listed on each article. The blurb is simply a throwback to the old reproduction licence. May phase it out in the longer term now that Creative Commons is judiciously integrated across the site.

I’m using @cufon at the moment. Still a XHTML 1.0 template, with just some very basic hAtomised content. Long term strategy is to move to HTML5, @font-face with font-squirrel and more microformats.

Thanks for the feedback. We’re still soft launching till mid next week.

Theme is being tuned to suit. Will head to HTML5 and font-face soon. Already subtley microformatted.

Shane

That’s not really the rewriting rule I’m looking for. I need a category slug permalink that can handle ampersands and spaces and/or rewrite to the category number.

Think I might revisit my migration procedure and just preg_replace/json_encode the category slugs as a workaround.

Would this help ?

https://fucoder.com/code/permalink-redirect/

Could this be modded to display nice archives for each category, each author and each post title ?

I got 15,000 posts currently running on 1.5 (upgrading to 1.5.1 tonight), and I need to know which would be better for me:

WP-cache or Staticize Reloaded ?

Skippy,

Is just specifying a meta_key (“my_author”) and meta_value (“name goes here”) in the postmeta table ??

If so, how do I differentiate between meta keywords (which I’m planning to put in the header) and this additional key inside the template?