For multiple select based taxonomy:

(php)

$nodeObj->taxonomy = array(2=>array(15,19));

(python)

nodeOb['taxonomy']['2'] = [15,19]

For tags based taxonomy:

(php)

$nodeObj->taxonomy = array(
  'tags' => array(
         2=>'military,navy'
   )
);

Nginx WordPress Mu FastCgi_Cache Conf Rewrites are an interesting thing to get set up because of the cookie situation. You also don’t want to have wp-admin php files cached either.

One of the problems with mu supercache is it doesn’t have very good support for Nginx. By default I think the latest version turns off the supercache portion if it cannot detect the apache mod_rewrite module or htaccess file. This means supercache is automatically turned off for nginx servers.

The Nginx fastcgi_cache is blistering fast and makes supercache redundant for Nginx users.

Usually Nginx caches a response depending on whether you have added “X-Accel-Expires: 0″ in the response with the cookie. Then you include the cookie in your key. This seemed unnecessarily complicated to set up on the wordpress side. It did require a bit of lateral thinking to get something quick n dirty up and working that avoided the above approach.

Really the only content you want nginx fastcgi cached is any permalink running off /index.php the wordpress controller for all published page requests. I couldn’t get try_files working so I just flagged the rest. This set up is for cache to expire after one day for successful 302 and 200 requests.

Step One:

The first step is in the root folder of your Mu WordPress folder make a copy of your index.php file which is the wordpress controller and call it second_index.php.

example:

/home/mu/public_html/index.php
/home/mu/public_html/second_index.php

Of course in your root wordpress folder there will be all the standard other wordpress files and folders.

Step Two:

In the main http { } area of your nginx create an area where the cached files are to be stored:

http {

fastcgi_cache_path  /var/nginx_cache levels=1:2 keys_zone=one:100m inactive=7d max_size=4g;

...
...
...
}

The above configuration sets the path to where the cache will be stored. Level’s is the number of folders to use for the cache.

keys_zone is the name of the zone which you will specify in your fast_cgi parameters and 100m means that nginx will use up to 100m for to store the key values.

Inactive is the time that the cache file will stay in the cache inactive before its deleted. I’ve set this to a long time because I’d like to have static files cached for up to 7 days.

max_size is the size of the maximum cache size. I’ve set 4 gigabytes.

The cached files are stored as binary files. The key of the file is written in the binary file before the headers and the content. The file name of the cached fastcgi request is an md5 of the url. For example ‘bookmarks.honewatson.com/2009/09/02/nginx-wordpress-mu-fastcgi_cache-conf-rewrites/’ filename is 119a34a0e9e5817140836ffb44883df1. Using this knowledge I suppose a plugin could be written to grep through and delete the cache file if it is edited or comments are added.

Step Three:

Create a configuration that will direct all non-logged in cookie users to a location where requests are cached. For all other php files, do not cache. You don’t want to fastcgi_cache files of logged in users. No php files in wp-admin are cached. Any requests of logged in users are sent to second_index.php which is not cached. They can see regularly updated comments. You could also set it up so the cache time is much lower for logged in users. Maybe 5 minutes. I’ll include a second configuration down the bottom for this.

This means you get far greater control than you would with supercache.

So here is something that is working for me:

location / {
            	root   /home/mu/public_html;
            	index index.php;
		if ($http_cookie ~* "comment_author_|wordpress|wp-postpass_" ) {
			error_page       404 = /second_index.php?q=$uri;

		}
	    	error_page       404 = /index.php?q=$uri;
}

location ~ /index\.php.*$ {
	fastcgi_cache_key $host$request_uri;
	fastcgi_cache_valid 200 302 1d;
	fastcgi_cache_valid 301 7d;
	fastcgi_cache_valid any 5m;
	fastcgi_cache_use_stale off;
	fastcgi_cache one;
	fastcgi_ignore_headers  Cache-Control  Expires;
	fastcgi_pass   127.0.0.1:9000;
	fastcgi_index  index.php;
	fastcgi_param  SCRIPT_FILENAME /home/mu/public_html$fastcgi_script_name;
	include        /usr/local/nginx/conf/fastcgi_params;
}

location ~ \.php$ {
	fastcgi_pass   127.0.0.1:9000;
	fastcgi_index  index.php;
	fastcgi_param  SCRIPT_FILENAME /home/mu/public_html$fastcgi_script_name;
	include        /usr/local/nginx/conf/fastcgi_params;
}

Second configuration:

1. Cache any 200 or 302 published content requests from anonymous users for 1 day.
2. Cache any 200 or 302 published content requests for logged in users for 5 minutes.
3. Don’t cache any other php files.

location / {
            	root   /home/mu/public_html;
            	index index.php;
		if ($http_cookie ~* "comment_author_|wordpress|wp-postpass_" ) {
			error_page       404 = /second_index.php?q=$uri;

		}
	    	error_page       404 = /index.php?q=$uri;
}

