Script updates
I had to do some update on the weblog script, because the vmswiki and the standard wiki-help paths wer not yet included. I took the opprotunity to some more enhancements: One annoying problem I found on some entries was a warning of a commandline being too long. Researching the issue, I found it was on writing a line to the log, that exceeded 256 characters. By adding “/SYSMBOL” to the WRITE command solved that problem. Still, I cut lines if ther exceed a certain size – just to be sure.
I also added a log line showing the file processed – handy in case of problems 🙂
The adapted script has run against all log files without an unexpected message.
WordPress 2.5
is out for a day now, and just to see how it would behave on OpenVMS, I downloaded the zipfile, and installed it. The basic requiremenst are humble and should fit the PHP engine (4.3) and MySQL (4.1) running on OpenVMS.
Installing required doing a bit of renaming – and that impacts all 2.2.3 blogs on the system: This one, “Trips, Tracks and Travels”, and the old bootcamp-2007 blog; the bootcamp-2008 blog runs WordPress 2.3 so that one wasn’t affected 🙂 by renaming wordpress.dir to wp223.dir. All logicals of the affected blogs needed this minor change included, and the operator entry page, that links straight into the basic, code-containing directories needed to be updated accordingly, as well as the file shat defines these logicals. Just a few minutes and the new definitions were implemented where required.
But once the new WordPress.dir was created and populated – and renamed to wp25 – the protections set properly, the configuration files fitted to fit MY requirements (have the access details out of the way) and an empty WP25 database created, the test blog could be accessed, the database got populated and I could login with the supplied , generated password. The result was a very, very basic page, without any formatting and scheme applied. The reason of this is simple: if set up, there is the assumption that the blog resides on a non-secired session – using http: as protocol. So I missed all stylesheets. This is not aproblem since eveey link you need is available. So the configuration page does come up when selected and the protocol can be changed from http to https, leaving avery other bits in place – and all of a sudden, the blog comes up formatted, colored and all.
A first impression: It’s way faster than 2.3, and it looks the database-engine is less heavily accessed, though on a first post, MySQL crashed again – just after the watchdog loop started again, so I had to wait almost 15 minutes…. But after that, the impression was strenghtened.
Time for exploring the benefits (and drawbacks).