In the past, the CLUG wiki has had minimal wikispam, because we thought up some clever regexes, that blocked spammers from editing. However spammers would still sign up, before they tried to edit. This has left the wiki with over a thousand bogous users. Not that that is a problem in itself, but it becomes a bore when you want to guess somebody’s wikiname to give them “Bureaucrat” status for example.
So jerith talked himself into coding up a quick SQL query to find all these bogus users, and a python script to remove them. Any history they’ve had has been assigned to the “Spammer” user, and they have been wiped from the wiki. If, in our zealousness, we’ve deleted any legitimate users who’ve simply never edited the wiki, we apologise. Maybe if you contribute something, it won’t happen again… :-)
This is my script for migrating from Wordpress to Drupal. I know that there is already a migration script out there, but I still wrote my own for a few reasons:
So here it is.
Limitations and bugs:
wp-). This is messy, but while Drupal’s multi-database system is a cool and would be perfect, it’s unworkable when you are debugging. Errors seem to be hooked in drupal, and if you have a broken SQL query (for example) the error handling code hooks Drupal themes, which aren’t findable in the alternate-db world you are visiting.
As should be obvious to non-feed readers, I’ve migrated my blog to Drupal. This fits in with my greater plan of organising myself and moving into digs this holiday. Drupal is an awesome CMS - or maybe a better description is “the only decent CMS”. I’ve set up and maintained a few drupal sites, and have been very impressed with it.
I’ve yet to migrate all my previous blog-posts across, but by the time you see this post, that’ll be done. Vhata has walked this road before me (albeit from Serendipity), and I intent do follow his advice.
In the past, I mantained my Wordpress blog as an SVN install. This allowed me to install plugins with
svn:externals, which made upgrades a doddle. Drupal uses CVS, so this approach wasn’t an option. After months of procrastination, I investigated config-manager. With it, I built a recipe for downloading drupal and all the modules I use with it. Then I committed this as a bzr tree, so that I could base all my sites on a common base. To install a module, I
bzr mv modules/foo drupal/sites/all/modules/.
Now to update all my drupal sites, I update my
config-manager recipe, and build a new master tree. Commit it to the repo, and push to launchpad. And then
bzr merge in all the sites. It’s pretty quick and painless.
For anyone who’s interested, the modules I’m using are:
So far I’ve had to write a drupal module to support amatomu, and it was a bliss. Drupal’s API and code is some of the neatest PHP I’ve ever had to work with.
I think I’ll be happy here :-)
Todo list (Things amatomu does that I don’t care for, and thus haven’t coded):
Available from Drupal.org. Releases for Drupal 5 and 6 are available.
You know what happens with old phones, right?
The battery slowly dies, and it needs charging all the time.
So we modded this old brick by attaching the charger to the battery, increasing the phone’s usability by 1000%.
Now you never need to worry about the battery running out, just plug it in. AND because it has a 3-pin plug, you never need an adapter.
It is was in use everyday by Nicholas Abbot for a couple of years (although he had to enlarge his trouser pockets <grin>).
The ultimate mod!