wordpress

You are currently browsing the archive for the wordpress category.

WPMu was just updated to a long awaited Version 2.7.1 which has, in turn, triggered events in the BuddyPress realm. The new WPMu version offers a number of important improvements making it a significant improvement. As a consequence, BuddyPress has finally been able to release Version 1.o.

Upgrading from WPMu 2.7 to 2.7.1 was a cinch. First make up your files and database , then simply click the upgrade notification and the new files load. Upon upgrading , the first thing you will notice that the horizontal on the top of the admin page has disappeared. The controversial feature is now an optional plugin.

This upgrade goes yet further in polishing and un-cluttering the administrative interface. Plugin management is much improved and can be handled through the backend rather than the prior ftp for mu plugins and the backend for the wp plugins.

I’m going to start from scratch on my WPMu/BuddyPress installation soon and look forward to renewing my BuddyPress and Elgg comparisons.

Tags: , , , ,

I recently came across CommentPress. It’s a WordPress plugin that allows readers to comment on a post paragraph by paragraph. CommentPress looks like a very promising collaboration tool. CommentPress is on the cusp of a major upgrade from version 1.4.1 to 2.0. We will look at features in the current version, and preview Version 2.0.

Currently, CommentPress is a WP theme. Install it and activate it.

cp_1

The resultant main page includes a table of contents on the left side, a “page” that you can customize in the center, and some widgets on the right. The meat of this comes when you clink a link to one of the posts.

cp_2

Each paragraph has a “speech bubble” to the right of it. Click on that and you can view all the other comments on that paragraph. Comments can even be threaded. Whether or not there are comments already, there is a text field for entering comments.

As it stands, CommentPress works well. Yet the developers plan on giving it even greater flexibility with version 2.0 due out in a couple weeks. I had trouble with the beta on my server, so I can only write about what I have seen and read on their site.

Rather than just a theme, the new version will include 3 plugins and a theme that can work independently so you only use the components you need. You will be able to use it with most WordPress themes. The comment box can be dragged and dropped to any location on the page. There are also enhancements that improve CommentPress’s ability to work with changed text in the posts. I also understand that it will be more flexible in working with other widgets and plugins.

cp_3

CommentPress’s potential in education and in other areas is great. The ability to annotate and critique text paragraph by paragraph make it much easier to focus a response to a given segment of text. It would work well for peer editing of student writing. Teachers could post a segment of text for students to read allowing them to respond to the text and other comments. I have installed CommentPress to facilitate discussion of our school’s web publishing policy.

I look forward to working with a new version of CommentPress, but I wouldn’t hesitate to recommend it as it is today. As a bonus, the current version works with WPMU, and I hope the newer version will as well.

Tags: , , , ,

As I ramp up our school’s WPMU blog platform, I look forward to rolling out the new 2.7 interface. I have updated and tested my favorite plugins. DSader’s More Privacy Options, and Peter’s Collaborative Email still work. To make things even better I found a pair of plugins that will make our configuration more secure and give greater control over user privileges.

First off, there was a security hole wherein students could view pending comments that have not been approved by an administrator. Dean Matteson discovered this flaw when he realized that student comments were appearing without his having reviewed them and wrote about in his blog. He came up with a plugin that blocks access to the comments page.

Looking for new plugins for our school site I found the WPMU Menus plugin that not only solves this problem, but it allows you to enable or disable not only comments, but almost every other function in the dashboard interface. Site Admin Options reveals new choices.

wpmu_menu

The screen shot encompasses only half the options available. Beyond security, this allows administrators to greatly simplify the back end user interface making it easier for younger students to navigate.

wpmu_menu2

This takes care of the comments security issue. I tested it further by appending edit-comments.php to the blog backend urls. I was still unable to access the comments page and it redirected me to the profile page.

The next plugin of particular interest is Role Manager. Role Manager is not a WPMU plugin. It must be enabled and configured on each individual blog. Role Manager allows you to change the permissions on any existing role or group of users. It also allows you to create new roles as well. Go to Users–>Roles.

roles1

While logged in as admin, you can also configure the permissions of an individual user by accessing their profile.

roles2

Of course, if you give a user the permissions to access a feature, you also need to enable access in the Menus.

I look forward to relaunching our school blogging platform this March with a fresh new back-end interface, greater security, and a simplified dashboard for our students. If anyone has any input regarding use of WPMU for the K12 setting, I’d love to hear from you!

