Congratulations to ZF developer team, and congratulations to us all, PHP developers around the world.

As Bill Karwin, ZF product manager, said, “please click C:\Windows\Media\tada.wav now”.

Link: Download ZF 1.0.0

Oh yes, the compatibility issue. Ok, since i’m rewriting all my web apps using Zend Framework now, i guess I don’t have much choice except to switch my PHP installed on my server to PHP5 (Zend Framework was written in PHP5).

Why would i use Zend Framework? two words: beautiful and simple. ZF knows very well how to use the power which comes with PHP5. OOP and design pattern are well written all over the place. Having a quick look at Zend_Controller will explain why i say this.

About the simplicity, Aaron Warmus put it well when he said this,

When evaluating the code within Zend Framework, it was clear that the concept of “Extreme Simplicty” meant that when faced with design decisions, Zend Framework always went with using the power which is built into PHP5 …

In a couple words, extreme simplicity means not reimplementing functionality already available in PHP5.

download mean girls 2 film in hd formats

ZF now in days away from its stable version (currently in 1.0.0-RC2). As many other people out there, i hope ZF will be the rescuer of PHP5 slow adoption. In broad, i hope it will make alot easier for us to build a profesional yet reliable web apps using PHP.

Anyway, i’m switching my server now, wish me luck.

What? are you kidding me, off course i passed the exam.

So now i’m officially Zend certified engineer.

Thanks to Brainmatics for such a good effort preparing my test.

Now, there are three Zend certified engineers from Indonesia. Rock on, dude!

PHP Abstract is Zend Developer Zone‘s new podcast for PHP developers. It was announced on may 17th 2007, but the first episode was just online today.

PHP Abstract episode 1 talks about PHP security tips by Eli, the author of PHP 5 in Practice. It is a short duration talks, but pretty useful.

Link:

PHP Abstract Feed

Since Ngeblog 0.2 now uses the modified version of Zend_Gdata, the files is getting larger and it is hard for me to put Ngeblog 0.2 to phpclasses. So for now on you can download the source here or you can use svn to get the latest files on Google Code project hosting here.

Try out the demo here for ClientLogin authentication and here for AuthSub authentication. You can see the source code here and here for both demo respectively.

Alright, now let’s look what is new with Ngeblog.

Using ClientLogin Authentication

By the time of this writing, Zend_Gdata hasn’t supported ClientLogin authentication. But they promised to implement it soon. So for now, Ngeblog uses my own ClientLogin class for Zend_Gdata. Please read my previous post to understand how it works.

To use Ngeblog with ClientLogin authentication, you must first include the file like this,

  set_include_path(dirname(__FILE__) . '/Ngeblog');
  require_once 'Ngeblog/ClientLogin.php';

assuming Ngeblog is located in Ngeblog directory.

As i said in my previous post, you need a token to be able to access Blogger (or any other Google Services). And you must authenticate yourself to get this token. Here is how you can do that with Ngeblog,

  $resp =  Ngeblog_ClientLogin::getClientLoginAuth($username,$password);

if your username and password is correct and you have at least one Blogger account for that username then you’ll get $resp['auth'] as the token (authentication code). Use this token to create an instance of Ngeblog class, like this:

  $myblog = Ngeblog_ClientLogin::Connect($resp['auth']);

$myblog is an instance of Ngeblog class which can be used for viewing post(s),updating post or deleting post. All of this operation is described in my previous post. Or you can see the source code for ClientLogin demo here to get the picture.

As an illustration, the following codes will add a new post for blog id 839898989 :

<?php

  set_include_path(dirname(__FILE__) . '/Ngeblog');
  require_once 'Ngeblog/ClientLogin.php';

  $username = 'yourusername';
  $password = 'yourpassword';
  $resp =  Ngeblog_ClientLogin::getClientLoginAuth($username,$password);
  if ( $resp['response']=='authorized' )
  {
    $myblog = Ngeblog_ClientLogin::Connect($resp['auth']);

    $title = 'My Title';
    $content = 'Here is the content';
    $blogid = '839898989';
    $myblog->newPost($title,$content,$blogid);
  } 

?>

Using AuthSub Authentication

To use Ngeblog with AuthSub authentication, you must first include the file like this,

  set_include_path(dirname(__FILE__) . '/Ngeblog');
  require_once 'Ngeblog/AuthSub.php';

