Notes Log » PHP http://noteslog.com Sat, 15 May 2010 13:31:55 +0000 en hourly 1 http://wordpress.org/?v=3.0 How to show a slow loading page http://noteslog.com/post/how-to-show-a-slow-loading-page/ http://noteslog.com/post/how-to-show-a-slow-loading-page/#comments Sun, 05 Apr 2009 22:52:59 +0000 Andrea Ercolino http://noteslog.com/?p=343 Problem – Slow loading pages are frustrating, for web users and developers too. Of course there are many possible tweaks you can use to speed them up, but sometimes you cannot optimize a page any further.

  • UPDATED 2009-10-11

Solution – If you can’t beat them, join them. You can show a progress indicator to let your web users know that your server is thinking hard the answer to their request, but how do you do that?

Requirement 1 – You cannot put the progress indicator on the leaving page, because you don’t want to modify every single reference to a slow page. It doesn’t make sense either: a slow page is slow by itself! You really don’t need that coupling.

Requirement 2 - You cannot put the progress indicator on the landing page, the slow one, because the browser needs it before the slow page has arrived. If they arrive together, the progress indicator is useless!

There is a good article about this issue but it fails at implementing the first requirement. Anyway that was the idea I worked on when starting this project.

Here is the waiting page that get’s loaded while loading the slow page. For browsers other than IE, the trick is to change the document.location.href property after loading the progress indicator image. In IE we change the document.location.href and then add the image.

I used jQuery to make it simple.

waiting.php

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd">

<html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml"><head>

<title>Loading Page...</title>

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3/jquery.min.js"></script>
<script type="text/javascript">
jQuery( function( $ ) {
	function redirect() {
		$('form').submit();
	}
	
	if($.browser.msie) {
		redirect();
		$('img').appendTo('body').attr('src', 'loading-page.gif');
	} else {
		$('#loading').bind('load', function() {
	        redirect();
	    }).attr('src', 'loading-page.gif');
	}
} );
</script>

</head><body>

<h1>Loading Page...</h1>
<img id="loading" />
<form method="<?php echo $method ?>" action="<?php echo $url ?>">
 <input type="hidden" name="waiting" value="<?php echo $waiting ?>" />
</form>

</body></html>

And here is the slow page.

slow-page.php

<?php

if ( ! isset($_REQUEST['waiting']) ) {
    $url = htmlspecialchars( $_SERVER['REQUEST_URI'] );
	$method = $_SERVER['REQUEST_METHOD'];
	$waiting = time();
	include "waiting.php";
    return;
}

sleep(10); //simulate a slow task

?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd">

<html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml"><head>
 <title>Slow Page</title>
</head><body>
 <h1>Hello World!</h1>
</body></html>

You can test it here.

]]> http://noteslog.com/post/how-to-show-a-slow-loading-page/feed/ 8 How to setup your web development environment http://noteslog.com/post/how-to-setup-your-web-development-environment/ http://noteslog.com/post/how-to-setup-your-web-development-environment/#comments Sun, 01 Feb 2009 20:19:14 +0000 Andrea Ercolino http://noteslog.com/?p=318 If you want to setup a web development environment in your PC, there are many options out there, so I’m going to describe the one that just worked for me.

This is a no-frills tutorial about how to setup a web development environment for PHP, using 

  • An EeePC 1000H as the local machine
  • A wireless ADSL network for the internet connection
  • WinXP/SP3 Home as the operating system
  • Apache as the web server
  • MySQL as the database management system
  • PHP as the source language
  • Subversion and Tortoise for source control management
  • Eclipse PDT as the integrated development environment
  • Zend Debugger for remote debugging
  • Zend Framework as the supporting framework

A PC connected to the internet

This is easy, you already have it, or you should. Mine is the EeePC, with WinXP Home.

Apache, MySQL, PHP

This is very easy too. There are many all-in-one packages, but I feel at home with the WampServer.

  • Download and install the WampServer 2.0

These versions are currently bundled:  Apache 2.2.11, MySQL 5.1.30, PHP 5.2.8, phpMyAdmin 3.1.1

Subversion and Tortoise

XP-Dev is my choice for Subversion hosting. Easy to setup and free. Nobody else will get access to your code by default, but you can change it as needed. Slick interface, fast updates and commits, (apparently) trustworthy.

  • Create your account at XP-Dev. You’ll currently get 1500 MB of svn hosting space.
  • Login and create your first repository. Its name will be <your XP-Dev account>_<your repository name>

