Woohoo, JournalPress should now be compatible with WordPress v2.7 RC1. There really wasn’t much to change, apart from the fact that I was apparently using a depreciated API hook to add the meta box to the new post page. So that’s now been updated to use add_meta_box() like a good plugin, and all should be dandy.

2.7 puts the Add Mirrors page in an exceptionally stupid location¹, which I’ll fix eventually (maybe), but for now take heart by the fact that there’s a new little plugin page hook that allows you to add custom link options. Now if only people actually read the instructions instead of emailing me every time they can’t find something…

I’ve also rolled up that fix for the non-Roman characters on the Settings page, so all should be well. There are a couple more minor features to get slotted in before I go back to poking at The Big One (userpics), but I think this weekend will be spent updating β’s template to use 2.7’s native threaded comments.

Or playing WoW… or Fallout 3. I haven’t decided yet.

1. It’s under Tools, if you’re looking. [↩]

Mirrored from void-star.net β. Comments are preferred on the original.

So, those of you who use JournalPress will note that it hit v0.1.3 last night. This is mostly a “tweak” version, with the following changes:

• Debugged some of the backdating stuff. It’s a bit more brute force now, but hopefully more reliable (maybe).
• Added the ability to tag a post with categories, tags or both (you’ll need to re-update your options).
• JournalPress should now accept non-Roman characters in the crosspost text, music and mood field (location and tags still have issues, but I maintain this one is LiveJournal’s fault).
• Quotes no longer cause icky backslashes to appear in the mood, music and location fields.
• Thanks to some of the world’s most convoluted return code, errors are now no longer silent.

Alas, despite my efforts with UTF-8 to entity conversion, I still missed out the appropriate part on the admin page that will allow those of you who use non-Roman characters in things like your linkback or custom journal name to actually, like, edit those. I’ll roll the proper fix into v0.1.4, but if the issue is bugging you right now, you can open up journalpress/jpfunctions.inc.php and change the following on line line 114:

114

<?php echo htmlentities( $old_name ); ?>

To:

114

<?php echo htmlentities( stripslashes( $old_name ), ENT_COMPAT, 'UTF-8' ); ?>

And again on line 153:

153

<?php echo htmlentities( stripslashes( $old_custom_header ) ); ?>

To:

153

<?php echo htmlentities( stripslashes( $old_custom_header ), ENT_COMPAT, 'UTF-8' ); ?>

Kudos to Anton Borisov for the tip.

Oh, and for the record, v0.1.3 is (hopefully) going to be the last release before the much-anticipated WordPress 2.7. Mmm, delicious new features…

Mirrored from void-star.net β. Comments are preferred on the original.

Pew Pew v0.1, void-star.net β

So, instead of working on JournalPress like a good girl, I’ve been delicately tapping away at the layout here at β. And lo! It is done!

I’m probably about, hrm… 64.58% happy with it, I guess. The concept was a “rough” version of what I plan to do with the finished product, hence the painted look of all the elements. That part I think worked out pretty well, but this is still definitely relegated to a proof-of-concept design rather than anything polished and final. Which, for β, is highly appropriate. Hence the layout stays.

Scarily (and unintentionally), despite being designed for Gecko/WebKit (albeit a little small on the iPhone), it also renders the same — :before and :after pseudoclasses excepted — in IE6 and IE7. Wow; I think that’s, like, a first since circa 2003.

In other news, it’s been pointed out to me that JournalPress doesn’t work with the beta of WordPress 2.7. No, it doesn’t; there’s no point wasting time on compatability to an API that isn’t finalised.

… I have a beautiful analogy for this, too, but alas I can’t use it for fear of getting Googled by work. Damnit.

Mirrored from void-star.net β. Comments are preferred on the original.

Proper release testing? Psh, what’s that!

Anyway, JournalPress v0.1.2 has hit WP.org, so hopefully y’all should be getting prompted to update your existing versions soon. What’s new? Well.

First off, if you’ve got no (active) mirrors defined, the JournalPress tab on the post page will now prompt you where to add some. This is due to some people reporting difficulty locating this particular options page.

Secondly, scheduled post are now supported (I think), as per Sue’s request. The solution on this one is kinda… inelegant (it adds an extra post meta tag), but it seems to work, so… This feature was going through a phase of cross-posting then deleting scheduled posts from WP, but I think it’s over that now.

Tags are now, well, tagged as well as categories. Hoo-fucking-ray for that. The function that actually achieves this is seriously undocumented for some reason, and the return values aren’t easy to work with. Hooray for random Google searches.

And finally, basic mood, music and location support has been added, in the form of manually entering in Custom Field values of (surprise) mood, music and location. These are case-sensitive, incidentally (I dunno, it’s just how WP works). I’ll probably extend this in future to support meta values from other, similar plug-ins (or at the very least write a pretty little front-end for JP’s version), but right now it works well enough raw.

Oh, and just in case you were wondering; yes, JP works with WordPress 2.6.5 and no this doesn’t fix the userpic barfing. Oh, and Tara, I’m sorry dude but I can’t replicate your editing error. The only thing I can maybe think of is the fact that you’re using an older version of WP; it’s a crappy answer, I know, but yeah… can’t think of anything else right now.

Early Morning Edit: And, hrm, apparently the logic on some of the date-out-of-order stuff is still wrong. Damn, I hate that part. Whomever invented backdate needs a slap.

Mirrored from void-star.net β. Comments are preferred on the original.

