oberlincilc

Unfortunately, if the student blogs are all standalone installations of WordPress, the class blogs plugin will not work. However, if you run a single multi-user installation of WordPress, each student will be able to have their own blog, you’ll still be able to have an instructor’s blog, and you’ll be able to benefit from the class blogging plugin.

Sadly, I don’t have anything new to offer besides the suggestions in this thread, since I still can’t replicate this error on my setup, and don’t have much free time to do any further debugging.

Ludology-

The posts should be appearing on the front page by default. However, since they’re not doing so on your install, try the following things:

• Create posts as multiple different test users and see if any of their posts show up on the front page.
• On the Student Data Options Class Blogs admin page, ensure that the Aggregation Enabled radio button is set to Enabled. Also try clicking the Refresh Student Data button.
• On the Student post OptionsClass Blogs admin page, ensure that Show Student Posts on Root Blog is checked.

Hopefully one of those things should work. If not, I’ll have to think a bit for other things to try.

David-

The ability to change the date on which a post was made is a core part of WordPress, so there’s no functionality to change that in the class blogs plugin. I could add it in at some point, but I have no immediate plans to do so.

The plugin is actually able to handle both situations. It will work if WordPress is running in a standard mode where there is only one blog but multiple student user accounts with authoring privileges on that blog, and it will also work if each student has their own blog in a multi-site network setup.

Thanks for your system information and the debugging update. When I get some free time, I’ll try replicating a setup with the plugins that you have installed (on multisite and standard installations) to see if that has something to do with it. Based on the outcome of the upgrade of your test system to multisite, perhaps there will be other courses of action that make sense.

I’m sorry that the plugin doesn’t seem to be working. Clearly there’s a bug that I need to fix if you’re having the exact same error as another user. The problem is still that I cannot seem to replicate this on either my development machine or our production server. In an effort to change this, though, I’ve got a few questions.

What operating system are you running? What other plugins are you running? Have you tried creating a clean installation of WordPress and only installing the class blogging plugin? Have you tried creating a new, non-multisite installation of WordPress and installing the plugin? If you’re trying out the plugin on a server, have you tried it out on a local, development machine and experienced the same error?

Hopefully the answer to one of the questions will help me figure out what’s going on. If it doesn’t, we could move this conversation to email and try some much more specific fixes that involve editing the plugin’s source.

Sorry that the plugin is playing hard-to-get. I’m unable to replicate this error on my end, so I don’t have much to offer besides questions.

First of all, what operating system are you running?

Second, since you’re talking about network activation, I assume you’re running WordPress in multisite mode. Have you tried creating a new, test instance of WordPress that’s not running in multisite mode and installing the plugin on that? If so, did you get the same error?

I wish I had more to offer, but that’s all I’ve got for the moment. I’ll keep playing around to see if I can replicate the error, and roll out a fix if I can.

The code that rCampbell is posted is not too far off, as it no longer gives the plugin the chance to look for an array key in something that’s not an array. However, it also bypasses the check for the page_id variable entirely, which will make the plugin perform in unexpected ways.

I just posted version 0.5.1 of the plugin, though, and that contains modified code that should prevent this error message from coming up again. If you have a chance, try out the new version and let me know if that solves the problem. If not, I’ll have another go at fixing this.

I think it comes down to an issue of focus. BuddyPress is a super-awesome plugin with a sweeping vision of turning an instance of WordPress into a self-contained social network, with a lot of focus on inter-user messaging, groups, and other things that one would expect of a social network, allowing for large amounts of interaction to happen on the WordPress instance.

The class blogging plugin, in contrast, has a very narrow focus, being something that allows a professor to make WordPress a bit easier to use when blogging as a class. Instead of overhauling WordPress, it just adds some nice features. It doesn’t add any new ways for users to communicate with each other, because we make the assumption that most users will be students and will be interacting with each other in the classroom. This, I suppose, brings up the other big difference between BuddyPress and the class-blogging plugin. BuddyPress is extremely configurable, and can be used to run all sorts of sites. Our plugin basically lets you make a blog to support a class, and not much more beyond that. If that’s what you want to do, though, the class-blogging plugin should prove to be quite useful.

Hopefully that helps. If not, I’d be happy to answer any follow-up questions that you have.

Sorry for the slow response. I just posted version 0.5.1, which includes a fix for the bug that’s causing the error message that you’re seeing. If you get a chance to try it out, let me know if it fixes your problem. If you’d like to wait two weeks before letting me know in order to serve up some karmic justice, I won’t hold it against you.