Also, have spent entire day reading up on and attempting to implement various Wordpress security measures. Have developed buggy eyes and raging headache as a result. Ow.
The heart of the problem is that I can't upgrade to WP 2.9.x until we upgrade to PHP5, and as the WAMP I'm using is no longer in development, I'm going to have to start all over again and either find another WAMP or suck it up and install Apache, PHP, and MySQL myself -- my attempt to upgrade PHP this weekend so I could upgrade the blogs ended in my breaking the server, so I had to roll back to the status quo. And with switching to a new WAMP or installing the stuff myself, I don't think I can keep the current WPMU install, because it's stuck in Apache2Triad. So I'd have to ask the bloggers to set their themes up all over again once I imported their content and it's hard enough already just trying to get them to switch on a simple stats plugin (o joy to whoever implemented the "activate plugin sitewide" thinger! except when I still have to configure it individually for each blog!).
So basically today was an attempt to shore up as much security as possible to hold it together until WP3.0 comes out, whereupon I'll take the blogs down for a couple of days and install everything new and shiny, including WP3.0, and give the bloggers brand new shiny custom themes that fit the school's Web standards instead of making them re-do their old ones. :D I get to spend the time between now and then making said new shiny custom themes (anything major I have to watch out for that'll be different in 3.0? :D).
Toby pointed out a hole in Apache to me that I could fix (yay!) and I'm going to check tomorrow and see if there's any known holes in the PHP and MySQL versions I've got, and shore them up as much as possible. And make sure I've got regular WP backups Just In Case.
The wp_nav_menu() tag is the big new thing. It replaces wp_list_pages() or whatever else themes have been using to create nav menus. Not much else new on the theme front... there's now a comment_form() tag you can use to print a standardized comment form, but that's the only other thing that comes to mind.
I am trying to keep http://codex.wordpress.org/Version_3.0 updated with the big things, but my focus is elsewhere and the developers mostly haven't touched that page yet.
... hang on, I just reread the first part. Why do you need PHP5? WP doesn't require it; it's steadfastly stuck on 4.3-something. (I'm quite sure of this, having listened in on more than one contentious discussion in the developer chats.)
If it wants the higher version, I may still be stuck in the same place, but if it's just a library, that might be do-able.
I am so glad that the school is buying some sort of wiki software so I can move the ref wiki over there and then NOT SUPPORT IT. The blogs are enough for me!
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
no subject
no subject
no subject
no subject
The heart of the problem is that I can't upgrade to WP 2.9.x until we upgrade to PHP5, and as the WAMP I'm using is no longer in development, I'm going to have to start all over again and either find another WAMP or suck it up and install Apache, PHP, and MySQL myself -- my attempt to upgrade PHP this weekend so I could upgrade the blogs ended in my breaking the server, so I had to roll back to the status quo. And with switching to a new WAMP or installing the stuff myself, I don't think I can keep the current WPMU install, because it's stuck in Apache2Triad. So I'd have to ask the bloggers to set their themes up all over again once I imported their content and it's hard enough already just trying to get them to switch on a simple stats plugin (o joy to whoever implemented the "activate plugin sitewide" thinger! except when I still have to configure it individually for each blog!).
So basically today was an attempt to shore up as much security as possible to hold it together until WP3.0 comes out, whereupon I'll take the blogs down for a couple of days and install everything new and shiny, including WP3.0, and give the bloggers brand new shiny custom themes that fit the school's Web standards instead of making them re-do their old ones. :D I get to spend the time between now and then making said new shiny custom themes (anything major I have to watch out for that'll be different in 3.0? :D).
Toby pointed out a hole in Apache to me that I could fix (yay!) and I'm going to check tomorrow and see if there's any known holes in the PHP and MySQL versions I've got, and shore them up as much as possible. And make sure I've got regular WP backups Just In Case.
no subject
I am trying to keep http://codex.wordpress.org/Version_3.0 updated with the big things, but my focus is elsewhere and the developers mostly haven't touched that page yet.
no subject
no subject
no subject
I'll take a good hard look at that message again tomorrow.
ETA: I should also check my PHP version - I might have mistaken the message for telling me to go to 5 when it needed me to go to 4.3 or something.
no subject
no subject
I am so glad that the school is buying some sort of wiki software so I can move the ref wiki over there and then NOT SUPPORT IT. The blogs are enough for me!
no subject