More blog issues
I found that though the normal user access to blogs was not really impacted by the transfer for MySQL 5.1 (except that it seems to be significantly faster), some admin panels didn’t work properly at all. To be honest: couldn’t be accessed at all, because things seemed to be broken somehwhere in the MySQL database access. So I had to configure these blogs to use the new 5.1 database. This applied to the SYSMGR blog, the Bootcamp2008 blog and my Trips, Tracks and Travels. Remarkably, the testblogs that are still available for older WordPress versions) did work nicely, even in the Admin panels.
So I am moving all blogs to MySQL 5.1, and put versiom 4.1 to rest. It may cause some blogs inaccessable for some time.
There was, for some reason, a problem with the Bootcamp 2008 blog: it failed to load, the admin panel didn’t show up or it was the WP25 admin page (the BC2008 logical refers to the BC2008 environment first, and to the WP25 environment after that). The logicals were fully correct, the same structure and definition is used for both the Bootcamp 2007 and Trips,Tracks and Travels blog, and these were all fine, both the blog as the admin panels.
Restarting the webserver solved the problem – but I had to define the logicals /EXEC first 😉
Anyway, this problem is solved now. There must have been a glitch within the server cache, perhaps?
WordPress 2.6
is out for a week now, I got it already and will test it this week. It may cause some themes to be changed because the current skin is not compatible with this version.
I installed it, and it didn’t work out-of-the-box as did the previous versions: a number of files have a dot in the name and this is replaced by underscore when unzipping the package:
class.wp-dependencies.php
class.wp-scripts.php
class.wp-styles.php
functions.wp-scripts.php
functions.wp-styles.php
The PHP code however checks for the name containing the dot;
Luckily, it’s just one file (script-loader.php) where these five are loaded. I renmaned the files and it worked. Well, almost. The database has to be created, after that tables were created but accessing the testblog (after I added it into the WASD configuration, of course) failed. That is: the main page is shown but the stylesheets are missing. Login and admin however cannot be accessed. Cause: When the tables are created, the default protocol for the blog is http, where I expect it to be https since the testblog is on the operator web – which is, for obvious reasons, secured.
Changing these two entries (site URL and home) usiing direct access to the database to state https solved this. It works fine. So now it’s a matter testing it all.
LogScan problem
I updated the logscan last weekend: the list of “allowed locations” needed an update because there are some new directories, and some old ones. But due to a mistake: the last entry of one of the lists ended in “|”, there was hardly any invalid location, just the commands that I think inappropiate on the site. This error has been corrected now and the list rerun.
VAMP (the Vms/Apache/Mysql/PHP site) is found to be offline for quiet a while now, so I disabled access in the OpenVMS blogroll for the moment.