To get AuthSub token, first you need to ask your users to log into their Google Accounts authentication. Use Ngeblog_AuthSub::getAuthSubTokenUri() to show this URI. Here is the example to do that:

  echo 'You must <a href="'.Ngeblog_AuthSub::getAuthSubTokenUri().'">login</a> first to use our service.';

When they click the link, they will be prompted to log into their Google Accounts and grant/deny your web application to access their Blogger account. Once it’s authorized (and granted by them), Google redirects the user back to your web application with additional token in the query string which looks something like this:

http://www.yourwebapp.com/blogger.php?token=CKF50YzIHxCT85KMAg

You can use this token to create an instance of Ngeblog class like this:

  $myblog = Ngeblog_AuthSub::Connect($_GET['token']);

As an illustration, the following codes will update a post for blog id 839898989 and entry id 938393839383938:

<?php

  set_include_path(dirname(__FILE__) . '/Ngeblog');
  require_once 'Ngeblog/AuthSub.php';

  if ( !isset($_GET['token']) ) {
    echo 'You must <a href="'.Ngeblog_AuthSub::getAuthSubTokenUri().'">login</a> first to use our service.';
  } else {
    $myblog = Ngeblog_AuthSub::Connect($_GET['token']);

    $newtitle   = 'My New Title';
    $newcontent = 'Here is my new content';
    $blogid  = '839898989';
    $entryid = '938393839383938';
    $myblog->editPost($entryid,$title,$content,$blogid);
  } 

?>

Using Session to Hold The Token

This is the major change in Ngeblog 0.2. As you might have noticed this, the old version of Ngeblog holds the token information in Class scope. Which means that you have to re-authenticate yourself each time you access the page.

In current version, i separated the authentication layer from the actual operation layer. This way, you only need to authenticate once and holds the token information for the rest of operation. One way to hold this token information is by using session.

As you can see in ClientLogin demo file, this is how you can do to use session to hold the token information,

  set_include_path(dirname(__FILE__) . '/Ngeblog');
  require_once 'Ngeblog/ClientLogin.php';

  session_start();

  if (!isset($_SESSION['clientlogin_token']))
  {
    if (isset($_POST['username']) && isset($_POST['password']))
    {
      try {
        if (isset($_POST['captchatoken']) && isset($_POST['captchaanswer'])) {
          $resp =  Ngeblog_ClientLogin::getClientLoginAuth($_POST['username'],$_POST['password'],$_POST['captchatoken'],$_POST['captchaanswer']);
        } else {
          $resp =  Ngeblog_ClientLogin::getClientLoginAuth($_POST['username'],$_POST['password']);
        }
      } catch ( Exception $e )  {
        echo $e->getMessage();
        exit;
      }

      if ( $resp['response']=='authorized' )
      {
        $_SESSION['clientlogin_token'] = $resp['auth'];
        header('Location: '.$_SERVER['PHP_SELF']);
        exit;
      }
      elseif ( $resp['response']=='captcha' )
      {
        echo 'Google requires you to solve this CAPTCHA image <br />';
        echo '<img src="'.$resp['captchaurl'].'" /><br />';
        echo '<form action="'.$_SERVER['PHP_SELF'].'" method="GET">';
        echo 'Answer : <input type="text" name="captchaanswer" size="10" />';
        echo '<input type="hidden" name="captchatoken" value="'.$resp['captchatoken'].'" />';
        echo '<input type="submit" />';
        echo '</form>';
        exit;
      }
    }

    // if session doesn't exist, show login form
    echo '<form action="'.$_SERVER['PHP_SELF'].'" method="post">';
    echo 'Username: <br /><input type="text" name="username" size="45" /><br />';
    echo 'Password: <br /><input type="password" name="password" size="45" /><br />';
    echo '<input type="submit" value="Login" />';
    echo '</form>';
    exit;
  }
  else
  {
    if ($_GET['cmd']=='logout') {
      unset($_SESSION['clientlogin_token']);
      header('Location: '.$_SERVER['PHP_SELF']);
      exit;
    }
  }