Tortoise is my choice for the svn administration. Easy to setup and free (again).

  • Download and install Tortoise.

Tortoise is for dummies like me. Just righ click in a folder and the contextual menu will show all the needed options.

  • Create a local folder for mirroring your remote project repository. Don’t put it under the www folder of Apache.
  • Checkout the repository there. This will setup the link between them.
  • Into the local folder create the classical trunk, tags, and branches folders.
  • Commit all back to the repository, together with a nice comment.

If all goes well, your new source control management system is correctly setup.

Eclipse PDT

Eclipse PDT is my preferred IDE for PHP. There’s an all-in-one distribution, that’s very easy to setup. Well, it couldn’t be easier: no setup at all.

  • Download and install Java
  • Download and unzip Eclipse PDT into the root of a disk unit, like C:

It’s important that you unzip into the root, otherwise some files won’t unzip due their long path names. Eventually, you’ll get an eclipse folder, containing an eclipse executable.

  • Start eclipse and learn how to move around.
  • Create a new PHP project, into the trunk folder.
  • Open the trunk folder from WinXP and add to the ignore list of Tortoise all the files automatically created by eclipse. Then commit.

Zend Debugger

Even if you think that the Zend Debugger was bundled with the all-in-one Eclipse PDT, follow this step too. In fact, that Zend Debugger is not for server debugging, while this one is.

  • Download and unzip Zend Debugger.
  • Follow the short instructions of the readme file to intall it. For editing the php.ini, use the link provided by WampServer.

Zend Framework

You could use any other framework, or no framework at all, but I know the Zend Framework quite a bit.

  • Download and unzip the Zend Framework.

The Zend Framework site provides a QuickStart tutorial that sets up an “Hello World” application.

  • Activate in Apache (WampServer) the rewrite module.
  • Create in Apache (WampServer) an alias from ‘project’ (trim apostrophes) to the trunk folder of your project.
  • Go back to the IDE and code in the QuickStart tutorial. Don’t put the ZF library into the trunk/library folder. Instead leave it where it is and put its path into the include_path directive of php.ini, using WampServer.

That’s much better, because your current ZF library version won’t replicate by means of svn to your remote repository, and when a new version will be available, you can change the include_path directive to point to it, and change it back if something goes wrond (sometimes it does), without moving files around.

Moreover, you can use the trunk/library folder for your own library files. I suggest a personal folder for your reusable classes like forms, elements, filters, and validators, and a Zend folder that mirrors the Zend Framework when you need to fix a bug in a class, or hack something into the ZF library.

Due to the fact that the PHP interpreter will scan the trunk/library folder before the external ZF library folder (if you set up the include_path as shown in the QuickStart tutorial), you can “overwrite” the ZF library classes with your copies if you need, on the fly, maintaining them well apart.

First debugging session

Now your web development environment should be setup and you can start your first debugging session.

  • Open the home page http://localhost/project/ in a browser.
  • Start the debugger at that page, using Eclipse PDT. Check that the URL into the Debug Configuration dialog is correct, and the option ‘Break at first line’ is checked.
  • Explore the code step by step.
  • If all is OK then commit, else fix bugs.

Start developing

That’s alll. Now it’s up to you.

]]> http://noteslog.com/post/how-to-setup-your-web-development-environment/feed/ 4 Enzymes 2.0 Released Today http://noteslog.com/post/enzymes-20-released-today/ http://noteslog.com/post/enzymes-20-released-today/#comments Sat, 10 Nov 2007 22:55:43 +0000 Andrea Ercolino http://noteslog.com/post/enzymes-20-released-today/ Enzymes is a WordPress Plugin for retrieving properties and custom fields of posts, pages, and authors, right into the visual editor of posts and pages, and everywhere else.

I’m releasing now Enzymes 2.0 which is quite a step forward. The features are

  • a new syntax for retrieving properties of posts, pages, and authors; as well as the old syntax for custom fields
  • a new syntax for identifying posts and pages by means of their slugs; as well as the old syntax with their numbers
  • a new elaborate method allowing for an easier processing of indirect arguments
  • a new merging method helping at crafting how the pathway is built by evaluation enzymes
  • slash and backslash templating uniformly supported by transclusion and evaluation enzymes
  • a cleaner code
  • a new manual
  • new examples
