Encoding and decoding is a simple as this:

$s = new PHPShortener();
// encode a long url
$shorturl = $s->encode('http://devthought.com/projects/php/phpshortener/', 'is.gd');
// decode a short url (autodetects the service)
$longurl = $s->decode('http://tr.im/jBBp');

Head to the project page for downloads and documentation. Fork me on GitHub if you want to contribute!

#!/usr/bin/env php

This allows us to run the script without prefixing it with the “php” command, and instead we can run it like this:

chmod +x myscript  # This gives execution permissions to the script, do it only once
./myscript --first=option --second --third=option

If we want our script to take options like in the example above, we can use this snippet:

$options = array();

foreach ($argv as $arg){
	preg_match('/\-\-(\w*)\=?(.+)?/', $arg, $value);
	if ($value && isset($value[1]) && $value[1])
		$options[$value[1]] = isset($value[2]) ? $value[2] : null;
}

The $options array will hold the supplied options. You can then use them like this:

if (!isset($options['somevalue']))
	// show an error

if (isset($options['dosomething']))
	// do something

This is an extract from Devthought header.php WordPress template file:

All you have to do is change the routes to match your files. If you’re not using wordpress, you’ll have to remove the get_stylesheet_directory* and get_template_directory* function calls and replace with your paths.

To create a unique file with the right permissions use the tempnam function:

$filename = tempnam('/tmp_directory', 'filePrefix');

You can test this from the command line like this:

php -R 'tempnam("/tmp", "hello");'

The output file looks something like this:

guillermo-rauchs-macbook-pro-15:tmp willy$ ls -la hello*
-rw-------  1 willy  staff  0 Mar 11 03:26 helloyvEzzb

Couple this function with sys_get_temp_dir and you’ve solved the dilemma:

$filename = tempnam(sys_get_temp_dir(), 'filePrefix');

One of them is -d, which alters a php.ini value for the duration of the command. An example is as follows:

php5 -d memory_limit=128M symfony propel:data-load

This was a real time saver considering the server was not setup with a CLI-specific php.ini, like some are.

First we define the getters and setters for the plaintext password in the AdminUser model:

  public function setPasswordPlain($plain)
  {
    if(! empty($plain))
        $this->setPassword(sha1($plain));
  }

  public function getPasswordPlain()
  {
    return "";
  }

Then, in generator.yml we add this field to form sections, using the display parameter:

      form:
        display:              [login, password_plain, email]

If we try the generator now, we’ll get an error message telling us that password_plain widget does not exist, which is true. The new admin generator uses the great Symfony 1.2 forms system, which treats a form as a set of widgets and validators.

If we inspect the lib directory of our generated module we’ll notice the file called adminsGeneratorConfiguration.class.php. This file extends BaseAdminsGeneratorConfiguration which, if we look closely, configures what form is related to this generated module:

  public function getFormClass()
  {
    return 'AdminUserForm';
  }

What we have to do is obvious. We extend AdminUserForm, and we override that method to return the name of our new class. In the same lib directory we create the form:

class myAdminUserForm extends BaseAdminUserForm
{

  public function configure()
  {
    parent::configure();

    $this->setWidget('password_plain', new sfWidgetFormInput());
    $this->setValidator('password_plain', new sfValidatorString(array('max_length' => 255, 'required' => false)));
  }

}

and finally we alter the adminsGeneratorConfiguration accordingly:

class adminsGeneratorConfiguration extends BaseAdminsGeneratorConfiguration
{

  public function getFormClass()
  {
    return 'myAdminUserForm';
  }

}

• It’s one of the first things people notice.
• It’s visible in the window chrome, the tabs, the bookmarks
• It’s something search engines pay attention to

WordPress settings allow you to set the blog title and description. With this modification, the description will be appended whenever a post title is not displayed, to avoid making it extremely long.

Edit the functions.php file of your template and append:

add_filter('wp_title', 'dv_wp_title', 100, 3);

