Cacti Error XML hash version does not exist

I thought I would write a quick post on this error, it is very simple to fix. If you receive the following error when importing a Cacti Template:

Error: XML: Hash version does not exist

This simply means the template was generated on a version of Cacti newer than the one you are importing to. Don’t despair, there are simple upgrade instructions on the cacti website.

Just make sure you make a full backup of your database and Cacti webfiles before attempting the upgrade (As a cautionary tale, if you installed cacti from a package you should first check to see if an updated package is available. Package installs can sometimes put the different files required in different places)

OpenSUSE AutoYast/AutoInstall Howto Part 1

OpenSUSE and SLES (SuSE Linux Enterprise Server) both come with AutoYaST which is a very powerful tool that allows administrators to quickly and easily deploy servers that have an identical configuration for rapid server deployment.

In this three part series we will explore creating a repository for use with multiple systems, creating and customizing the AutoInstall file, and finally running through an install procedure.

Part 1 – Creating a repository for use with multiple systems

In this part we will look at creating a local install repository for use with installing OpenSUSE. This can be done in several ways, one from the CD/DVD or with an RSync’ed copy of the repository.

Continue reading

WordPress 2.8 Indentation Issues

Ok, the indentation issues in WordPress 2.8 were caused by another plugin, SyntaxHighlighter Evolved. I upgraded to SyntaxHighlighter Evolved from Syntaxhighlighter Plus as Evolved claimed to have support for WordPress 2.8 whereas Plus is apparently not being updated anymore.

The next question I have is, now that WordPress has syntax highlighting in the backend with the code editor, can we use this function in our posts to have the native code highlighter work rather then needing a plugin?

WordPress 2.8 Gripe No. 1 (Indentation Issues)

My first complaint (quite possibly a fault) about WordPress 2.8 is that when using <pre> tags in a post if you switch between the Visual tab and the HTML tab all indent/space formatting is lost.

This is something that worked fine on WordPress 2.7.1 but fails on 2.8, as you can imagine this is a real pain if you are trying to post snippets of code or anything else that requires spaces/tabs for formatting. I am hoping there is a quick fix for this.

If anyone has any suggestions please let me know.

Upgrade to WordPress 2.8

And the verdict…. Nothing special.

The upgrade process was extremely simple. Just went through and updated all my plug-ins and theme to be 2.8 compatible and followed the three step upgrade process, and voila.

The admin interface has received a small polishing, with a new theme browser and theme installation method. I like the new editor for use with theme php & css files. The syntax highlighting and automatic documentation feature seems to be the best improvements for me.

So to sum up the installation went very smoothly, but unless you are into customising your themes or changing theme’s often then I don’t see any compelling reason to race out and upgrade.