I went through the list of blogs here and deleted inactive ones. I was shocked at the amount of spammed comments on some of those blogs!
Blog owners here have been emailed too, so if you get an email from me requesting you click on a link on this site to validate your email, it’s in your interest to do so!
For some reason, Yahoo mail prints “\n” directly so urls are a bit fscked. Just click on them anyway as the info’ll get recorded in any case.
I made 2 minor changes to the blogroll plugin.
Moderation of comments is now enabled on every blog on this server!
When someone posts a comment, you’ll receive the usual email with the comment, but at the end of the email will be a link to the Comment Moderation page for your blog.
From this page you can list:
Comments aren’t really deleted, just not displayed. I may add an option to “really delete” a comment eventually.
I’ve updated the comments on every blog here to “OK” status. This means all current comments will be displayed. You can change that status as you like from the backend.
Please leave a comment here, or mail me if you notice any bugs (There’s bound to be!), or have any feature requests.
Comment posting may break tonight if you post comments on any of the blogs on this site. Please be patient and visit again later!
Thanks to Dougal Campbell for writing a Pirate filter on his site. I copied the code and put it into a Smarty plugin. It’s available here for everyone on blogs.linux.ie to use as follows:
{$the_content} variable in there.pirate function: {pirate content=$the_content}. If you’re using the highlightsearch modifier, then use this code instead: {pirate content=$the_content|highlightsearch}. Oh, of course, it’ll only work today, as it’s Talk Like a Pirate Day!
UF has a special Pirate Talk Day feature today! 🙂
I was drafted in to help on WordPress a long time ago. Unfortunately I haven’t done much work on any OSS projects in a while and it was bothering me.
I did do some useful work though – I found out that the Smarty register_resource construct was buggy when using caching. That rules out using MySQL as a backend to hold templates. (I posted a mail to the Smarty list but nothing came of it. *shrug*)
Finally, after re-installing Linux on my new hard drive last weekend I Smartyised WP! Here’s a WIP snapshot.
What does it do? Well, I wrapped some of the Smarty template API (ie. bloginfo(), etc) in Smarty functions of the same names. I’ve only done enough to get the default template working, as it’s laborious work and I wanted to get something out quickly!
The template is split up into 3 parts: top.tpl, post.tpl and end.tpl. They live in users/main/templates/ and can be edited there with a text editor. The online editor from b2++ will make it’s way there eventually probably.
Before trying this, please be sure to backup your WP installation. The files in the tarball don’t conflict with the files in CVS but I can’t guarantee that this won’t delete all your WP install files if you’re not careful!
Download the WP – Smarty mod. (40Kb)
First of all the trivial stuff. I just noticed that my referer log was spammed by some domain resellers. The script I based my referer code on already had “checking” in there to make sure the referer actually listed your url on it, but I didn’t enable it. That’ll be enabled and added to b2options shortly. I also added a “delete” function to b2referers so you can delete referer records to get rid of spammers.
I just noticed that Google, Ask Jeeves and other search engines have visited in the past few days. I should really ignore those hits in the referer script.
This morning I received an email from Matthew Mullenweg asking me to join the WordPress effort. It took me all of 5 seconds to agree that b2 would be best served by a merger of b2++ and WordPress.
I’m off to Chicago on Sunday, life’s hectic here as I tie up loose ends. It’ll probably take a few weeks before there’s anything useable from this merger, but I’m excited at the future possibilities of b2!
I added a discussion forum and documentation site for b2++. Both are quite empty right now, but you can post to the forum if you have any queries or comments about b2++, and if you’d like to contribute to the documentation feel free to email me and I’ll setup an account for you to edit pages in the Wiki.
The documentation is handled by WakkaWiki but I’ve limited editing by requiring a username/password.
The forum is running a stock version of phpBB.
b2++ 0.7 is out. Read the announcement on the b2 forums.
I’ve also installed a wiki and phpBB2 on this site. If anyone would like to contribute to the documentation effort, or can test/verify a phpBB2 install I’d appreciate it. That said, installing it was quite easy and may influence the install of b2++ in the future!
Go download it now!
Michel’s back, and announced details about the future of b2.
WordPress is going to be the next version of b2 and is developed by Mike Little and Matt Mullenweg. I’ve exchanged brief emails with both on different matters and hope to continue exchanging ideas and code as we’re working on a similar codebase. Tim has more on the announcement too.
With b2++ and WordPress around, the future of b2 looks good! 🙂
On another note, there’s a security hole in the blog import tools shipped with b2. I bundled these scripts with b2++. The easiest way of fixing that is by deleting gm-2-b2.php and blogger-2-b2.php.