A WordPress Plugin

This version is available for download from wordpress.org

The previous version

I released Enzymes 1.2 one year ago from mondotondo.com, and re-released it as version 1.3 one month ago from wordpress.org. Both were almost the same thing. Here are the only differences:

  • updated the description header, accounting for the new address (notelog.com)
  • removed the signals to my server for activation / deactivation of the plugin
  • packaged as a wordpress plugin, available for download from wordpress.org
]]> http://noteslog.com/post/enzymes-20-released-today/feed/ 0 How to add semantics to WordPress posts http://noteslog.com/post/how-to-add-semantics-to-wordpress-posts/ http://noteslog.com/post/how-to-add-semantics-to-wordpress-posts/#comments Fri, 02 Mar 2007 09:49:35 +0000 Andrea Ercolino http://noteslog.com/?p=151 Browsing the WordPress’ ideas repository I’ve found one that could make WordPress fill the gap between a blog tool and a knowledge base: Structured Blogging.

The fact that it got 60 votes but only 50% stars means two things:

  1. voting people are lazy thinkers
  2. it’s a difficult task at many levels

Nonetheless it’s a good idea because this is and will be for many years to come the blogging era, where millions of authors post content to the Internet. There is no good reason for that content to be unstructured except lazyness and complexity.

Nothing can be done about lazyness but complexity can be substantially reduced. The solution needs:

  • a mechanism for adding XML tags from some dictionary
  • a template system for showing XML content appropiately

On the path to something readily usable (I hope Matt will provide it in WordPress 3.0), a mechanism could be a jQuery plugin for the visual editor, and a template system could be based on Enzymes.

Autocompletion

I think that tinyMCE can be extended by plugins, but I don’t know how to. jQuery itself has an autocompletion plugin that could be used this way. When an author presses a < key, the autocompletion gets triggered and the popup … pops up :-)

If you have ever used IME (for Japanese for example), you should know what I mean. Options are organized in a hierarchy and you get the most relevant at the top, depending on the few characters already typed. XML dictionaries could be ajaxed and locally cached; they could be plugins that you install into your blog, or be web services too; they could be international standards compliant or be completely custom.

The most-relevant-first feature of the autocompletion popup would be a big help for authors. If I already opened a Tag, then the most relevant options after pressing < could be:

  1. the closing tag for that Tag
  2. any tag that could be inside that Tag (properly sorted if needed)
  3. any root of the cached dictionaries (if possible in Tag)
  4. an option for accessing additional dictionaries (if possible in Tag)

Templates

A PHP template for properly rendering XML content is very easy to write, and Enzymes could be used in the clockwork. In fact an Enzymes feature is the possibility of easily transcluding all the content of a post or a page by means of the special char *

The XML to HTML template can be transformed in an Enzymes template with a couple of PHP instructions, thus allowing you to almost copy and paste already available templates. Then you could apply a solution like this:

  1. write a private post or page with the XML content, using the autocompletion feature described above (say this post is #123)
  2. write a public post or page with the Enzymes statement {[123.* /template.php]} in its content

The post in 1. needs to be private because you don’t want it to appear on the blog as is, and 2. makes the transformation happen. As an added benefit, you can display that semantic content inside of a greater context, and you can transclude it wherever you want in your WordPress blog (as many times as you like).

]]> http://noteslog.com/post/how-to-add-semantics-to-wordpress-posts/feed/ 0 How to Highlight Mixed Language Source Code http://noteslog.com/post/mixed-language-snippets/ http://noteslog.com/post/mixed-language-snippets/#comments Fri, 16 Feb 2007 15:35:29 +0000 Andrea Ercolino http://noteslog.com/?p=143 Web pages contain many snippets from different languages, like HTML, PHP, CSS, and JavaScript. Chili 1.x cannot highlight mixed language source code automatically, but the forthcoming released Chili 2.0 will be is able to do that.

Meanwhile, if you are using a Chili + Enzymes setup, then it’s possible to write an Enzymes template capable of making Chili 1.x highlight a web page perfectly (expanding on my previous php template).

Here is the new updated (2007/02/19) chili-web.php Enzymes template. At the moment it supports XHTML, and embedded CSS, JavaScript, and PHP snippets.