Tags: , , , , , , ,

WordPressMu 2.7 was released a few days ago. I have been using the beta version on my BuddyPress test installation and our school’s blogging platform. At school the updates from 2.6 to 2.7b to 2.7 went without a hitch by means of ftp. On the BuddyPress site, the svn switch from trunk to tag 2.7 was a breeze.

I have been using WPMU since December 2007 for our school’s blogs starting with version 1.3. In the space of 13 months, there have been ten versions of WPMU, each representing significant improvements.

Version 1.5.1 brought a badly needed overhaul to the administrative interface and each incarnation including 2.6.x and 2.7 have built upon these improvements. To contrast the differences take a look at the following screenshots. The first one is an administrative view of the blogs page in version 2.3:

Credit Jim Groom

Credit Jim Groom

In version 1.3 all administrative options are under the site admin tab. Most weren’t as cluttered as Jim’s installation, but it gives you an idea. In stark contrast, here is the blog view in version 2.7:

wpmuadminblog

The new version looks strikingly better, but it also adds much to the navigation. The left side navigation. Clicking on a menu item brings up any submenu options. The Top menu bar were moved above the blog header and integrates viper007bond’s WordPress Admin bar. The bar can also be configured to appear on nonadministrative site pages once a user is logged in.

I look forward to customizing WPMU 2.7 for our school blogs. It will also be time to revisit the plugins that will help secure and administer blogs in a K12 setting. I’ll be writing about options soon. Are there any others using or considering use of WPMU for the K12 environment?

Tags: , , , ,

Donncha O Caoimh tweeted:

WPMU 2.7 is just about ready. Unless someone has found a showstopper bug or has a great patch, it’ll be out later tonight

This is great news for all WPMU users as well as those waiting for a release of BuddyPress. Once the current beta is tested with a WPMU 2.7 release, the march toward the release of the second beta, then BuddyPress final. It would seem that the final release of BuddyPress is likely to occur by the Middle of February based upon the old release date and the number of days between the announced delay and the actual release of WPMU 2.7.

Donncha also believes that automatic updates should work in WPMU 2.7 for subsequent versions. This is a great security enhancement and convenieince for WPMU administrators.

The current SVN revision for WPMU is 1644. The includes/version.php still lists the code as 2.7-beta. I look forward to updating my installations this evening.

Tags: ,

BuddyPress developers have postponed release dates for the second beta and the subsequent final release waiting for the launch of WordPressMu 2.7. The second beta was originally scheduled for January 26, while the final was slated for February 9.

WPMU developer Donncha O Caoimh released WPMU 2.7 beta January 22 revision 1627 on the SVN repository. While he reports that there are still plenty of open tickets, I have found 2.7 beta very stable and relatively issue free. I am using this version for my test BuddyPress installation and our school’s WPMU blog site.

WPMU represents a major overhaul of the administrator and user dashboard and backend. Overall, I find the interface increasingly intuitive and easier to use. WPMU certainly has come a long way since I began using it just over a year ago.

I hope for a February release of BuddyPress along with Elgg 1.5. It looks like a big month for free and open source social networking platforms.

Tags: , ,

While comparing software features is important, it is also essential to consider user experience. This post is going to focus on the new user experiences for Elgg and BuddyPress working through first look at the site, the registration process, and the resultant page once one has logged in for the first time. I gave an initial overview of the differences between Elgg and BuddyPress in my previous blog post.

With BuddyPress, a visitor arrives a page that may look like this with a “sign up” link on the upper right hand side of the page.

In Elgg, a first time visitor may encounter a page like the one below. Note that the Elgg landing page has been altered using an index.php override. I feel this is a fair comparison in terms of effort with installation. As you may recall from my previous comparison, the BuddyPress installation required a certain amount of coding, so I thought it would be fair to apply comparable effort to an Elgg installation as a starting point. Note the registration link in the left column.

bpelgg2

Registration

Click on the register button with BuddyPress and you arrive at a page asking you to provide profile information by filling out several fields. The administrator can change or add to these fields making them optional or required. In this installation, I added a “Profession” field. Further discussion of this feature will appear in future posts.

bpelgg3

Next, you are given the option to create a blog or just an account.

bpelgg5

You then are notified to look for an activation email. Once you click on the link in the email, you are given a password.

bpelgg6

Elgg, on the other hand, simply asks for a display name, email address, username, and password.

bpelgg4

