The result was this article http://en.wikipedia.org/wiki/Postcodes_in_Australia#States_and_territories

And the PHP function is:

	/**
	/**
	* Returns the state for a postcode.
	* eg. NSW
	* 
	* @link http://en.wikipedia.org/wiki/Postcodes_in_Australia#States_and_territories
	*/
	function findState($postcode) {
		$ranges = array(
			'NSW' => array(
				1000, 1999,
				2000, 2599,
				2619, 2898,
				2921, 2999
			),
			'ACT' => array(
				200, 299,
				2600, 2618,
				2900, 2920
			),
			'VIC' => array(
				3000, 3999,
				8000, 8999
			),
			'QLD' => array(
				4000, 4999,
				9000, 9999
			),
			'SA' => array(
				5000, 5999
			),
			'WA' => array(
				6000, 6797,
				6800, 6999
			),
			'TAS' => array(
				7000, 7999
			),
			'NT' => array(
				800, 999
			)
		);
		$exceptions = array(
			872 => 'NT',
			2540 => 'NSW',
			2611 => 'ACT',
			2620 => 'NSW',
			3500 => 'VIC',
			3585 => 'VIC',
			3586 => 'VIC',
			3644 => 'VIC',
			3707 => 'VIC',
			2899 => 'NSW',
			6798 => 'WA',
			6799 => 'WA',
			7151 => 'TAS'
		);
 
		$postcode = intval($postcode);
		if ( array_key_exists($postcode, $exceptions) ) {
			return $exceptions[$postcode];
		}
 
		foreach ($ranges as $state => $range)
		{
			$c = count($range);
			for ($i = 0; $i < $c; $i+=2) {
				$min = $range[$i];
				$max = $range[$i+1];
				if ( $postcode >= $min && $postcode <= $max ) {
					return $state;
				}
			}
		}
 
		return null;
	}

The pharmacy locator takes the postcode of the user and plots the 5 nearest pharmacies on a map for the user to see. The technology behind this maps each pharmacy address to latitude and longitudes, maps the postcodes main latitude and longitude and then uses some advanced mathematical calculations to calculate the distance (it’s not as simple as trigonometry, although it would of been before this was proven wrong). This means that even if you hard pharmacies in a different locale (a lot of store locators match a postcode to a locale and then simply return all stores in that locale), state or country the closest 5 will always be returned.

The job involved a front website which could be used as informational purposes and then also a shop which could accept payments online. Magento was used as the platform for the online store and a custom Magento theme was developed which would match the look & feel of the front website. The online store also integrates with Australia Post for delivery costs and PayPal for processing order payments.

The front website also integrates inside the Magento category structure and allows the front website to display categories from the shop, this provides multiple gateways into the shop to promote more purchases.

The site runs off the same Content Management System as Without Surgery, Skills Connect. The CMS allows the updating of videos, images, menus and more. They can even update the location of the coral see on the Google map (even though I don’t think it’s going anywhere sometime soon). The site also utilises caching to provide maximum performance when under heavy load, especially when the television commercial comes in late September.

In addition, the site is also integrated with Campaign Monitor.

So last night I mashed up a quick web app which used jqTouch and the Harvest API. Now I can check my invoices from anywhere, and I abstracted it enough so anybody out there can use it.

Check it out (on your iPhone) at http://scripts.waww.com.au/harvest_invoices

So I came up with a function that would first look inside the custom domain and if nothing was found then it would naturally work inside the default domain. The function is named __dd(), which is short for default domain.

/**
 * Allows you to override the current domain for a single message lookup.
 * If the msg doesn't exist in the current domain, it will use the default
 * domain.
 *
 * @param string $domain Domain
 * @param string $msg String to translate
 * @param string $return true to return, false to echo
 * @return translated string if $return is false string will be echoed
 */
function __dd($domain, $msg, $return = false) {
	$d = __d($domain, $msg, true);
	if ( $d == $msg ) {
		return __($msg, $return);
	}
	if ( $return ) {
		return $d;
	}
	else {
		echo $d;
	}
}

I’m not sure why the CakePHP gods haven’t done it this way, I’m pretty sure there would be a reason though. The idea came to me with the recent feature addition of domains to my settings plugin (documentation).

The Model Validation Rules

<?php
class Product extends AppModel {
 
	var $name = 'Product';
 
	var $validate = array(
	    'title' => array(
    		'notEmpty' => array(
    			'rule' => 'notEmpty'
    		),
	    )
	);
}
?>

The View Template

<div class="products form">
<?php echo $form->create('Product', array('type' => 'file'));?>
	<fieldset>
 		<legend><?php __('Add Product');?></legend>
	<?php
		$options = array(
			'error' => array(
				'class' => 'errorField',
				'email' => 'Please enter a product title'
			)
		);
		echo $form->input('title', $options);
		echo $this->element('attachments', array('plugin' => 'media'))
	?>
	</fieldset>
<?php echo $form->end('Submit');?>
</div>
<div class="actions">
	<ul>
		<li><?php echo $html->link(__('List Products', true), array('action' => 'index'));?></li>
	</ul>
</div>

Which, when submitting the form with an empty product title would you give the error message of “Please enter a product title” inside a div with the class “errorField”, however Cake forgets the custom error class and gives the “error-message” class.

What Happened?

I got this code…

<div class="input text error">
    <label for="ProductTitle">Title</label>
    <input type="text" class="form-error" id="ProductTitle" value="" maxlength="255" name="data[Product][title]"/>
    <div class="error-message">Please enter a product title</div>
</div>

What was expected?

This…

<div class="input text error">
    <label for="ProductTitle">Title</label>
    <input type="text" class="form-error" id="ProductTitle" value="" maxlength="255" name="data[Product][title]"/>
    <div class="errorField">Please enter a product title</div>
</div>

The Fix

After looking through the core code, I traced the problem down into the error function of the FormHelper. The input() function only passes the $field name and the $text variable as the options submitted in the original “error” key to the options passed to the input() function.

In the error function, if the $text array contains the key of the error type, then it disregards the rest of the $text array, forgetting the custom error class. What we need to do is set the $options variable to $text if it is in array, as well as pull the custom message for the error type, kapeech? OK, I’ll just give you the code…

Before

411
412
413
414
415
416

if (is_array($text) && isset($text[$error])) {
	$text = $text[$error];
} elseif (is_array($text)) {
	$options = array_merge($options, $text);
	$text = null;
}

After

411
412
413
414

if (is_array($text)) {
	$options = array_merge($options, $text);
	$text = isset($text[$error]) ? $text[$error] : null;
}

I never like touching core code so I’m hoking the cake devs will be able to get on this for the next release, and it looks like I just missed the next release, as CakePHP 1.2.5 just popped up on my reader.

I have submitted a ticket at http://code.cakephp.org/tickets/view/76

Something like…

I’ve released the datasource to make this happen as part of my Util plugin for CakePHP. To get started please see the Wiki page.

Util is just a plugin full of unrelated libraries for CakePHP, most of the code there is from other people.

Currently only for MySQL but you only have to change one line for different databases.