'.htmlentities( $code ).''; } function snippet_php( $open, $code, $close ) { return snippet_wrap( 'html', $open ).snippet_wrap( 'php', $code ).snippet_wrap( 'html', $close ); } function php_inside_html( $matches ) { list( $all, $before, $open, $code, $close ) = $matches; if( '' == $open ) return snippet_wrap( 'html', $all ); else return snippet_wrap( 'html', $before ).snippet_php( $open, $code, $close ); } function php_inside_css( $matches ) { list( $all, $before, $open, $code, $close ) = $matches; if( '' == $open ) return snippet_wrap( 'css', $all ); else return snippet_wrap( 'css', $before ).snippet_php( $open, $code, $close ); } function php_inside_javascript( $matches ) { list( $all, $before, $open, $code, $close ) = $matches; if( '' == $open ) return snippet_wrap( 'javascript', $all ); else return snippet_wrap( 'javascript', $before ).snippet_php( $open, $code, $close ); } function php_inside( $class, $code ) { return preg_replace_callback( '/(?:(.*?)(\<\?php\s)(.*?)(\?\>))|(?:.+)/si', "php_inside_$class", $code ); } function snippet_web( $class, $open, $code, $close ) { return snippet_wrap( 'html', $open ).php_inside( $class, $code ).snippet_wrap( 'html', $close ); } function format_code( $matches ) { list( $all, $before, $open, $tag, $code, $close ) = $matches; if( '' == $open ) { return php_inside( 'html', $all ); } else { switch( $tag ) { case 'script': $class = 'javascript'; break; case 'style' : $class = 'css'; break; default : $class = 'html'; } return php_inside( 'html', $before ).snippet_web( $class, $open, $code, $close ); } } function format_clean( $out ) { do { $len = strlen( $out ); $out = preg_replace( '/(\[^<]*)\<\/code\>\/is', '$1', $out ); } while( $len != strlen( $out ) ); return $out; } } ?> 

)(.*?)(\<\/\3\>))|(?:.+)/is', 'format_code', $this->result );
	echo format_clean( $out );
?>

The WordPress file /wp-content /themes /default /comments-popup.php is a page that uses all the supported languages, so it’s a good test for the previous template:

<?php echo get_option('blogname'); ?> - Comments on <?php the_title(); ?>

Comments

RSS feed for comments on this post.

ping_status) { ?>

The URL to TrackBack this entry is:

post_password) && $_COOKIE['wp-postpass_'. COOKIEHASH] != $post->post_password) { // and it doesn't match the cookie echo(get_the_password_form()); } else { ?>

  1. by — @

No comments yet.

comment_status) { ?>

Leave a comment

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed:

" />


ID); ?>

Sorry, the comment form is closed at this time.

Powered by Wordpress

Chili & Enzymes confirm to be a perfect match.

]]> http://noteslog.com/post/mixed-language-snippets/feed/ 4 Enzymes 1.2 Released Today http://noteslog.com/post/enzymes-12-released-today/ http://noteslog.com/post/enzymes-12-released-today/#comments Mon, 25 Dec 2006 14:48:01 +0000 Andrea Ercolino http://noteslog.com/?p=96 Changes

  • Fixed a bug in the metabolism outside a post. For example, a title transcluding a custom field by means of an implicit reference rendered correctly when viewing the post but not when the title appeared in a list of post titles.

Files

]]> http://noteslog.com/post/enzymes-12-released-today/feed/ 9 AdSense Enzymes http://noteslog.com/post/adsense-enzymes/ http://noteslog.com/post/adsense-enzymes/#comments Wed, 06 Dec 2006 08:26:39 +0000 Andrea Ercolino http://noteslog.com/?p=93 AdSense Enzymes are very simple.

At the simplest level of abstraction, I can directly trasclude the custom field which I’ve stored the ad code into. And I can do it either by means of a statement into the content of a post or a page, or by means of a call to the metabolize function (available in Enzymes 1.1) into the php code of a WordPress template file.

The former method is useful when I want to place an ad unit in a particular/variable position inside the content of a post or a page; the latter method is useful when I want to place an ad unit in a general/constant position inside the blog.