location ~ /index\.php.*$ {
	fastcgi_cache_key $host$request_uri;
	fastcgi_cache_valid 200 302 1d;
	fastcgi_cache_valid 301 7d;
	fastcgi_cache_valid any 5m;
	fastcgi_cache_use_stale off;
	fastcgi_cache one;
	fastcgi_ignore_headers  Cache-Control  Expires;
	fastcgi_pass   127.0.0.1:9000;
	fastcgi_index  index.php;
	fastcgi_param  SCRIPT_FILENAME /home/mu/public_html$fastcgi_script_name;
	include        /usr/local/nginx/conf/fastcgi_params;
}

location ~ /second_index\.php.*$ {
	fastcgi_cache_key $host$request_uri;
	fastcgi_cache_valid 200 302 5m;
	fastcgi_cache_valid 301 1d;
	fastcgi_cache_valid any 5m;
	fastcgi_cache_use_stale off;
	fastcgi_cache one;
	fastcgi_ignore_headers  Cache-Control  Expires;
	fastcgi_pass   127.0.0.1:9000;
	fastcgi_index  index.php;
	fastcgi_param  SCRIPT_FILENAME /home/mu/public_html$fastcgi_script_name;
	include        /usr/local/nginx/conf/fastcgi_params;
}

location ~ \.php$ {
	fastcgi_pass   127.0.0.1:9000;
	fastcgi_index  index.php;
	fastcgi_param  SCRIPT_FILENAME /home/mu/public_html$fastcgi_script_name;
	include        /usr/local/nginx/conf/fastcgi_params;
}

Third configuration:

1. Cache uploaded files for 7 days – slip this extra configuration in before the all other php files location.

location ~ /wp-content/blogs\.php.*$ {
access_log  /nginx_logs/muimagesphp_cache.access.log small_php;
fastcgi_read_timeout 10;
fastcgi_cache_key $host$request_uri;
	fastcgi_cache_valid 200 302 7d;
	fastcgi_cache_valid 301 7d;
       fastcgi_cache_valid 504 1s;
	fastcgi_cache_valid any 5m;
	fastcgi_cache_use_stale off;
	fastcgi_cache one;
	fastcgi_ignore_headers  Cache-Control  Expires;
	fastcgi_pass   127.0.0.1:8084;
	fastcgi_index  index.php;
	fastcgi_param  SCRIPT_FILENAME /home/mu/public_html$fastcgi_script_name;
	include        /usr/local/nginx/conf/fastcgi_params;
}

location ~ \.php$ {
...
... etc

}

The following fix worked for me:

Install Drupal Tweaks, increase php memory, and mysql recommendations etc

http://drupal.org/project/drupal_tweaks

Download the following patches:

http://drupal.org/node/251792#comment-1831346

http://drupal.org/node/317775#comment-1491208

From command line copy patches to your root drupal directory.

cd to your root drupal directory and then apply the patches. Each time you will be asked where the file is for the patch and the actual path to the files to be patched will be provided in the command line. Just copy and paste each file path as presented into the prompt.


cp *.patch /home/drupal_directory/
cd /home/drupal_directory/
patch < no-router-blob-317775-56-D6.patch
patch < lock-251792-163-D6.patch

So in the above text you can see it gives you the path ‘includes/bootstrap.inc’. Just copy and paste that to where it says ‘File to patch:’. For each file it will provide you the correct path to the file assuming you are in the drupal root directory.

The final thing to do is to cp the lock.inc file which is created to includes/

You can use the php-fpm init.d script below. You need to change the variables at the start for your bin, conf, and pid to suit your set up.  PHP-FPM works great with Nginx.

Not sure if WordPress will format this script right so you can get as a text file here:

http://images.honewatson.com/random_files/php-fpm.txt

#! /bin/sh

esac

If you assign a template to a category or section menu item and you do not have articles which are part of that category as menu items, the article pages will also use the template assigned to the category or section.

If you then add an article as a menu item it will use the default template instead of the assigned template.

Place Here Placehere Content Item Module Joomla 1.5

The next step is to use the Google Maps suggestions mechanism.

To configure Nginx to load balance multiple FastCgi servers use this type of configuration:

upstream servercom {
server 127.0.0.1:44440;
server 127.0.0.1:44441;
server 127.0.0.1:44442;
server 127.0.0.1:44443;
server 127.0.0.1:44444;
}

location ~ \.php$ {
fastcgi_pass servercom;
fastcgi_index stream.app;
fastcgi_param SCRIPT_FILENAME /var/www/htdocs$fastcgi_script_name;
include /etc/nginx/fastcgi.conf;
}

If you’re using spawn-fcgi from lighttpd consider replacing it with php-fpm.

This is a simple tutorial that explains the basics.

These include PHP5 snippets for the Ebay Trading API.

It’s actually quite hard to find this both at Ebay and through Google.  Have you developed any php apps for the Ebay trading API?

If you have please let me know I need to hire somebody.