Working on WordPress upgrade
At this moment, all blogs are still on 2.6.5. The reason is simple> since WP 2.8 there have been internal changes that cause a loop in displaying the main pages.
Given the unexpected comment a few days ago, I think it better to get on to the latest version (l3.4.2) but I don’t want to interfere with this old version hat still works fine. So first, I created a new “blog” but still in 2.6.5: copied wp-config.php of an obsoleted blog and changed what’s needed, set up the system logicals to access it, and added the configuration in WASD_CONFIG_MAP. It created the blog and under 2.6.5, it all worked (including the hiccup in the admin pages).
Next, I installed WP 3.4.2, needed a bit of tweaking since unzip still fails to create a file including a dot in the name – not a big deal, there only 5 of them 🙂 – and set the logical for this test-blog to this version.
And now it didn’t work anymoe, as I was expecting: WASD runs into a loop because the mapping goes bazurk:
12:12:28.49 SERVICE 1659 0001 CONNECT VIRTUAL www.grootersnet.nl:80|
|12:12:28.49 REQUEST 4870 0001 REQUEST GET /wptest/INDEX.PHP/|
|12:12:28.49 MAPURL 1148 0001 MAPPING PATH /wptest/INDEX.PHP/|
...
Redirect: /wptest/INDEX.PHP//index.php?
|12:12:28.50 REQUEST 1816 0001 REQUEST REDIRECT /wptest/INDEX.PHP//index.php?|
|12:12:28.50 SERVICE 1659 0001 CONNECT VIRTUAL www.grootersnet.nl:80|
|12:12:28.50 REQUEST 4870 0001 REQUEST GET /wptest/INDEX.PHP//index.php|
|12:12:28.50 MAPURL 1148 0001 MAPPING PATH /wptest/INDEX.PHP//index.php|
...
Redirect: /wptest/INDEX.PHP//index.php/index.php?
|12:12:28.50 REQUEST 1816 0001 REQUEST REDIRECT /wptest/INDEX.PHP//index.php/index.php?|
|12:12:28.50 SERVICE 1659 0001 CONNECT VIRTUAL www.grootersnet.nl:80|
|12:12:28.50 REQUEST 4870 0001 REQUEST GET /wptest/INDEX.PHP//index.php/index.php|
|12:12:28.50 MAPURL 1148 0001 MAPPING PATH /wptest/INDEX.PHP//index.php/index.php|
It keeps adding /index.php until WASD finally concludes there is a loop somewehere….
So I removed all redirects in the configuration, but at that point, it doesn’t work either. It fails from the start:
|12:25:21.21 SERVICE 1659 0003 CONNECT VIRTUAL www.grootersnet.nl:80|
|12:25:21.22 REQUEST 4870 0003 REQUEST GET /wptest/INDEX.PHP/|
|12:25:21.22 MAPURL 1148 0003 MAPPING PATH /wptest/INDEX.PHP/|
even if I don’t specify anything but the minimal URL; index.Php should be added because that’s specified in WASD_CONFIG_GLOBAL as one of the starting documents. But it seems to be translated into a directory. And in that case, a 404 error (document not found) is to be expected, as is shown in WATCH output:
|12:25:21.23 ERROR 1539 0003 RESPONSE REQUEST:5965 (basic-only) 404(000) %X0001C04A (%RMS-E-DNF, directory not found) "Directory not found" "/wptest/INDEX.PHP/" "(no information)"|
|12:25:21.23 REQUEST 1099 0003 REQUEST STATUS 404 (Not Found) rx:648 tx:870 bytes 0.014648 seconds 103,635 B/s|
Being out of options for the moment, I asked on the WASD mailing list; I know some use WP as well and they have it running.
Of course, this test=blog has been disabled so you don’t need to try and access it :).