Road to nowhere (Photo by Matthew Connor, cc-by-nc license)

Back in January, I got an unexpected flurry of WPBook support requests, and ultimately discovered they were the result of Facebook’s decision to allow people to browse Facebook in HTTPS mode.

As part of that change, Facebook introduced some new settings: “Secure Canvas URL” and “Secure Tab URL,” which would enable https connections throughout your Facebook application.

WPBook mostly worked with these two variables properly set (thanks to cshiflet for this patch).

Now, however, Facebook has announced they will require ALL apps to support https:

Today, we are announcing an update to our Developer Roadmap that outlines a plan requiring all sites and apps to migrate to OAuth 2.0, process the signed_request parameter, and obtain an SSL certificate by October 1.

What will this mean for WPBook users?

Unfortunately, my guess is that many WPBook users are not prepared to install an SSL certificate and accept https traffic on their blogs. (SSL certificates typically require that your blog have a unique IP address and cost extra at shared hosting facilities).

If you are unable to install an SSL certificate for your blog, and enable https based browsing of it, you may be unable to use WPBook after October 1, 2011 (or whenever Facebook decides to actually enforce this migration step).

More to come as we get closer to that date.

(photo by hobvias sudoneighm, click for photo page)

Thanks to troubleshooting help from mommyknows and other users, I’ve been able to track down and fix an issue with posting to different kinds of pages.

Thanks to Brooke Dukes, we also now have a site for the plugin itself: wpbook.net – with instructions, blog posts about the plugin, and the like.

Grab 2.0.8.1 from the plugin repository and check it out!

(2.0.8 somehow incorporated a nasty syntax error – whitespace ahead of the opening PHP tag – so skip that and go straight to 2.0.8.1).

For a long time now WPBook has enabled users to cross-post excerpts from their blog posts to either the wall of their personal profile or the wall of a Facebook fan page.

However, in setting up WPBook many users were ending up with:

• Your WordPress blog outside Facebook. (Example: www.openparenthesis.org
• The Facebook application view of your blog. (Example: apps.facebook.com/openparenthesis)
• The Application Profile page for your new Facebook application.(Example: https://www.facebook.com/apps/application.php?id=12797741823)
• A Facebook Fan Page for the Blog, or other Fan Page on which the blog gets published. (Example: https://www.facebook.com/pages/WPBook/44062579871, which in this case isn’t a fan page specific to the blog but to the WPBook plugin itself).
• Facebook Tabs, which can be added to users’ personal profiles (including your own), or Facebook pages (either a Fan page or an Application Profile page). (Example: https://www.facebook.com/pages/WPBook/44062579871?v=app_12797741823).

Starting with 2.0.8.1, WPBook can instead post directly to the wall of the Application Profile page – which is a nice way of showing potential application users what kind of blog posts come through the application.

Of course, you can post to your own profile’s wall in addition to a second target, which can be any of these:

• A Fan Page wall
• Your Application’s Profile page
• The Wall of a Facebook group

If you post to a Fan Page wall or an Application Profile wall, the post will come from the Application; if you post to the wall of a Facebook group, the post will come from your personal profile.

Settings for Profile ID and Page ID

You should provide your personal Facebook Profile ID in the WPBook settings, and then in the field provided for “PageID,” you can provide:

• An actual Page ID, for a Fan Page. (To find this, click on “edit page” – the url will look something like this: https://www.facebook.com/pages/edit/?id=44062579871 – the Page ID is the part after id=)
• An application ID, for an Application Profile page. (To find your application ID, go to the Application profile page, the url of which will look something like this: https://www.facebook.com/developers/apps.php?app_id=12797741823 – the Application ID is the part following app_id=)
• A group ID, for the wall of a Facebook group. (To find your group ID, just visit your group page, the url of which will look something like this: https://www.facebook.com/group.php?gid=149948248362737 – the Group ID is the part following gid=)

As always, please post in the support forums with your experiences.

It’s about your digital footprint: the sum total of all the interactions your customers, prospective customers, fans, antagonists, employees, suppliers, and partners have with your content and services throughout the entire Internet.

A quotation in a recent post on the Inc. Technology blog, It’s Not About Web Traffic Anymore, put it this way:

It’s not about getting people to come to my web site anymore. It’s about getting my content; my videos,my articles, my event promotion announcements, on YOUR web site. That’s what I’m paying attention to now.

– Barbara Scala, Founder of Bloom

I agree wholeheartedly, but remember that “YOUR web site” might be a Facebook news feed, it might be a blog, it might be an link from YouTube sent via IM or a tweet. It’s no longer about getting folks to come play in your garden, but about making yourself available in all the places folks might already be hanging out.

Private Garden (Photo by surprise truck, cc-by license)

Your web presence (which should be a combination of sites, blogs, microsites, and official presences in social networks) is still critical, of course – as the place to which folks will often go for more information, to sign up, to interact with you – but if your efforts stop at the sites you own and control you’re missing out on the majority of the web.