and this is how to do it for AuthSub authentication,

  set_include_path(dirname(__FILE__) . '/Ngeblog');
  require_once 'Ngeblog/AuthSub.php';

  session_start();

  if (!isset($_SESSION['authsub_token'])) {
    if (isset($_GET['token'])) {
      $session_token =  Ngeblog_AuthSub::getAuthSubSessionToken($_GET['token']);
      $_SESSION['authsub_token'] = $session_token;
    } else {
      echo 'You must <a href="'.Ngeblog_AuthSub::getAuthSubTokenUri().'">login</a> first to use our service.';
      exit;
    }
  }
  else
  {
    if ($_GET['cmd']=='logout') {
      Ngeblog_AuthSub::AuthSubRevokeToken($_SESSION['authsub_token']);
      unset($_SESSION['authsub_token']);
      header('Location: '.$_SERVER['PHP_SELF']);
      exit;
    }
  }

Please note that you need Ngeblog_AuthSub::getAuthSubSessionToken($_GET['token']) to upgrade a single use token to a session token. And to revoke AuthSub session token you need to use additional Ngeblog_AuthSub::AuthSubRevokeToken($token) besides unset(). This is because AuthSub session tokens don’t expire; your client can store the session token for as long as needed. Therefore it must be revoked to clear granted access to your web apps.

After played around with it for hours, i finally got into a decision to use Zend Gdata for abstracting Ngeblog connection to Blogger. Unfortunately, Zend GData class library only supports AuthSub authentication, while Ngeblog already uses ClientLogin authentication and works fine so far.

So, to make it available for both type of authentication, i finally sat down and wrote some codes myself to add ClientLogin support for Zend GData. You can download the bundle in .zip here or in .tgz here which contains both original Zend_Gdata bundle and my Zend_Gdata_ClientLogin class for ClientLogin authentication.

How it works

To understand how this class works, you must first understand how Google account authentication works. Please read the manual for that. But i try to explain it anyway.

Authentication is required to access any of Google Services such as Google Calendar, Google Base or Blogger. To do that, first you must provide username and password to log into your Google account. And then once your login is authorized, Google will give you a token to identify yourself for accessing the desired Google Service.

Currently there are two kind of authentication that Google uses. AuthSub authentication and ClientLogin authentication. As the manual said, AuthSub is used for web application that offers a service to access Google Service. While ClientLogin is used for installed application, such as desktop or handheld application.

But that doesn’t mean you can’t use ClientLogin for web application. It’s just that with ClientLogin authentication you must handle the authentication programmatically yourself to get the token. While with AuthSub you only need to redirect your web users to log into Google Account web site and grab the token as the result once they authorized.

Now, let’s get to the business. To use this class, you must first include Zend.php and load Zend_Gdata_ClientLogin class, like this:

  require_once 'Zend.php';
  Zend::loadClass('Zend_Gdata_ClientLogin');

Then use getClientLoginAuth method to get the token (authorization code), like this:

  $username     = 'yourusername';
  $password     = 'yourpassword';
  $service      = 'blogger';
  $source       = 'Ngoprekweb-Zend_Gdata-0.1.1'; // companyName-applicationName-versionID

  try {
    $resp = Zend_Gdata_ClientLogin::getClientLoginAuth($username,$password,$service,$source);
    print_r($resp);
  } catch ( Exception $e )  {
    echo $e->getMessage();
  }

As you can see, there are four parameters required for this method: username, password, service and source. You can read about these parameters here.

The results of this method will be in three possibilities:

First

, if the authentication is success (authorized by Google), the output will be something like this,

Array
(
    [response] => authorized
    [auth] => DQAAAGgA...dk3fA5N
)

Second, if the authentication is failed for some reasons, it throws exception. About the reason of this failure, the manual said:

Please note that ClientLogin does not differentiate between a failure due to an incorrect password or one due to an unrecognized user name (for example, if the user has not yet signed up for an account).

Third

, if Google requires you to solve CAPTCHA challenge, the output will be something like this,

Array
(
    [response] => captcha
    [captchatoken] => DQAAAGgA...dkI1LK9
    [captchaurl] => http://www.google.com/login/captchaALD$ALSJ4.png
)

About CAPTCHA challenge, the manual said,

ClientLogin uses standard security measures to protect user account information. To block bots and other entities from breaking user passwords, Google Accounts may add a visual CAPTCHA� to the authentication process when the server suspects an illegal intrusion, such as after too many incorrect login attempts. A CAPTCHA ensures that a real person is attempting login, and not a computer trying random strings (a dictionary attack).

Handling CAPTCHA Challenge

