The spammers were busy last night and this morning! I received some 20 comment spams and notifications are still coming in. So, now when you go into the comment moderation page, when you “delete” comments, they actually are deleted from the database now.
To delete old comment spams simply open up the “Deleted Comments” page and hit “Submit All”.
So, to the spammers.. don’t bother. You’re not going to get through here!
Later still.. Until the storm of comment spam drops off, notification emails are disabled. Check the Comment Moderation link during the day if you see comment number increase during the day!
It looks like iTools 7 for Mac OS X & Mac OS X Server is using or at least shipping b2++ as one of their “new extentsions to make websites easier”. It sits alongside such well-known stalwarts as Gallery and phpBB2 and PHP-Nuke! (Thanks Mark for the link!)
Blog owners on this site will notice and hopefully appreciate a minor change to the referer listing. Instead of printing the complete url to Google requests, Individual keywords are now displayed!
you’ll now see
Google: font too small thunderbird linux
which I think you’ll agree is much nicer!
Does anyone understand the language used in this blog entry about b2++?
Finally, a new release of b2++! This is a minor release, putting the features we’ve been using here on blogs.linux.ie into a release for wider distribution!
New in this release:
- Comment Moderation: Every comment, pingback and trackback must now be validated before they’re displayed. Bye bye comment spam!
- Referer Blacklisting: You can add any referer in your backend to a blacklist. The next time someone visits from that site the referer doesn’t show up on your site.
- Minor bugs with the smilies in b2edit.
- Added Pirate Speak plugin by Dougal Campbell.
If you’re upgrading from b2++ 0.7, then download the upgrade package and copy the src/ directory into your b2++ install and run the upgrade script. That’ll update your database tables properly.
New users should of course download the full b2++ package.
New users: b2++ 0.8 tar.gz | zip
Existing users: b2++ 0.7 -> 0.8 upgrade tar.gz | zip
I’ve just added a blacklist to the b2++ referer system.
It’s fairly simple. If you see an evil referer appearing on your page simply go to the referer admin page, select the checkbox next to that URl and hit the “Add To Blacklist” button.
I’ve briefly tested it and it seems to work fine, but if you encounter any problems please leave a comment here or email me at the usual address.
Now to blacklist that medication site that linked to me…
I’ve ported the Smarty template editor and theme chooser from here to WordPress. It’s available to download as a tarball.
Warning! This is highly experimental code. It will nuke your current WP installation so install it on a testing server. It’s not ready for public consumption, it’ll give you food poisoning, it’ll make bad things happen, it’ll cause massive problems for the .. oh, just try it on a test server, don’t use it on a production server at all.
Here’s the mail I sent to wp-dev last night:
What this adds:
1. Smarty template aware editor. This editor makes automatic backups of your template. To restore a previously edited template just click 1-5 next to the template name and save that template again. It’s a FIFO queue..
2. Template picker/chooser. The default WP template is there as well as “Blue Dash” that I did for b2++. Click on the “Use this theme” link to use the selected theme.
3. Smarty is included, so you don’t need to download that if you haven’t got it.
Anyway, here’s what you do with this lot:
1. Don’t install this over your current live WP installation as it’s only for testing!
2. Download the tarball. It creates a wp directory so move stuff around if you have to. Files should be overwritten, so backup, backup, backup!
3. In the wp-blogs/main directory you’ll want to chmod 777 the templates_c smartycache templates directories and chmod 666 templates/*
Fire up your browser and point it at your WP install!
chmod 777 templates_c smartycache templates
chmod 666 templates/*
Well, WordPress 1.0 has been released! There are a few comments on the dev blog announcement to look over as well as the support forums to post questions. I’ll be updating my CVS work area in a few minutes. 🙂
Here’s something I sent to the WordPress dev list this morning…
Anyway, this morning after a hectic night taking some 250 photos of a friend’s band at a Christmas party it I was wondering how best to blog the best of them. Here’s what I thought of:
The blog entry will have a number of thumbnails (could be automatically created when the large size images are uploaded), and a space underneath, perhaps filled with the first image.
This weblog was out of service for a while, but I fixed the problem – the site error.log gave unusual errors about reading xml data. The only place I use xml is in reading data from blo.gs for my blogroll.
Unfortunately their site is down at the moment and their xml feeds are unavailable.
I never checked if the “fopen” to connect to their server succeeded, so when the routine tried to read data in it barfed. Here’s a quick fix to function.blogroll.php if you have the same problem:
if( $blogroll_remote_fp == false )