For example, if I put the statement {[1.ad001]} here, it would reproduce by itself the ad unit right here, because in the first post I’ve stored the ad code in a custom field called ad001. But to make the ad unit appear before any post, I need to find the line in the index.php file of my default theme that reads

and replace it with this line

Taking the abstraction one step further, I’d like to store the string 1.ad001 in a new home field, so that I can provide a separation layer that makes it possible for me to replace the ad code simply by changing the content of a field, rather than having to change the php file again.

Indirect transclusion is not directly available in Enzymes, but it can be easily achieved by means of a simple enzyme like this

preg_match( '/'.$this->e['substrate'].'/', $this->substrate, $matches ); return $this->item( $matches['sub_id'], $matches['sub_key'] );

I’ve called this enzyme get, and I’ve put it into the first post. So the Enzymes statement becomes {[1.get(1.home)]} and the edited line for the index.php file becomes

I’m currently using the latter for my blog home, so I don’t have to worry about placing ads every time I post a new log, and the former for my pages, so that I can place the ads insdide the content, in a position that I hope will fit better.

Why does Google limit to three the number of ad units per page? Is it a technical reason?

 

]]> http://noteslog.com/post/adsense-enzymes/feed/ 5 Enzymes 1.1 Released Today – updated http://noteslog.com/post/enzymes-11-released-today/ http://noteslog.com/post/enzymes-11-released-today/#comments Fri, 01 Dec 2006 23:06:11 +0000 Andrea Ercolino http://noteslog.com/?p=90 Changes

  • the title and the excerpt are now directly supported, together with the content
  • any location of a WordPress theme is now supported

Example

  • open the php file you are interested in (eg: sidebar.php)
  • select the location where you want the enzyme’s result to appear (eg: before the last closing ‘div’)
  • paste there a code like this
  • save and test
  • generic custom field keys are now supported. Just wrap your international, multiworded key in a pair of ‘=’ and you are done (any ‘=’ your key may include must be escaped by ‘\’)

Example

  • escaped: {[.=æ°´=]}
  • metabolized: mizu (æ°´) means water
  • no bug fixes, hence no need to upgrade, except for getting the new features
  • backward compatibility preserved, hence no reason not to upgrade :-)

Files

]]> http://noteslog.com/post/enzymes-11-released-today/feed/ 0 Entity enzyme, or The pacman effect strikes back http://noteslog.com/post/entity-enzyme-or-the-pacman-effect-strikes-back/ http://noteslog.com/post/entity-enzyme-or-the-pacman-effect-strikes-back/#comments Thu, 09 Nov 2006 16:18:27 +0000 Andrea Ercolino http://noteslog.com/?p=83 This is so much a basic enzyme, as it is also necessary for what it does.

If you want to represent an HTML entity in a post, you’re going to struggle with the escaping / unescaping issue.

For example, to write that an ampersand is represented by an ampersand followed by ‘amp;’ is not as visually appealing as it is to show it right away, like & = &amp;

You begin this adventure by writing & = &amp; and after a Save and Continue Editing you get & = &, which is certainly true but not what you meant.

You think, well it’s obvious, I should have used that HTML trick in the first place. Do you remember that trick, don’t you? You have to escape the ampersand twice: it works in a plain HTML file. You think that the WordPress editor should have done it by itself: it’s simple enough! But you want things done, you’re not interested in polemical discussions with your beloved blogging tool. So you write & = &amp;amp; and go for another SaCE roundtrip and & = &amp; shows up.

Wow! You’ve done it, pal. Time for a reward. Go for a coffee and back soon. You’re inspired now, not a good idea to waste too much time.

Just before the last molecules of coffee disappear from your tongue, you want to check that all is OK for a Publish trip, and go back trough your post. Suddenly you see something that makes you feel guilty for a simple coffee, whose taste was still there, just because. You saw it right, it was & = &amp; but now it is & = & again!! How can it be?

Soon you’ll discover that that old trick is useless. It only delayed the problem twice. Yes, each time you Save your post, an &amp; of your escaped entity gets unescaped automatically, that is & eats amp; up. So &amp;amp; will be &amp; after the first new Save, and & after just the second one. & = pacman.

Well, you only lose a couple of battles. You recently installed that new plugin that promised miracles about transclusions, don’t you? Yeah, Enzymes was its name.

OK, lets add a custom field called ‘amp’ with &amp; as its value. Then write & = {[.amp]} and save and continue editing. Try it now, you’ll see that this solves the issue.

