WPBook 2.0.1, beta testers still needed

Once again, I’ve tagged a new version of WPBook for release. See the “other versions” section of the download page.

I’ve revamped the way permissions are requested, so as to store the session key Facebook provides when the user grants “offline access” permission. This enables WPBook to import comments from either the user’s Facebook Wall or the Wall of a Facebook Fan Page.

I’ve also added the ability to change the attribution line (the little blurb WPBook attaches to each message when you post it).

Given the complexity of all the different ways one might configure the application, though, I feel a need to get some folks testing it before making it the ‘default’ new release.

If you’re testing it, please do let me know – either via comments here, in the wpbook support forum, or via the contact form.

NOTE: This version has debugging on by default, which means it will create a debug text file in your wpbook plugin directory – this can be disabled by editing wpbook_cron.php at line 37, changing:

define ('DEBUG', true);

to

define ('DEBUG', false);

But there is useful info in that debug file for trying things out.

You’ll also probably find, in testing, that you’ll need a plugin like Core Control which lets you see what cron jobs are running and run specific jobs ahead of schedule.

Thanks

John

State of Drupal

(First part of this week I am attending DrupalCon 2008)

[Update 3/4/08: Audio from the State of Drupal as well as Jay Batson and Dries' "Presenting Acquia" talk are available on Shai's podcast]

[Updated again 3/6/08: Video from the State of Drupal at Internet Archive]

Not surprisingly, Dries’ state of Drupal presentation was well received by the crowd of assembled Drupalers.

The state of our union is strong, Dries began, citing the success of Drupal 6 in attracting even broader communities of interest. But as we prepare for the broader audiences that success brings, there are things we need to pay more attention to.

The focus of Drupal 7, as Dries recommended to the community, should be on interoperability and usability. This means improving internal and external APIs, enhancing data portability, and redesigning the home of Drupal, drupal.org, to better accomodate the next wave of users joining the community.

(Great to see a project lead of a major open source community paying so much attention to usability!)

Read more…