DrupalCamp CT and the Legacy of Henry R. Luce

Last weekend I went down to New Haven for DrupalCamp CT 2011, at Yale. It was a smaller camp (compared to Design4Drupal Boston, or DrupalCon) but had excellent content and showed there is a strong Drupal community in the heart of the nutmeg state. (We did take a group photo but I haven’t seen it surface yet).

Even at a smaller camp there were multiple parallel tracks of presentations, and I found myself wishing talks had been recorded so I could see some of the ones which overlapped, my inability to be simultaneously two places at once hold me back yet again.

Program for DrupalCamp CT 2011 - click for larger

My favorite sessions of the day were Benjamin Melançon‘s “When there isn’t a module for that” and John Zavocki‘s keynote “From the Margins to the Center.”

Read more…

WordCamp Boston 2011

The other major reason I haven’t been very active here in the last few months is WordCamp Boston, coming up in just under two weeks (July 23rd and 24th).

This year’s camp promises to be even bigger than last years, with content from 30+ speakers spread out over one and half days at the Boston University student union. We’ve even got a pre-conference workshop the Friday before and a reception Saturday evening at the Microsoft NERD center.

If you haven’t already got tickets, you’ve missed regular registration, but you can still get in on late registration (which just means you’re in line after the regular registration folks for lunch and T-Shirts) for just $40.

New gig: ISITE Design

So 2011 has been a pretty crazy summer for me, as evidenced in part by the fact that it has taken me over 2 months to write about changing jobs. (Or anything else, for that matter – I think that’s the biggest gap in posts since I started this blog back in 2006).

Back in the beginning of May, I left Optaros and started working across the river in Cambridge at ISITE Design.

Read more…

WPBook 2.2.1

Try Again (Photo by Samantha Marx, cc-by license, http://www.flickr.com/photos/spam/3355834452/)

Spent some quality time this weekend with WPBook. As a result, I just released version 2.2.1. (There was briefly a 2.2 release, but something was corrupted in that version of the SVN repo, so use 2.2.1 instead).

Included in 2.2.1:

• Read More is back. Re-enabled the “Read More” action link. Unfortunately, because of a Facebook API bug wpbook can’t add more than one action link to a post, so no “share” button on wall posts until that is fixed. (Facebook doesn’t add the Share link automatically to posts from the Graph API and there’s currently no way to make that happen other than manually adding it as a link, but I think the “Read More” link is more important.)
• Post to Group Walls. Added posting options for Group walls, and comment import form Group walls. Because of the way the Facebook API has changed, posting to a Group feed is distinct from posting to a Page’s feed, and requires different syntax.
• Controlled debugging. Limit the size of debug files created to 500k, so that users who enable debugging and then forget won’t have an unlimited file growing every hour. Also made the debug constant more specific to WPBook so as not to interfere with other plugins potentially using DEBUG as a constant
• Fopen errors. Clean up DEBUG for cases where permissions fail or file is not writeable
• Facebook::$CURL_OPTS . Made “disable ssl verification” an option so that only users who need it will have it and others won’t get conflict
• Required fields are required. Cleanup to the admin screens in general, more clarity around what is required and better language on the admin screens about what is being checked. (Thanks BandonRandon for patches)
• Better check permissions. Improved “Check permissions” page, to show what options mean and enable links to view profiles, pages, links to validate IDs are correct.
• Added wpbook logo which had been missing
• Fix for get_themes() issues with WordPress 3.0.1 through 3.0.5

I realize from the activity in the forums that many users are having trouble with the 2.1 and later WPBook – but I believe all the known errors have been fixed, and most are due to misconfiguration.

A few configuration notes that might help:

1. Your application ID, secret, canvas URL, and Profile ID must be correct or nothing else is going to work. If you load your application canvas page and you don’t see the WPBook theme, but see just your blog in an iframe (unchanged), then something is wrong in your Facebook Application setup, your WPBook setup, or in a plugin conflict.
2. Your personal FB profile is absolutely required, even if you don’t plan to publish to your profile’s wall. It is through the FB profile that the access_token for publishing to pages is retrieved. If your FB profile ID is wrong, nothing else is going to work.
3. Any time you change the Profile ID, the Page ID, or the Group ID to which you are trying to publish, you must visit the Check Permissions page and will most likely need to regrant permissions. Again, if permissions aren’t working, nothing else is going to work.

If you’re stuck, please open a new thread in the wordpress forums and provide the following debugging info:

• The URLs of your Facebook Application and your blog outside FB
• The contents of your check permissions page – verbatim
• What you are trying to publish to – profile, page, group – by ID and by URL
• What error messages you are seeing, in the WordPress interface and/or in the PHP error log

With the right information, we will be able to get it working.

Thanks

WPBook 2.1.4 Released

Code Bug (Photo by Guilherme Tavares, cc-by license, http://www.flickr.com/photos/guitavares/1703252007/)

Just released WPBook 2.1.4.

Two key bugfixes in this release:

1. Comment Imports. In changing to the Graph API I needed to add an access_token to the FQL calls I’m using to retrieve comments from non-public streams.
2. Facebook Avatars for Pages. Given that you can now comment on wall posts as a page (by using the “use Facebook as page” option if you are the admin of a page) some of your comment authors in FB might be pages themselves. This fix will get the right FB avatar for them, eliminating what was otherwise a broken link image.

There should not be any need to regrant permissions or change any Facebook settings in this release.

Thanks to all the users who’ve provided feedback (and debug files!) in the forums.