Click on Register and you are returned to the landing page with a prompt telling you that you will be getting an confirmation email. Clicking on the link in the mail returns you to the site notifying you of confirmation success. You can then log in.

Logging In

Once logged in, Elgg and BuddyPress deliver you to entirely different pages. BuddyPress brings you to your public Profile page, while Elgg delivers you to your private Dashboard.

Once you log into your new BuddyPress Account, you return to the main page with the options available to a logged in user. Note the gray menu bar on the top of the page that was not visible when not logged in.

bpelgg9

The first time you log into Elgg, you arrive at your dashboard page and prompted to click the edit page link highlighted below. The dashboard is visible only to the account owner.

bpelgg7

Once you click that, you are presented with a set of widgets that allow you to customize your dashboard. Simple darg and drop them into one of the three columns. These widgets can also be configured. On a side note, Elgg’s profile pages function much the same.

bpelgg8

Conclusions

BuddyPress’s and Elgg’s landing pages are strikingly different, especially if Elgg’s index.php file is not customized. No question that BuddyPress’s default theme with the widget customization is more attractive out-of-the-box. That being said, this is not very important as one can install different themes on either platform. Elgg has many free themes available and BuddyPress will have a variety of themes upon release. Discussion of this is really best left to another post.

BuddyPress’s registration page solicits much more information than the bare bones Elgg registration page asking the new user to fill in profile information and to upload an avatar before the registration process is complete. It also allows the administrator to customize the fields in the form. This could cut both ways. Some users might be put off by the steps required to register preferring to enter just enough information to get inside. On the other hand, it would be more likely that users actually provide profile information and an avatar. It requires somewhat more of a commitment to get an account. In the Elgg community site, I have found it irritating that many users have no profile information at all because it is not required. They just leave it all blank.

Elgg, delivers you to a blank dashboard page; whereas, BuddyPress delivers you to the logged in front page. Some have argued that the blank dashboard is confusing and univiting. On the other hand, it does invite immediate action to customize your account with an easy to use widget interface. With BuddyPress, you will need to explre the menu to find more options. Both Elgg and WordPress require a certain amount of exploration once logged in as not everything is immediately obvious.

I will continue to post about the features and user experiences in future posts. Hopefully, these posts will help individuals choose the best platform for their needs. Beyond that, perhaps developers can learn by examining the different interfaces.

Tags: , , ,

There are two major open source social networking platforms that are garnering much attention of late: BuddyPress and Elgg. Elgg 1.0 was released in August 2008. BuddyPress is currently in beta. Regular visitors to this blog have probably read many of my posts on Elgg. Recently, I posted some first impressions of BuddyPress as a user having created an account on BuddyPress’s test site.

I just finished a BuddyPress installation on my server, so I am now able to make more comparisons between the two platforms. The intent of this is not so much to decide which platform is superior, but to discuss the features, interfaces, and administration of each; thus, helping individuals decide which may be best suited for their purposes. Having looked both over, I believe that each may be best suited for different purposes.

Installation

Both Elgg and BuddyPress require the administrator to set up a mySQL database. The packages must be uploaded to a web server, and browser based installers are used to attach the database to the software and create the appropriate config files to make the programs work. They also require Mod Rewrite to be enabled on the server.  Beyond that, there are several differences.

BuddyPress installation is fairly complex. First WordPressMu must be installed which is simply a matter of creating a database, uploading the software, and running the installer. (One caveat: WPMU is much easier to install in the root public_html directory.) The only thing out of the ordinary is the option to use subdomains (blog.mysite.com) 0r subdirectories (mysite.com/blog). The former is generally recommended and requires activating wildcard dns on your server. Next you need to ftp and install the BuddyPress plugins and themes to the appropriate directories.

Finally, one needs to install and integrate bbPress if one wants the forums to function. bbPress must be uploaded and it should share a database with WPMU. It took a lot of back and forth with the admin interfaces and tweaking the bbPress and WPMU config files to make the cookies work.

Elgg installation is very straight forward. The Elgg developers responded to early complaints about difficulties with installation and made it even less particular about server configuration. Create a database, upload the software, run the installer. It doesn’t matter whether it is installed in the root or a subdirectory.

Now this might sound like a slam dunk for Elgg, but the results of installation are not equal. Let’s start by looking at the front page. The resultant buddyPress looks like this:

Click to enlarge

Click to enlarge

BuddyPress presents the admin with a prompt to add widgets to the threee columns on the front page. Click on the add widget link and you arrive at a familiar WordPress Widget interface.

