Chrome Milk 1.6.2 RC1 Screenshot

WordPress 2.7x reply form (jQuery thickbox)

A9 OpenSearch 1.1 Auto-discovery (OSD)

Various Microformats embed

Safari native search feature

WordPress 2.7x Comments Pagination

Download

• Chrome Milk 1.6.2 RC 1 ·(436 KB) · SHA1 cheksum 76eb07ecc9d61fdabc33f9fb312842221e241e9d
• Chrome Milk 1.6.2 RC 1 (tar.gz) · (377 KB) · SHA1 cheksum836b6859225b036f750143019a0b50f2b2e7f85c

More on this → Chrome Milk 1.6.2 Release Candidate 1

The error notices is a total garbage, its something I’m not familiar with.

What surprised me is not the actual javascript errors but because google gears files is register as default wordpress scripts and running in the background, loaded via wp_default_scripts action hook filters (ref: script-loader.php Line:195) and there is no possible way to disabled this script from being loaded without editing the main files.

Attachments

1. Firebug Console Debug

   

2. Firebug Console: Loaded object, DOM tree

   

This was tested on Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9) Gecko/2008062315 (Gentoo) Firefox/3.0 & Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.15) Gecko/20080623 Firefox/2.0.0.15

More options

Google gears is a third party provider for wonderful client storage applications (Structured client-side storage) and by all meant not all end-user will be using this features (because some are really concern with their privacy).

IMHO its a good practice to have an options to disabled google gears (not running in the background) and should be handle like the XML-RPC settings in WP 2.6.

hope to see more clean version of wordpress for 2.6 release.

wp-config & wp-load files

Most plugin depend on “absolute path” to wordpress system file (wp-config.php). So the problem is there.

Lester-chan (GaMerZ) has this to say regarding the new WordPress 2.6 constant change.

The constant only get loaded when you load WP. Plugins will have problem finding wp-config.php or wp-blog-header.php from the plugin file.

might be broken in WP 2.6

require_once('../../../wp-config.php');

Long story, short

Below is my workaround for quick plugin activation setup. Its not the best solution as it involved the dirty “write-permission”, it need improvement. If you intent to uses it, there is few preliminary step to be set first:- ↓

1. browse to your plugin dir
2. create a blank php file: constant.php
3. copy paste the below code save it as new file relative to the constant.php
4. create or set your .htaccess and add Options All -Indexes.

Custom wp config file

function my_plugin_write_config()
{
	$constant = get_defined_constants(true);
	$user_defined = $constant['user'];
	unset($constant);

	$constant = array();

	// assuming that all latest wordpress CONSTANT start with WP_
	$wp_constant_prefix = "/WP_/";

	foreach($user_defined as $k=>$v){
		if (preg_match($wp_constant_prefix,$k)){
			$constant[$k] = $v;
		}
	}

	unset($user_defined);

	$constant['ABSPATH'] = (strtr(realpath(ABSPATH), array("\\", DIRECTORY_SEPERATOR)));
	$constant['WPINC'] 	= WPINC;
	$constant['WP_VERSION'] = get_bloginfo('version');

	$constant = array_map('json_encode',$constant);

	$my_plugin_config_file 	= dirname(__FILE__).DIRECTORY_SEPARATOR.'constant.php';

	if (is_writeable($my_plugin_config_file))
	{
		$content = "<?php if(!defined('MY_PLUGIN_TOKEN')) die('42');\n";

		foreach($constant as $k=>$v){
			$content .= sprintf('define(\'CONST_%1s\', %2s);',strtoupper($k),$v)."\n";
		}

		unset($constant,$k,$v);

		$content .= "?>";	

		$fp = false;

		if ( ($fp = fopen($my_plugin_config_file,'w+') ) != false) {
			stream_set_blocking($fp, TRUE);
			stream_set_timeout($fp,5);
			stream_set_write_buffer($fp, 0);
			fwrite($fp, $content);
			fclose($fp);
		}		

		unset($content,$my_plugin_config_file,$fp);

	} else {
		add_action('admin_notices','my_plugin_notification');
	}
}

function my_plugin_notification()
{
?>	<div id="message" class="error">
	<h3><?php _e('ERR') ?> </h3>
		<p><a href="http://doc.myplugin.com"><? _e('RTFM!'); ?></a></p>
	</div>
<?php
}

register_activation_hook(__FILE__, 'my_plugin_write_config' );
add_action('update_option_siteurl','my_plugin_write_config');
add_action('update_option_home','my_plugin_write_config');

Basically this script will search all user defined constant that start with “WP_” prefix, plus additional wordpress constant. Then it will write all these constant to disk inside “constant.php” (once). It also runs after a WordPress option has been update (active when user update settings for home & siteurl, I add the extra action hook just for example).

Deprecated Functions

Out of all this issue I still think WordPress as one of the best “back-compat friendly” CMS. Most of the legacy functions & variables (since version 0.71 >= 2.5) is still available inside WordPress system (wp-includes/deprecated.php). Not sure how long it will stay there..

Might be interested

• What You Need To Know About WordPress 2.6
• 10 Things You Need to Know About WordPress 2.6
• What Plugin Coders Must Know About WordPress 2.6