3DN Technology » wordpress

Playing with Simple Facebook Connect

Fred Leeflang — Thu, 16 Jun 2011 22:23:19 +0000

As a brief note to myself and other who may experience the same problem: I use the “Simple Facebook Connect (SFC)” WordPress plugin on my site. It’s a very nice modularly written plugin but that’s all described very well on the site. My note is about using this plugin on a WordPress instance running multiple domains however.

While adding ‘like’ buttons to my second domain on the server, I noticed I started getting error message from Facebook saying:

The app ID specified within the “fb:app_id” meta tag is not allowed on this domain. You must setup the Connect Base Domains for your app to be a prefix of http://dutchie.org/rowan-lore/.

Further investigation showed that the

As http://dutchie.org is really running on http://dutchie.3dn.nl but mapped on there with the domain mapping plugin, I figured I’d change the href parameter into http://dutchie.3dn.nl/rowan-lore. This can be done through a bit of an undocumented feature in SFC. I modify the theme files directly through putting an sfc_like() call in the theme file. When used without arguments, the sfc_like() function will generate the URL based on the get_permalink() WordPress API call. However, noticing the function also parses a $args parameter when provided, I decided to do:

$url = urlencode(str_replace('dutchie.org ', 'dutchie.3dn.nl ', get_permalink($id))); sfc_like_button(array('url' => $url));

While of course this little trick is handy to know and resulted in the desired effect, the error message remains.

I’ve also been looking into the FBML tags being put in the header:

And manually tried to force sfc-base.php to generate dutchie.3dn.nl instead of dutchie.org in the og:url field. Alas, this also did not work. Otto, the developer of SFC assured me that there is no way of adding a second domain to a single FB application, but I’m still curious about this as http://dutchie.org is a second domain on the server indeed, but it’s *mapped* to http://dutchie.3dn.nl which is a subdomain of the facebook app.

New 3DN Techblog

Fred Leeflang — Wed, 12 May 2010 14:33:09 +0000

This is the first post on the WordPress 3.0 MU server. http://wordpress.3dn.nl has now become a ‘site’ under the main blog http://3dn.nl. This is possible since 3.0 which now has the multi user functionality built in.

First there will be some transitioning stage where plugins I used on the old http://wordpress.3dn.nl will be enabled on this site, so it’s possible that this site will look off for a while. Please bear with me, I’m still trying to figure this out.

The migration was fairly simple. I probably could have done it even simpler by just starting with the old database and migrating that to 3.0 but I decided to have 3.0 running in parallel with 2.9 for a while when I tackle the Debian way. I first created a MU site called http://wordpress.3dn.nl and tested that to work. Then I went on to export (using Tools -> Export) in the wp-admin screen, which gave me an XML file. Then I imported this into wordpress.3dn.nl and checked the box to import attachments as well. The latter tries to fetch the attachments using the URL; since this has http://wordpress… in it, I had to temporarily leave the old server running. After it imported I renamed wordpress.3dn.nl and disabled the old wordpress.3dn.nl

I fully expect some plugins not to work. The first one I found not to work properly is the linkedin resume plugin. Peculiarly it failed at updating the settings. I also found EHT graphviz not to work, in fact it messed up the whole admin section.

There are still some major glitches on the site but I’ve decided to go for it as some problems may be related to having a different site name.

Add Ajax to Expertise Plugin

Fred Leeflang — Sun, 28 Feb 2010 08:43:32 +0000

The Expertise plugin is nearing completion now. We still need to give experts a method to sign up as experts for the 3DN expertise areas (or to sign out should they no longer want to act as expert). We will be using some WordPress specific Ajax constructs for this.

One of the reasons we would like users to sign up and be logged in when they look at the expertise pages is so we can see right away if somebody who’s visiting the pages is an expert himself or not. This way we can decide what button to show and what action to attach to the button. We have two different buttons to choose from:

These are opt-in / opt-out buttons where a visitor can indicate whether he is or isn’t an expert on the expertise being viewed.

These buttons have a simple onclick javascript that gets executed when the user clicks on them; when the opt-in button is clicked a simple thickbox dialog asking for the user’s expertise level is displayed while the opt-out button simply shows an ‘are you sure’ question. In this article I’ll assume the reader is familiar with thicbox and how to pop-up a dialog.

Using SACK

SACK is the Simple Ajax Code Kit. We don’t want clicking the button on the popup dialog to cause a reload of the whole page so we’re using SACK to send an asynchronous page request to the server to handle the opt-in / opt-out.

