wordpress

You are currently browsing the archive for the wordpress category.

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: , , , ,