Technocrank

Icon

It Done Broke.

WordTwit Strangeness

WordPress 2.9.1
WordTwit 2.3.1
WPTouch 1.9.7.7

Some bizarro stuff going on with WordTwit. First it was complaining about a foreach() loop and coughing up a PHP error. Now it doesn’t seem to know how to handle the multi-dimensional array $tweets; it spits back the first character of the first levels elements. I posted the letter “t” -900 minutes ago and the number “2” 14646 days ago?

In another theme that handled widgets, similar hanky, but with doing something with an array that PHP didn’t like.

Unfortunately, Bravenewcode, the authors, have their support forums in plastic surgery right now and I’m not sure how to contact them. I’ve also tried hitting them up on Twitter for a clue on how to hit them up. Nothing yet.

Update: the lads from Bravenewcode have quickly fixed this. It was an error caused by Twitter not returning an array when only one tweet was available (when it normally does). WordTwit 2.3.2 and WPTouch 1.9.8.1 address this issue.

WordPress For iPhone Local Drafts

WordPress 2.9.1
Wordpress for iPhone 2.1-2.2

Saving a local draft fails. Not iust fails, but completely doesn’t happen at all. Writing a post of any length goes into /dev/null. Seems it’s not an exactly uncommon issue as this forums post shows but for some reason isn’t reproduceable.

Saving as a draft to the server is fine, though.

wp-Typography Beta for WordPress

Haven’t gotten around to installing it yet, but last week wp-Typography (a merge between wp-Hyphenate and wp-Typogrify) for WordPress was released under a beta version.  The author has also factored out the functional code into a separate PHP package for typography.

Google Gears & Firefox Working Again

Google Gears (0.5.29) has just been released and now works with Firefox 3.5.  I’ve only tested it so far with WordPress.

Contributing to WordPress: Worth The Time?

I suppose this is really a subset of a larger question: does it make sense to get involved with open source software projects in general?  Seeing Jane Wells’ recent posting about contributing to WordPress stoked an old ember deep inside me and I thought this is actually a question worth asking out in the open (not moderated by, um, moderators with a vested interest).

By their very nature, open source projects are pet projects.  They have people who are very interested in their success.  And, of course, this is a good thing (no, I’m not going to capitalize those last two words).  Also, there is a need to have some degree of management and control over what gets dumped into the repository.  This is sensible – that there should be some level of review and direction that keeps the project on track (even if that track is the Oregon Trail).

Within the WordPress development system, everyone is encouraged to contribute.  Everyone has read (a.k.a. checkout) permission to the SVN repository.  However, only a handful of people have “submit” access to the repository.  That is, only a few (key personnel) can write to the code base directly.  If you’re not one of those few, you can still grab a bug or whatever out of their Trac, work away on it and then submit a patch back to the Trac whereupon somebody needs to recognize the patch has been submitted, test it, and then approve it.

Reality kicks in, though, when you realize that the core developers who have direct write access to the repository also grab bugs from the Trac and also work away on them (feverishly, even).  However, they don’t always check to see that somebody else has claimed the bug (or if they do, they don’t care).  So it’s a bit of a slap when you discover that after going through the motions of following their procedures, claiming responsibility for the bug, the thing you’d spent hours, days working on has been been superseded and already patched by either Matt, Ryan, Mark or whoever – while it’s still marked as YOUR BUG IN THE TRAC.  Either that, or you submit the patch and nobody notices.  I mean, hell, the system flags it (assuming you submit the tags properly), so somebody should notice, no?

God bless them.  They work hard and there’s a lot of stuff to crank through and they do a great job.  Yeah – but if you want to get involved and help out with squashing bugs in the core?  Forget it.  It’s really not worth your time.  There are theoretically better things to do, like work on the documentation, offer help in the support forums, write a plugin or a theme – basically anything that doesn’t require direct approval or suffer from intervention-itis.  I guess what I’m saying is only work on stuff that’s useful and that matters.   And by that I mean, if it doesn’t matter to the developers if you are spending or have spent your time, then your time has been wasted.

And while a lot of open source projects suffer from the same deficiencies (or benefits, as some call them), not all do.  You could also just start your own pet project.

Note: this has been written intentionally rhetorical, but not untruthful.  I am a crankietech, after all (and I have voiced this concern in the appropriate places prior to this).  If you feel that I’m way off base, please feel free to comment and also give me write access to your repository.  Whatever your project is. 🙂  I would love to hear from people whose experiences contradict mine.

Twitter: crankietech

RSS This Day In Tech (From Wired)

  • An error has occurred, which probably means the feed is down. Try again later.