Blogs

Comunity’s Open!

The No-Rights Community is now up and running. Come get your free account and join in the fun. I’m looking forward to posting movie reviews and discussing all sorts of things. Cartoons, comics, bands… you name it. Gonna be a good time 🙂

Reviews of forum packages

I tried a handful of different forums trying to decide on one. Here’s a quick rundown of each

Simple:Press Forum

This plugin for WordPress is very easy to install, integrates into pre-existing themes fairly well, and users don’t have to register for a different system in order to log in. In the end I decided a standalone forum would probably be less of a resources strain.

phpBB

Arguably the most popular free option out there, it’s got a lot of features and my webhost offers it as a one-click install. Of course, when something’s popular it’s also more likely to come under attack. phpBB3 is a step up in security and anti-spam, but I was looking for something a little more lightweight. Also I have a bit of a philosophical difference of opinion when it comes to displaying posts. phpBB likes to organize everything into different forums you then have to click and open to look through. I can understand this if there’s a large user base with plenty of discussion categories established. Personally I’d rather see that people are actually posting discussions right up front.

BBPress

Automattic, the folks behind WordPress, have their own forum solution. It integrates with WP and puts posts above the categories in it’s display. It’s fairly lightweight, requiring plugins to provide extended features. The problem I had was with compatibility. If I want to integrate WP 2.8 with BBPress I need to use version 1.0 that recently had it’s official release. And with that I find plugins don’t work. I understand this is mostly a transitional thing and from what I’ve seen BBPress gets the short end of the stick whenever WP decides to change something in an upgrade. I could try the .9 series as a standalone but I’d really rather give 1.0 a couple months to a year to sort itself out and see how it shines. In the mean time I went with another option. (I liken this to my recent switch from ComicPress to Webcomic & Inkblot. Both are great solutions and whichever one fits my needs best at the time is the one I’m going to use.)

Vanilla

Lussumo have developed this simple forum framework that functions similarly to BBPress and I must say I was on the fence about which one I wanted to use for awhile. I figure WordPress integration isn’t the biggest deal-breaker as the community itself can sport the features it needs with plugins. (And Vanilla has some plugins going back to 2006 that still function fine.) Vanilla2 is still in heavy beta but 1.1.8 is so solid I’ll use it for the time being.

What’s the status of things right now? Well, if you’ve been watching this page lately you’ve noticed I’m tinkering with the theme. An issue that’s bugged me for awhile is needing multiple installs of WordPress to power my comic sites as well as this blog and the Lil’ Reaper Books page. It’s inefficient from a resources standpoint and annoying from a practical perspective. If I’m logging into different accounts for different things nothing gets done. It needs to be simpler.

Now I’ve used ComicPress with the ComicPress Manager Plugin for some time, which is pretty awesome, but it doesn’t really support multiple comics yet. Enter Webcomic and Inkblot. They take the angle of using the plugin to power the comic so you can drop tags to display everything into any WP template. I like this approach. I’m still resolving issues with pointing the comics’ domains at the proper indexes, something I’m trying to work out between this WP Subdomain Plugin and the theme itself. If I can’t get it working I’ll just redirect to the page standing in for the index.

When I first started posting comics in 2002 it was on Keenspace, (Yes, back when it was still officially Keenspace) and things ran smoothly for about 3 days until I deleted some all-important file. This was way back before the server melt down and nobody could be bothered to fix my problem or show me how to fix it at the time. Striking out on my own I moved to a dinky free website and updated using AOLpress and Blogger. Eventually I registered Towniescomics.com and decided at some point to move the archives to a php script solution to make it easier to change things on every strip’s page. That’s when I started using the Walrus script. Some time later I learned my way around MySQL, too, and moved to ATP Autosite. That got a little long in the tooth when web standards started getting brandied about. If you’ve tried looking for webcomic update scripts you know they have a habit of going undeveloped as time rolls on. Tyler Martin did us all a favor by rolling out the previously mentioned CP. That brings us right around to today.

WC & IB sort of remind me of the earlier days, back before WP got involved. The code’s relatively simple and easy to customize. I might go back and forth between it and CP as time moves on. They’re both good systems being developed concurrently. A little competition is good for developers. It keeps them on their toes. And at the moment it’s not too complicated to switch between the two, either. Right now I’m just focused on which will get my archives looking like I want with the least amount of fuss. After that I should probably decide on a shopping cart system to replace the LRB site. Then I need to customize the theme on the new Community. This is important because I want it to just feel like another part of the site instead of just a forum slapped on. I was trying to integrate it with comment posting member registration but that’s going to be more trouble than it’s worth. I’d really rather just have you sign up and log in for one thing so I’m gonna see what I can do about tying it into the comment system another way. I just really need to get all this technology out of the way and get back to creating comics and posting about them, all the other stuff will happen in time.

I updated all my sites to WordPress 2.8 once the built in updater recognized it was available. Things went smoothly on all of them except for this one. (Which I expected since I was running a lot of plugins in my attempts to fold all the other sites under this install.) I removed everything from the plugins directory besides what comes standard and that got rid of the error message. It also got rid of everything else. So I just decided to do an entirely fresh install since I’d been meaning to for some time, anyway. I’m pretty much back to where I was before the update, excluding the new features of the latest version, except one of my plugins needs to be fixed before I can use it.

I’m hoping I can get a replacement for whichever one is causing the problem or it gets upgraded soon. I’m not going to consider any one plugin critical to the changes I’m making because then I’d be in pretty big trouble every time there’s a new version out. However I’d rather rely on activating a few instead of having to dig into code and add functionality that way, both because that’s more complicated to do and it’s a lot easier to break with every upgrade.

On the top of my To Do list right now is decide on a unified theme, at least something of a unified header design so the pages and different sections look the same. I tried incorporating the blog theme on all the sites but really dropped the ball when it came to styling the ComicPress theme to look like the others. It didn’t help that I was unfamiliar with the new CP coding and that the headers are very different by design. I really need to go in and tweak the default to something I’m comfortable with, something I can then use on all the other sections of the site as I activate them.