$dv_append_subtitle = false;

function dv_wp_title($title)
{
  global $dv_append_subtitle;

  if($title === '')
    $dv_append_subtitle = true;

  return $title;
}

function dv_the_subtitle($sep = '—')
{
  global $dv_append_subtitle;

  if($dv_append_subtitle)
  {
    echo $sep ? $sep . ' ' : '';
    bloginfo('description');
  }
}

Then go to header.php and make your title tag look like this (notice that I added the dv_the_subtitle call)

And that’s it! If you want to customize the separator, which defaults to — pass it as an argument to dv_the_subtitle.

• Tables not deleted anymore upon installation
• Fixed SimplePie error report.
• Fixed small post content bug (not hidden by default)
• Fixed cron url
• Removed inverted quotes from queries
• Fixed notices in debug mode
• No error showing for campaigns w/o feeds fixed

Click here to download

As usual, head to Lighthouse for bug reports

Remember that, just like any release prior to 1.0, upgrading will erase your previous campaigns, feeds, logs, etc.

• Now compatible with WordPress 2.5
• Categories shown with indentation (parent > children now separated)
• SimplePie updated to 1.1.1, and SimplePie Core now supported.
• Fixed broken cron command
• Fixed broken export on some systems
• Fixed broken redirect when resetting a campaign
• Everything now stored in GMT to avoid time issues. Gotten rid of NOW() functions in favor of WP time functions
• Fixed bug with validation upon deletion of feeds in existing campaigns
• Fixed bug with ‘allow comments’ setting.
• Fixed bug with logs dates
• Fixed bug with double quote escaping (fixes campaign templates / rewrite html bugs)
• Username in options tab changed to a more handy select box.
• Interface now looks better on IE (d’oh)
• Added many help files
• Fixed annoying duplicates bug
• Fixed small bug in import with labels

I need feedback on:

• All sorts of errors, warnings, notices, blank screens
• Styling problems, indicating Browser, OS, URL and a screenshot.
• Behavioral problems: bad dates, bad content, duplicates, etc
• Performance problems
• Unexpected behavior

Always include instructions on how to reproduce the issues please!

Go ahead and download it

Updates

• 1 – Fixed bugs with categories in edit mode and posts tools (thanks Mike)
• 2 – Fixed empty rewrite bug (thanks Mike) and replacements now case insensitive
• 3 – Fixed bugs with ‘use feed date’ option, footer copyright, bad dates in ‘view all’ logs, log message field made text, timestamps converted to datetime, ‘Clean logs’ function fixed (big changes, please test)
• 4 – Fixed bugs with older WP releases (now WP-o-Matic works with any version starting from 2.2). Now rewrite works with PHP4.
• 5 – str_ireplace bug fixed, allow comments bug fixed, now user can choose comments state.
• 6 – {content} not getting rewritten fixed, titles and other settings not being stored fixed.

Just writing to let you know that the upcoming release candidate of WP-o-Matic is being cooked and betatested!

This is a list of all the exciting changes, which include new features you’ve been requesting and lots of bugfixes

• Categories shown with indentation (parent > children now separated)
• Fixed broken cron command
• SimplePie updated to 1.1
• Fixed broken export on some systems
• Fixed broken redirect when resetting a campaign
• Everything now stored in GMT to avoid time issues. Gotten rid of NOW() functions in favor of WP time functions
• Fixed bug with validation upon deletion of feeds in existing campaigns
• Fixed bug with ‘allow comments’ setting.
• Fixed bug with logs dates
• Fixed bug with double quote escaping (fixes campaign templates / rewrite html bugs)
• Username in options tab changed to a more handy select box.
• Interface now looks better on IE (d’oh)
• New option added to select max number of items to process
• New option added to decide whether the permalink should point to the created blog post or to the source permalink
• New general option to get logs feedback while the campaign is being processed.

As usual, stay tuned. Sorry for not being able to respond and release with more frequency, but I’ve been really busy.