Well, Tara has the honour of being the first person to report a bug in JournalPress; hers isn’t editing. While I scratch my head trying to figure out why (I think it’s something wrong with the backdating options… maybe), here’s a quick guide on how you (yes you) can help me squish any bugs you might be encountering.

1. Open up lj.class.php in a text editor.
2. Find line 44 and change $this->client->debug = false; to $this->client->debug = true;.
3. Try and post or edit something (whichever it is you’re having trouble with).
4. You should end up with a big page of XML babble with an error down the bottom complaining about headers.
5. Copy the text from this page and send it to me, along with a description of what’s happening. (It doesn’t contain your password or anything like that. Hell, it doesn’t even contain the hash of your password.)
6. Open lj.class.php again and set line 44 back to false.
7. …
8. Profit.

Of course, hopefully none of you will have to do this… but that might just be wishful thinking.

Happy hunting!

Bleh. In other news, I’ve had a pounding headache all day and have spent most of the evening trying not to throw up.

To make matters worse, I realised tonight as I got into my car that some fuckhead had egged it, and the impact had chipped the duco off in a neat set of concentric rings. (Mat thinks it’s just dried albumen, but I’m fairly sure it’s actual damage.) Are you listening to me, internet delinquents? That shit is not cute; it does real damage.

Fuck. Kids these days. Except not, because I distinctly remember being egged myself by the neighbourhood thugs when I was about twelve. It hurt. On the plus side, I now have a house, a husband, a career, a degree, a future, an iPhone and a sportscar, while they have a juvenile record and a weekly trip to Centrelink. Who’s laughing now, fuckers.

Yeah.

(And this is just an edit to see if I can replicate Tara’s issue. I swear I checked for this… Okay, that worked. It might be a WP version issue then…)

Mirrored from void-star.net β. Comments are preferred on the original.

… yeah, okay. I really shouldn’t be as pleased to see that as I am. But hey, I’ll take what I can get.

Mirrored from void-star.net β. Comments are preferred on the original.

So, okay. JournalPress v0.1v0.1.1 is done and here. This is kinda the pre-release version, in that it works but probably needs about a month or so of in-use testing to smooth out some of the rough edges.

In the end, I gave up on the userpics thing. It pained me, but I figured getting the actual functional stuff in was more important that working on the chrome. The same error is still plaguing it; WP’s XML parser is just freaking out when it tries to convert the return value of the login call to an array. No array from this means no userpic lists. Oh, it sometimes works, but mostly it just throws errors. So, until I can figure out what’s wrong, it’s out.

The other thing that’s currently on the fritz is post tagging, because I spent an evening looking for the bloody function call that returns a post’s tags and came up blank. So I’m going to have to scour harder. Hrm…

There’s also no granularity on post security; this is by design, since it’s anticipating support for my mythical future plugin that will implement this feature into WordPress natively (good luck there).

Before that goes in, however, I’ll probably add some Currents support with the help of a few simple, interoperable plugins.

So yeah. Those of you who are interested, grab it, test it, report me some bugs.

Oh and, just for the record: JP slows down WordPress’ posting considerably, and gets worse the more journals you try and cross-post to simultaneously. Such is life when you’re trying to interact with a remote interface.

Edit: Haha. There’s the first bug. It helps with commenting when I get the variable name right, hey…

Mirrored from void-star.net β. Comments are preferred on the original.

Okay, it’s not that huge, but we’ve got ourselves our very first JournalPress cross-post (and, uh, sk.press is the VHost of my local test site, so don’t try clicking the backlink, hey).

So with that, I’d say JP is about, oh, 70% complete? It’s really only the edit/delete stuff that still needs to go in, plus a little more testing, but they’re fairly simple compared to what’s already been coded. I’m hoping to get a first release out by Monday since Emalee made the mistake of mentioning she was interested in using the plugin and, well, so am I.

I’m totally baffled, though, because the LJ.XMLRPC.postevent implementation went smoothly (it was mostly just copy-paste of the old code, with a few edits to jam it into JP’s LJClient class)… so why the hell am I still getting parse errors when I try and return the userpic lists on the post page? Oddly, it only seems to affect certain accounts (JournalFen returns fine, the JP test account returns fine, my main accounts on LJ and IJ don’t), and if I turn debugging on in the XML client I find that it actually does return… I just can’t access the values.

The only thing I can think of is maybe that I’ve got a userpic that’s… I dunno, getting parsed as a function call somehow? No, that doesn’t make sense.

Anyway.

The point is: Keep an eye out next week. Schwoit.

Mirrored from void-star.net β. Comments are preferred on the original.

Check it out! I've got my first fanlisting.

Well, okay. It's actually not a fanlisting for me, per se; it's for vs.hive, and it's run by the lovely echo.

I'm still totally buzzing over the fact that someone actually thought something I did was good enough to open a fanlisting for, so excuse me while I go squee in the corner for a while.

In other news, void-star.net β is up. It's the "second phase" testing platform for the WordPress transition here at v-s.net.

At the moment, the plan is to continue to develop JournalPress locally. β is for "live testing", as well as for slowly migrating my posting habits, so I can get used to WordPress' feature-set (I'm typing this at β, for example, and will manually cross-post it later). β also interfaces with my iPhone, so I'll start to get a bunch of "look what I found on the road" type posts.

When JournalPress has reached a release state (probably sometime in early 2009), I'll archive the sk.log version of void-star.net, stick up the new WP version and get started on work on the post security plug-in. I figure all that should keep me busy into the new year.

Awesome.

Mirrored from v-s.net. Comments are preferred on the original.