Click to enlarge

Click to enlarge

The front page is easily customized by adding widgets to the three columns and arraying them as desired. Elgg, on the other hand, has a front page that is initially simple and much more difficult to customize.

Click to enlarge

Click to enlarge

Customization of the front page is done using plugins (or hacking the core) which must be hand coded to render the desired results.

Default Features

Another area worth comparing is the default features with a standard installation of each package.

Component Elgg 1.x BuddyPress
Blogs X X
Groups X X
Private Messages X X
Bookmarks X *
Friends X X
Profile X X
Files X
Pages X *
Wire/Messageboard X X
Forums X X

* Features present in Blogs

The chart is really a rather superficial treatment, but serves to demonstrate that the two packages have similar feature sets. In spite of the similar set of tools, these tools are substantially different in many cases. Comparing these individual features will the subject of future blog posts.

Both Elgg and BuddyPress both require hand coding to create a good social networking plaform. BuddyPress currently requires a certain amount of coding in the installation process; whereas, Elgg requires coding to create something other than the spartan default main page. They have similar features, but the implementation is substantially different. Further comparision of components will yield more insight into the differences between the two platforms. In addition, the user and administrative interfaces represent other points of departure. Look for more posts comparing these two platforms in the near future. Feel free to visit my installation and create an account.

Tags: , , , , ,

Matt Leifer commented on my post about the advent of BuddyPress wondering if there was some sort of integration with a wiki and WordPress. His question aroused my curiousity as I use WordPress and MediaWiki. Indeed there is a very interesting WordPress plugin that works MediaWiki.

Append Wiki Page by Enej Bajgoric at the University of British Columbia is a WordPress extension that allows users to actually embed a MediaWiki page within an individual blog post. Install this plugin and a new option appears at the bottom of the edit post page.

wiki-inc

Simply type in the url of the desired wikipage and it appears in the post when you publish it. Here is a screencast illustrating its use. It includes edit links to the wiki, so that a reader could actually move from the blog post to the actual MediaWiki page and edit it if they have those priviledges. I first saw this on Jim Groom’s post/wiki on installing BuddyPress and wondered how he did it.  In a round about way, I found out how.

I like this plugin and it generally works well. I think that it has a great deal of potential in education and documentation. My only problem is that it, for some reason, will not work correctly when I use it with wikis on my server. If I link to any other wiki page, it works fine. I can only assume it is because of some setting on my server. I certainly would like to resolve this (any offers for help gracefully accepted) as the Append Wiki Page plugin is a great tool.

Tags: , ,

In my previous post about Web publishing security, I proposed the following security matrix:

While this is an oversimplification of the options, I think it gives a framework for making decisions on what web publishing software to deploy, when to deploy it as well as how. As an illustration of how this framework can be used and the potential complexity, we will examine the popular multiple blog platform WordPress MU. Another reason is that we have deployed WPMU in the past and there has been some debate about how it should be used if it should be used at all.

Out of the box, WPMU has two options for access to content: Open to the world and open, but blocking search engines and archivers. It has four options for moderation: Unmoderated, Posts only moderated, comments only moderated, and both posts and comments moderated. With WPMU, then, our matrix looks like this:

As one can see, there are already eight potential options in terms of access to publishing and content. While all the content can be accessed by anyone in the world through both choices, blocking search engines and archivers would significantly reduce access unless one has a link, or goes to the site directly.

WPMU has a plugin that I discussed in an earlier post called More Security Options. This plugin offers three more content access options: Community members (all users with accounts on the WPMU installation), Blog (People who are at least subscribers of an individual blog), and Administrators (only the administrators of an individual blog). The security matrix with this plugin appears:

There are now 20 options in terms of publishing and content access! Arguable, there are even more. For example one could choose to allow unmoderated comments, but restrict comments to logged in members of a blog. Clearly there is enough flexibility in WPMU to accommodate a wide range of Web Publishing Policies.

It is up to school tech committees to consider the ramifications of all of these options in terms of security, audience, and ownership and weigh the pros and cons of each before committing to a particular configuration. Teachers can then decide within the constraints of the school web publishing policy which option best suits their class. Publishing student content to the web is not simply as choice of yes or no. There are several shades of gray. These are not the only considerations and options for deploying this software. For further discussion, refer to my other posts about WPMU for more information on managing and securing the software.

Tags: , , , ,