To do this, we first need to tell WordPress to include the SACK library javascript:

// Add SACK requirement to head
add_action ('wp_head', 'expertise_js_header');

function expertise_js_header () {
 wp_print_scripts ( array ('sack') );

The only thing somewhat complicated for using SACK is that we need to figure out what page to post the AJAX requests to; WordPress comes with a /wp-admin/admin-ajax.php script for this. It’s a unified Ajax handler script that can be used for all AJAX requests. We only need to tell it about a callback function to use depending on which action the page receives. First we define our own actions, handle_signup and handle_signout:

// Configure AJAX callback
add_action ('wp_ajax_handle_signup', "signup_callback");
add_action ('wp_ajax_nopriv_handle_signup', "signup_callback");
add_action ('wp_ajax_handle_signout', "signout_callback");
add_action ('wp_ajax_nopriv_handle_signout', "signout_callback");

Then in our button javascript we use these action names in the SACK initialization:

// Define custom Javascript function
?>


Playing with Simple Facebook Connect   
New 3DN Techblog   
Add Ajax to Expertise Plugin   
Checking Comments for Requests   
Adding sendmail/SMTP to experts plugin   
Or in the Coding category:
Playing with Simple Facebook Connect   
Facebook Bookmarks for Chrome?   
Add Ajax to Expertise Plugin   
Checking Comments for Requests   
Adding sendmail/SMTP to experts plugin   
If you have any questions regarding WordPress, check out our         Wordpress page or our         Programming page. Note: The code I’m writing about is constantly under development. I can’t write about every little change I make but I try. I’m learning as I go because this is my first WordPress plugin. If you’re interested in the latest code you can always look in SVN through my public Trac server.

Periodic Expertise Events

Fred Leeflang — Tue, 16 Feb 2010 12:37:21 +0000

Earlier I wrote a few articles on creating the expertise plugin and how to add shortcodes to it. Today I want to add scheduled events to the plugin. When somebody posts a question to the expertise page, we could probably write a trigger that checks immediately who’s the expert for the section and send a notice in an email. However, I think it’s also nice to illustrate making a timed even that will check all expertise pages at once for new messages and send out all notifications right away.

Activation Code

One thing we have not yet added to the plugin is a decent activation/deactivation section. We should do this first, we’ll see why later on. In WordPress, a plugin can be activated and deactivated through the administrative plugin menu. These events can be trapped with the register_activation_hook() and register_deactivation_hook() functions. Typically these hooks get used to create extra database tables needed by a plugin, set default values for the plugin etc.

Another thing that can be done in an activation/deactivation section for a plugin is to create / remove a timed event for the plugin:

register_activation_hook(__FILE__, 'expert_activate');
add_action ('expert_msgcheck', 'hourly_msgcheck');

register_deactivation_hook(__FILE__, 'expert_deactivate');

function expert_activate () {
 wp_schedule_event(time(), 'hourly', 'expert_msgcheck');
}

function expert_deactivate () {
 wp_clear_scheduled_hook('expert_msgcheck');
}

function hourly_msgcheck () {
}

The above code snippet sets this all up; The add_action() call at first seems kind of pointless here as there’s no point in time where the WordPress core will execute this action. This all changed when an administrator chooses to activate the Expertise plugin. Through the register_activation_hook function expert_activate() will be called. This function in turn calls wp_schedule_event() which schedules the action expert_msgcheck (and thus the function hourly_msgcheck()) to be executed hourly, starting immediately.

Work with Me

Let’s add some code to the hourly_msgcheck() function. We know that we want it to send email eventually, so to check if the mechanism works we’ll simply let the function send us an email every hour. On my setup I need to use an SMTP mailer as I’m using Google Apps for email. This requires some settings we might as well initialize on activation of the plugin:

function expert_activate () {
 wp_schedule_event(time(), 'hourly', 'expert_msgcheck');
 add_option('expert_settings', array(
 'onpost' => 1,
 'smtp_user' => '',
 'smtp_password' => '',
 'smtp_server' => 'smtp.gmail.com'));
}

function expert_deactivate () {
 wp_clear_scheduled_hook('expert_msgcheck');
 unregister_setting('experts-settings-group', 'expert_settings');
 delete_option('expert_settings');
}

I’ve changed my earlier approach here from a variable expert_onpost to adding all related options into an array. Just learning as I go, and reading over Handling Plugins Options in WordPress 2.8 with register_setting() many times to see if I could figure out what’s going on there.

Remember we used the new API’s register_setting() call in a previous article? Well that’s still compatible with add_option() so it’s safe to set default values for the options with this. I have included the deactivation code though, just to show that you still need to use delete_option() as unregister_setting() does not take care of this for you.

I also added a parameter validation function:

register_setting( 'experts-settings-group', 'expert_settings','expert_onpost_validate');

function expert_onpost_validate ($input) {
 // Our first value is either 0 or 1
 $input['onpost'] = ($input['onpost'] == 1 ? 1 : 0);
 return $input;
}

This simply checks whether the variable onpost is actually a boolean. I haven’t included any validation checks on the other variables yet.

So with the registered variables in place it becomes really very easy to do the actual form building / handling:

function expert_settings_page() {
?>

Experts

 
 
 
 
 On Post in Expertise Section
 
  /> Do Nothing  /> Send Email
 
 
 
 SMTP username
 
 
 
 
 
 SMTP password
 
 
 
 
 
 SMTP server

Notice that there is no form handling in the plugin itself anymore! That’s all done by WordPress itself.

So now that we can actually set some required options, let’s add this send_email() function:

function send_email () {
 // PHP Mailer Variables
 if (!class_exists("phpmailer")) {
 require_once(ABSPATH.'wp-includes/class-phpmailer.php');
 }
 $expert_settings = get_option("expert_settings");
 $mail = new PHPMailer();
 $mail->Mailer   = "smtp";
 $mail->Username = $expert_settings['smtp_user'];
 $mail->Password = $expert_settings['smtp_password'];
 $mail->Host     = $expert_settings['smtp_server']
 $mail->SMTPSecurity = "tls";
 $mail->Post     = 465;
 $mail->SMTPAuth = true;
 $mail->CharSet  = "utf-8";
 $mail->Encoding = "quoted-printable";
 $mail->FromName = "3DN Techblog <3dn@3dn.nl>";
 $mail->AddReplyTo = "Fred Leeflang ";
 $mail->Subject  = "Test Email";
 $mail->Body     = "Testing gmail functionality";
 $mail->AddAddress("fredl@dutchie.org");
 if ($mail->Send()) {
 return 1;
 } else {
 return 0;
 }
}

And add a call to this function in the hourly_msgcheck() function just to see if it works:

function hourly_msgcheck () {
 send_email();
}

If you find this article interesting you might want to read some more articles in the WordPress category:

Or in the Coding category:

If you have any questions regarding WordPress, check out our Wordpress page or our Programming page. Note: The code I’m writing about is constantly under development. I can’t write about every little change I make but I try. I’m learning as I go because this is my first WordPress plugin. If you’re interested in the latest code you can always look in SVN through my public Trac server or simply download the latest development copy.

Expertise Shortcode

Fred Leeflang — Mon, 15 Feb 2010 14:25:35 +0000

WordPress has a mechanism for adding ‘shortcodes’ authors can use in their articles through a plugin. In an earlier article I described how to get started with writing your own WordPress plugins. In this article I’ll show how to add a handy shortcode to the plugin that generates code in the expert pages which allows people to register as experts in a certain area of expertise.

Functionality

Every time I create a new expertise page I try to write a brief introduction to the subject. I also want to add a button to this page. When people click on the button they should get a little popup window where they’re asked to indicate their expertise level. This button is mostly repetitive code which only differs in a few parameters (like ‘which expertise page are we on right now’)

WordPress’ shortcode mechanism is not the best mechanism to get this done but I want to add it this way mostly for educative purposes.

Adding the Shortcode

It’s real simple to add the shortcode to our plugin:

add_shortcode('expertise', 'expertise_shortcode');

That’s really all there is to adding the shortcode. Ofcourse we still need some code to implement expert_shortcode():

function expertise_shortcode ($att) {
 $expert = <<
EOM;
 return $expert;
}

After we added this code to our Expertise plugin, inserting [expertise] into our articles/pages should display a very basic button. Why you still see [expertise] in this article even though the plugin is currently active is because I used double [['s in the article.

The above is ofcourse the easiest thing I could think of to make an introduction from.

Hyperlinks

Besides adding a button on the expertise page, we could also use this shortcode to link to the expertise page from withing an article. We could ofcourse make an entirely new shortcode for that but it's not neccesary at all; We can add attributes to the shortcode. Let's agree first that we'll give every expertise page it's own 'expertise' custom field which holds the name of the expertise. Custom fields are easy to add in the 'Edit Page' screen. As the value for this 'expertise' field we choose a simple name like 'Linux'.

Now we'll add an attribute link to the expert shortcode so we can use it like [expertise link=Linux]. The expertiselink attribute is optional so if we don’t add it we’ll still get the ugly button but if we do add it, the plugin will look in WordPress’ database to find the URL of the page that has custom field ‘expertise’ set to ‘Linux’ and display code for a hyperlink to that page with all the titles etc.

function expertise_shortcode ($atts) {
 global $wpdb;

 // Extract attributes and set defaults if not present.
 extract(shortcode_atts(array(
 'link' => 0,
 ), $atts));

 if ($link) {
 $expertpost = $wpdb->get_row("
 SELECT wposts.*
 FROM $wpdb->posts wposts, $wpdb->postmeta wpostmeta
 WHERE wposts.ID = wpostmeta.post_id
 AND wpostmeta.meta_key='expertise'
 AND wpostmeta.meta_value='$link'
 AND wposts.post_status='publish'
 AND wposts.post_type='page'
 ", ARRAY_A);
 $url = get_permalink ($expertpost['ID']);
 $expert = <<{$expertpost['post_title']}
EOM;
 } else {
 $expert = <<
EOM;
 }
 return $expert;
}

That code looks a bit more complex already. First of all we’re using the shortcode_atts() function to check if the attribute link is set in $atts. If it’s not set, it gets the default value of 0. So whether link is set or not becomes an if-then-else construct that determines whether to show the ugly button or an equally ugly link. When $link is set it will be set to ‘Linux’ or something along those lines. We should also do some filtering on this later as it’s value is put into a SQL query and we don’t really want to encourage SQL-injection.

The SQL query uses $wpdb, hence the global $wpdb declaration at the top of the function. If everything works well the query should return a row with all the wp_posts columns set. This sample code doesn’t have error checking yet, which it really should have as the query could also return 0 rows (if the author made a typo, or the expertise page administrator has forgotten to add the expertise custom field).

Finally here’s an example using [expertise link=Wordpress], please go see our Wordpress page!

If you liked this article, maybe you want to read more in the WordPress category:

Or if you have any questions about this article or WordPress in general you might want to visit our Wordpress page.

Adding an Expertise Section to WordPress

Fred Leeflang — Mon, 15 Feb 2010 08:16:55 +0000

I’ve been thinking about a way to get people to add links to our blog on their site. A friendly way to do this is by adding an ‘expertise’ section to the site where people can go after they sign up. Here people can ask questions which will be emailed to the section maintainer(s) so they can answer any questions involving their expertise as timely as possible.

This is not a standard WordPress functionality however so I’m going to write my own WordPress plugin for this.

Requirements

I first created an ‘Expertise’ page to the blog. This page is freely accessible without having to log in. Then I created some pages with the Expertise page as it’s parent page. We need to have the ‘Member Access‘ plugin installed on the blog in order to make the separate expertises member-only. The first three expertise pages I set up were for ‘Linux/Unix’ (maintainers: FredLeeflang, TigerP), ‘Programming’ (maintainers: FredLeeflang, TigerP) and ‘IPv6′ (maintainers: TigerP).

I manually added the ‘maintainers’ custom field to each of the separate expertise pages to get started. When the plugin is done this field should be added automatically.

Getting Started with the Plugin

Creating a plugin for WordPress is easy. Simply go inside the wp-contents/plugin directory, create a new directory there and some files and you’re on your merry way. I also took some effort to import the directory into my public subversion server:

svn import experts https://secure.dutchie.org:444/svn/trunk/experts

So you should also be able to check out the source while I’m developing it by:

cd wp-contents/plugins
svn co https://secure.dutchie.org:444/svn/trunk/experts

So all I did to get the plugin to show up with some meaningfull information was to add a file experts.php and a readme.txt. The expert.php has a header in it:

/*
Plugin Name:    Experts
Plugin URI:     http://wordpress.3dn.nl/experts/
Description:    This plugin allows you to add experts to several pages on your site. Experts will get notified when a comment on the page is posted, allowing them to quickly respond even though they don't check the site every day.
Author:         Fred Leeflang
Version:        0.1
Author URI:     http://wordpress.3dn.nl/

Setup:
 1) Install the plugin.
 2) Go to the admin menus, and in the "Options" panel, select "Expers".
 4) Configure the plugin if you need.

*/

Which by itself is sufficient to make the plugin show up like this in the admin -> Plugins section:

Obviously this doesn’t make the plugin do anything yet but it just goes to show that having a header in a file makes the plugin show up with the correct description etc. in the plugin admin screen, ready to be activated!

Got Admin Options?

First we want to make a basic admin page. This is easily done with:

add_action('admin_menu', 'expert_ap');

function expert_ap() {
 //create new submenu under 'Settings'
 add_submenu_page('options-general.php', 'Expertise Settings','Expertise Settings', 'administrator', __FILE__, 'expert_settings_page');

 //call register settings function
 add_action( 'admin_init', 'register_expertsettings' );
}

function register_expertsettings() {
 //register our settings
 register_setting( 'experts-settings-group', 'onpost', 'intval' );
}

This is not complete yet but this shows two important mechanism; adding a submenu to an existing (eg. ‘Settings’) menu and registering settings for our plugin.

The add_submenu_page() function links our settings menu under WordPress’ settings (through using options-general.php), gives it a label, sets which capability is required and sets which PHP function must be called when the user selects the menu (expert_settings_page() which we have not added yet).

The add_action() function adds the function register_expertsettings() to the admin_init section of the page. There’s actually some pretty tricky stuff going on in register_expertsettings(), people who have coded plugins ‘the good old way’ will find out what I mean later. Essentially the register_setting() call adds a variable and a variable validation to a pulldown we’ll design later on. There will be no $_POST processing, HTML filtering etc, WordPress will do all that for us. We just need to make sure that the form POST’s to options.php and make sure that the variables we want to get from the form get registered with register_setting().

The Form

Because of letting WordPress handle our variables, we only need to build the form itself in expert_settings_page().

function expert_settings_page() {
?>

Experts


 
 
 
 On Post in Expertise Section

On Post in Expertise Section

Sample Expertise Area

I’ve set up a sample expertise area for WordPress Expertise. While I’m developing this plugin further I’ll post some more followup in there and probably later on I’ll add one or more articles about the development so stay tuned!

If you enjoyed reading this article you might also like other articles in the Coding category:

Or in the WordPress category:

Both older and newer articles in the Coding category will be listed here. Should you need (free!) WordPress Expertise, please feel free to check out our WordPress Expertise area.

New Colors

Fred Leeflang — Tue, 19 Jan 2010 13:39:52 +0000

New Colors

A while ago I decided to use the ‘smells like facebook’ theme. The navigation is familiar to some 350 million people and in general I think the facebook layout isn’t bad. Some people complained that it looks too much like facebook yet it isn’t, which is confusing.

So I compromised and since a new author will soon be writing about green technology I made the blue facebook shades look green. I think I rather like it myself! I’d love to hear your comments. One thing still remains to be done which is the search magnifying glass. Other than that I might have forgotten some things, so please let me know.

Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.

Meanwhile, please let me know how you feel about this layout / colors in the poll above.

Disabling Facebook Connect

Fred Leeflang — Wed, 13 Jan 2010 12:51:06 +0000

For a while I’ve been experimenting on this blog with the Facebook Connect plugin. While it seems like a great idea I’ve been experimenting lots of small irritating problems with it.

When I click on the Admin link, on random moments the site decides that I’m no longer logged in through Facebook.
When I need to login on the Admin screen again while I was logged in through Facebook, the plugin sometimes updates the Facebook user’s information. Sometimes the email address is overwritten, sometimes the user’s first and last name are reset etc.

Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.

If you have similar experiences with this plugin, please let me know. For now I would really like to know if my Facebook friends appreciate having the possibility to log in using their Facebook account.

Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.

3DN Technology » wordpress

Playing with Simple Facebook Connect

New 3DN Techblog

Add Ajax to Expertise Plugin

Using SACK

Periodic Expertise Events

Activation Code

Work with Me

Experts

Read More

Expertise Shortcode

Functionality

Adding the Shortcode

Hyperlinks

Read More

Adding an Expertise Section to WordPress

Requirements

Getting Started with the Plugin

Got Admin Options?

The Form

Experts

Sample Expertise Area

Read More

New Colors

New Colors

Disabling Facebook Connect

On Post in Expertise Section	/> Do Nothing /> Send Email
SMTP username
SMTP password
SMTP server