I’m at it again! We had another tree problem the other day which I was involved in fixing. However, this wasn’t a standard sized tree, it was huge!

I whipped out the tree inspector and starting working away on the tree. Everything was going smoothly, but with such a large tree and so many levels deep, it became really confusing, really fast!

I’ve updated the tree inspector with +, - and | placed strategically so it looks a little more like the trees as displayed in Explorer (on Windows). I will update this to use images at some point, but I didn’t want to make the distribution of the tree inspector hard (at the moment it is one file, and nice and easy to install). I’ll look into embedding images into the HTML using base64 encoding.

I’ve also encountered a seemingly common problem with the basic HTTP authentication that I added in the last version. On a couple of windows based servers the basic http controlled authentication (using the WWW-Authenticate header) wasn’t working properly (better described here).

If you’re working with a shared host, this is not always so easy to fix. In this instance, it was easier to comment the authentication code out of the script, upload, use it and then delete the file. I decided to make it easier to disable the authentication, and now you can turn it on or off by changing the bUseAuthentication variable at the top of the script.

Happy tree fixing.

I had a situation this morning, in which I had to whip out the Tree Inspector to resolve a problem with a FarCry tree. Some of the nlevel values were wrong, but Tree Inspector didn’t allow me to fix those; so now it does!

I’ve added a version number to the top (along with a h1 title), and you can now modify the nlevel values by checking the checkbox appearing next to each node.

It also occurred to me, that if this file sits unprotected on a website, someone who knows the name of the file can do some real damage. So I’ve added basic Authentication support to the script so it is now protected by default.

You should change the username and password before using the script, and I suggest you upload the file, use it and then remove it. Just like the install directory (that comes with FarCry), this is a file that shouldn’t be sitting on a production server.