Done? Isn’t it wonderful?

What? What are you saying? It doen’t work?!?! My Enzymes is bullsheet? Well, I’m sorry. I put many hours of my life in it, and it’s a bit ungrateful on your side, considering that I didn’t charge you a dime!

Are you sure you did exactly what I said? Please check again. Have you found the problem? Yes, that is the problem. The pacman effect strikes back! The & in your ‘amp’ custom field ate its ‘amp;’ up.

Ehi man, stop joking now! Tell me the solution please, I’m exhausted!

The solution is:

add a custom field called ‘entity’ with ‘echo htmlentities( htmlentities( $this->substrate ) );’ as its value (without quotes). Then write & = {[.entity(.amp)]}

Remember this post pal! You’re going to use it over and over: {[123.entity(123.amp)]}, if the ID of your post is 123.

]]> http://noteslog.com/post/entity-enzyme-or-the-pacman-effect-strikes-back/feed/ 0 Chili & Enzymes http://noteslog.com/post/chili-enzymes/ http://noteslog.com/post/chili-enzymes/#comments Wed, 08 Nov 2006 02:01:32 +0000 Andrea Ercolino http://noteslog.com/?p=81 UPDATE (2008-03-20): There is a new post about Chili & Enzymes. Thanks to their new versions, it’s now much easier to config WordPress highlighting than described here.

If you post many code snippets, then Chili and Enzymes can work together for making your life simpler.Here is my proposed configuration:

1. Install Enzymes
Download the latest version to your computer, upload it to your server, in the ‘plugins’ directory under ‘/wp-content’, and activate it. No configuration needed.

2. Upload jQuery and Chili
For this configuration I’m going to put the file ‘jquery-1.0.3.pack.js’ in a ‘jquery’ directory under the ‘/wp-content’ directory, and the file ‘chili-1.1.pack.js’ in a ‘chili’ directory under the ‘jquery’ directory. In the ‘chili’ directory I’ll put also any recipes and stylesheets I’ll need.
I recommend to upload and setup at least one of the examples provided with Chili. It’ll be useful for proving that Chili is properly configured (bypassing WordPress).

3. Upload an Enzymes template for each language you’ll use
In fact there are many valid alternatives, but I think that this one is pretty simple and you can eventually expand on it. Here is the template I’m going to use for JavaScript snippets: 

result ); 
?>
Note that the template decides the style of the ‘pre’ tag and that the result is automatically escaped. Anyway this is still a naive template, which is not suitable for javascript snippets mixed into html snippets. Remember that the base directory for Enzymes templates is ‘wp-content’.

4. Add style settings to the stylesheet of your current WordPress theme
You should provide only general format for the tags you are going to use for wrapping your code snippets. For example, I’m going to use a ‘pre’ tag wrapped around the ‘code’ tag. In the style.css file, I’ll add these definitions: pre.chili-all { color: #333333; background-color: #f4f4f4; font-size: 9pt; line-height: 120%; width: 450px; overflow: auto; } pre.chili-clip { color: #333333; background-color: #f4f4f4; font-size: 9pt; line-height: 150%; width: 450px; height: 450px; overflow: auto; } pre.chili-all code, pre.chili-clip code { font-size: 9pt; line-height: 150%; }As you see, they are very similar: chili-all adjust the height of the box to the length of the content; chili-clip fixes the height to a maximum.

5. Edit the header.php file of your current WordPress theme
This is to enable support for Chili in each HTML page of the blog. It’s just three script elements: two for loading jQuery and Chili, and one for configuring Chili.

The following two items must appear in the ‘head’ section, maybe just before the closing tag. The following two items must appear in the ‘body’ section, maybe just after the opening tag.

6. Done, now test the configuration

  1. Create a new post titled “Testing Enzymes & Chili”. Hit ‘Save and Continue Editing’
  2. Add a custom field with a Key “js-snippet” and a Value “document.writeln( "Hello World!" );”
  3. Add this Enzymes statement “{[.js-snippet /enzymes/chili-js.php]}” into the post area
  4. Hit ‘Publish’ and then ‘View site’

If it looks like this document.writeln( "Hello World!" ); then all is fine. Enjoy!

]]> http://noteslog.com/post/chili-enzymes/feed/ 7