deb http://ftp.cyconet.org/debian etch-backports main non-free contrib

Selfnote: Dump the wordpress user into separate domU

With 2.3 there where many infrastructure changes. For a complete list, see the Release Announcement. The most extensions breaking change was the implementation of native tag support. Referencing to Not working Plugin List Ultimate Tag Warrior and Extended Live Archives are problematic. Both caused troubles on update, but there is a fix for ELA and one for UTW. By reviewing the informations for writing this articel, I noticed that I’m running fine with the Ultimate Tag Warrior Bugfix Release provided by Christine from the Internet.
My theme K2 was needing also an update, which caused the style to be broken. So waiting for a fix did take little longer, but when reviewing it, I noticed that only a css class name did need an update.
This all teaches me, when using a project with much depencies, it will be a mess when updating, as long as isn’t all provided by one source. It’s some kind of using a project “still in development”.
Update: While we are at “still in development” .. I updated to 2.3.1-RC1 some seconds ago. :)

Next pity, some extensions or any equivalents aren’t available for wordpress 2.3 (yet). If you run multiple blogs via the stock debian package and wan’t to make use of the new wordpress version in any of your sites, you have update all at once … which maybe not a way you want to go. I decided to repackage wordpress 2.3.0 as wordpress23, which allows you to install wordpress (<<2.3.0) and wordpress23 at same time.

If you want to use debian plugin, widget or theme packages or use these from your normal wordpress installation (/usr/share/wordpress) with wordpress23, you need to symlink the dirs.

For example:

# mv /usr/share/wordpress23/wp-content/plugins/ /usr/share/wordpress23/wp-content/plugins.orig
# mv /usr/share/wordpress23/wp-content/themes/ /usr/share/wordpress23/wp-content/themes.orig
# ln -s /usr/share/wordpress23/wp-content/plugins /usr/share/wordpress/wp-content/plugins
# ln -s /usr/share/wordpress23/wp-content/themes /usr/share/wordpress/wp-content/themes

Remember that package updates of wordpress or wordpress23 may overwrite parts of /usr/share/wordpress/wp-content/[plugins|themes] in such situation. BE CAREFULL!

You can get the stuff via apt-line:

deb ftp://ftp.cyconet.org/debian wordpress main non-free contrib

Or directly from: http://ftp.cyconet.org/debian/archive/wordpress/

The actual package list is:

wordpress-plugin-af-extended-live-archive
wordpress-plugin-ald-spa
wordpress-plugin-all-in-one-seo-pack
wordpress-plugin-exec-php
wordpress-plugin-google-sitemap-generator
wordpress-plugin-landingsites
wordpress-plugin-lightbox-2
wordpress-plugin-now-reading
wordpress-plugin-page-links-to
wordpress-plugin-photopress
wordpress-plugin-related-posts
wordpress-plugin-rolemanager
wordpress-plugin-sideblog
wordpress-plugin-spam-karma
wordpress-plugin-stats
wordpress-plugin-ubernyms
wordpress-plugin-utw
wordpress-plugin-utwgooglesitemaps
wordpress-plugins
wordpress-widget-category-cloud
wordpress-widget-samsarin-php
wordpress-widget-utw-cloud
wordpress-widgets
wordpress23

If you want a plugin or widget included and it makes sence to do so, drop me a mail, where to grab. Be aware that UTW isn’t supported since wordpress 2.3 anymore. A tag system was included into wordpress and you need to search replacements for all the nice UTW extension!

Stay tuned!

* Is the backport neccessary? I don’t think we should upload packages to bpo
simply because we can do it if you can install the package directly from
testing without any recompilation we shouldn’t add it to bpo. Pinning
exists.

So I’m not allowed to upload it to backports.org, but I did upload it to my repro, like the following other packages:

• backuppc
• collectd (from experimental)
• fuzzyocr3 (from experimental)
• gallery2
• libfile-rsyncp-perl
• php-suhosin
• xen-shell

You can download it by using the following line in sources.list:

deb ftp://ftp.cyconet.org/debian etch-backports main non-free contrib

I was digging around and noticed, that only 3 values in 3 files are related. So decided to make use of ‘$_SERVER["SERVER_NAME"]‘ to have unique cache directories.

Here comes the patch:

diff -Nur orig/af-extended-live-archive-options.php af-extended-live-archive-options.php
--- orig/af-extended-live-archive-options.php 2006-02-22 19:06:00.000000000 +0100
+++ af-extended-live-archive-options.php 2006-05-26 22:47:28.000000000 +0200
@@ -7,7 +7,7 @@
*/

// get settings and construct default;


Here is the patch:
--- /tmp/google-hilite.php 2005-06-17 02:36:02.000000000 +0200
+++ /usr/share/wordpress/wp-content/plugins/google-hilite.php 2006-05-26 00:17:32.000000000 +0200
@@ -81,6 +81,10 @@
break;

case 'wordpress':
+ if (preg_match('|^http://'. quotemeta($_SERVER["SERVER_NAME"]) .'|i', $referer)){
+ return false;
+ break;
+ }
if ( is_search() )
return true;