As i mentioned above, when Google requires you to answer CAPTCHA challenge (when she suspects you as an intruder ), you’ll get both captchatoken for identifying which CAPTCHA image you received, and captchaurl that shows you the location of the image you have to answer (to tell miss Google you are human, not bot).

To answer that challenge, you use the same getClientLoginAuth method, only now with two additional parameters: captchatoken and captchaanswer.

  $username     = 'yourusername';
  $password     = 'yourpassword';
  $service      = 'blogger';
  $source       = 'Ngoprekweb-Zend_Gdata-0.1.1'; // companyName-applicationName-versionID
  $captchatoken = 'DQAAAGgA...dkI1LK9';
  $captchaanswer= 'brinmar';

  try {
    $resp = Zend_Gdata_ClientLogin::getClientLoginAuth($username,$password,$service,$source,$captchatoken,$captchaanswer);
    print_r($resp);
  } catch ( Exception $e )  {
    echo $e->getMessage();
  }

If you ARE really human, then most likely you’ll get something like this as the result,

Array
(
    [response] => authorized
    [auth] => DQAAAGgA...dk3fA5N
)

which means you’re now authorized to use Google Service you requested, in this case is Blogger. Use $resp['auth'] as your token (authorization code) to do the rest of operation (query, add, edit or delete posts in your Blogger).

In Action: Reading Blogger

This far, some of you might said, “what in Google Earth is this guy talking about?!”.

Alright kids, grab your emacs or UltraEdit, here comes the example. What we’re going to do here is to get the entries of your Blogger, for comparing purpose with what Zend does using AuthSub (see my previous post here).

<?php
/**
 * Testing Zend_Gdata_ClientLogin for getting list of Blogger entries
 *
 * written by: Eris Ristemena (http://www.ngoprekweb.com/tags/php)
 *
 */

  set_include_path(dirname(__FILE__) . '/Zend_Gdata');
  require_once 'Zend.php';
  Zend::loadClass('Zend_Gdata_ClientLogin');
  Zend::loadClass('Zend_Gdata');
  Zend::loadClass('Zend_Feed');

  $username     = 'yourusername';
  $password     = 'yourpassword';
  $service      = 'blogger';
  $source       = 'Ngoprekweb-Zend_Gdata-0.1.1'; // companyName-applicationName-versionID
  $logintoken   = $_GET['captchatoken'];
  $logincaptcha = $_GET['captchaanswer'];

  try {
    $resp = Zend_Gdata_ClientLogin::getClientLoginAuth($username,$password,$service,$source,$logintoken,$logincaptcha);

    if ( $resp['response']=='authorized' )
    {
      $client = Zend_Gdata_ClientLogin::getHttpClient($resp['auth']);
      $gdata = new Zend_Gdata($client);
      $feed = $gdata->getFeed("http://www.blogger.com/feeds/default/blogs");

      foreach ($feed as $item) {
        echo '<h3><a href="'.$item->link("alternate").'">' . $item->title() . '</a></h3>';
        $_id = explode("/",(string) $item->id());
        $blogid = $_id[count($_id)-1];
        $feed1 = $gdata->getFeed("http://www.blogger.com/feeds/$blogid/posts/summary");

        echo "<ul>";
        foreach ($feed1 as $item1) {
          echo "<li>";
          echo "<a href=\"{$item1->link('alternate')}\">{$item1->title()}</a><br />";
          echo "{$item1->summary()}<br />";
          echo "</li>";
        }
        echo "</ul>";
      }
    }
    elseif ( $resp['response']=='captcha' )
    {
      echo 'Google requires you to solve this CAPTCHA image <br />';
      echo '<img src="'.$resp['captchaurl'].'" /><br />';
      echo '<form action="'.$_SERVER['PHP_SELF'].'" method="GET">';
      echo 'Answer : <input type="text" name="captchaanswer" size="10" />';
      echo '<input type="hidden" name="captchatoken" value="'.$resp['captchatoken'].'" />';
      echo '<input type="submit" />';
      echo '</form>';
      exit;
    }
    else
    {
      // there is no way you can go here, some exceptions must have been thrown
    }

  } catch ( Exception $e )  {
    echo $e->getMessage();
  }

?>

Have fun. And please be kind to drop some comments below or report any bugs you find to my email (eristemena at ngoprekweb dot you know what).