We are pleased to announce the addition of a much-awaited feature to our WordPress site network. As of today groups added to sites can automatically maintain their membership over time. Site administrators will no longer have to go back into WordPress and regularly bulk-add groups to grant access to new group members.
In the WordPress Dashboard
When you add users to a WordPress site by group the new default option is to keep the group in sync:
Adding a new group to a site. Note the new “Keep in Sync” option.
All users currently in the group will be added to the site with the role you specified. Members of the group who already have a role with greater abilities will not have their permissions reduced. Members of the group who already have a role with less abilities will be raised to the role specified for the group.
The groups synced are shown in a list and can be removed if desired.
Over time, as people are added to the group, their roles in the site will be updated whenever they log into WordPress. If a person is removed from a group they will have their role in the site removed when they log into WordPress if their role hasn’t been manually changed to a different level.
More details about group-synchronization are available in the LIS Wiki.
In the Course Hub
In tandem with this new feature in the WordPress dashboard, the Course Hub now automatically adds class-groups to WordPress sites when adding WordPress Resources. When you add a WordPress Resource to the Course Hub the screen now includes an option that lets you specify what role to give students in the WordPress site. (Instructors will always be administrators of the site.)
Choose which role to give students in the WordPress site.
When you save the WordPress Resource in the Course Hub three class-groups (instructors, students, and audits) are added to WordPress site and kept in sync. Instructors no longer need to do the extra step of going to WordPress and adding the class-groups to the site. As well, new students enrolled during the “Add/Drop Period” will automatically have access to the WordPress site when they log in after their enrollment has processed.
The instructors, students, and audits groups are automatically added to WordPress by the Course Hub.
If you delete the WordPress Resource from the Course Hub the users and class-groups it added will be removed from the WordPress site, however the site itself will not be deleted automatically.
In February 2012 we started noticing a large influx of new comment-spam coming into our sites.middlebury.edu WordPress system that the built-in anti-spam plugins weren’t able to handle. To combat this annoying plague we created a new plugin that instantly killed any comments trying to submit an “author URL” along with the “author name” and “comment text” now that the “author URL” field is hidden.
In the year and a half since this plugin has been in place across our blog network it has blocked an average of 40,000 spam comments every month.
We have exciting news to report from Portland: Drupal 8 looks very interesting. Many of the features of the new version have been agreed on at this point and they are expected to freeze the code in July, spending the rest of the year fixing bugs and polishing it so that a stable version of the application can be released in 2014. This is discussed in the Keynote from Dries, the creator of Drupal.
Some of the new features of Drupal 8 that will be very helpful to our site editors include:
Inline editing. Click an edit link next to the content you want to edit and change it without leaving the page.
True live preview of your edits in the site.
One-step image uploading and embedding.
These new features were discussed further in a session on the new WYSIWYG editor integration for Drupal 8. That will be the first version of Drupal to come with a WYSIWYG editor in the core distribution. They have chosen to go with CKEditor (we use TinyMCE right now) because of its support for inline editing. The tight integration between the application and the editor will make things like custom button dialogs much easier for us to add, which will come in handy for integration with on-campus platforms like MiddMedia.
Drupal 8 is scheduled to go into “code freeze” in July with a stable release expected in 2014. There will be significant development work to move our sites onto Drupal 8 because of big changes that have been made in the configuration, block, and templating systems. We’ll discuss this in more detail at an upcoming “Deep Dive” meeting.
The Present and Future of Content Management
Part of the debate about the future of Drupal is whether or not it will be a Content Management System, an application for organizing atomic units of content and metadata, or a Web Presentation Framework, a system for displaying web pages. To be clear: we use Drupal very much in the latter sense. But with the rise of browsing on phones, tablets, digital signage, glasses, watches, etc. positioning items in a WYSIWYG editor is a waste of time. Responsive design is part of the solution, but we also need to rethink how we are authoring content for the web.
What does this mean for the content management system, for Drupal? Well, fortunately for Drupal is is quite good at content with a lot of discrete fields. There is an argument that the core development for the platform should focus on improving that strength so that Drupal can expand to be a great content management system that meets a wide variety of needs. If a web presentation layer is built on top of that, like we and Amherst have done with Monster Menus, that’s great if it meets our needs, but it may not make sense to have that as a priority for the underlying application.
We have completed the migration of most of the custom modules that make Middlebury’s sites work. Just before leaving for this conference, we were able to get the Middlebury website’s database migrated to Drupal 7 in development and the homepage working with real content from the database. The majority of the remaining work on the project is to move over the theme files one-by-one and test that the output is still working correctly, followed by the migration of a few modules, like the ones that support the campus map, that are presentation-intensive and couldn’t be tested without the theme layers finished.
By default, when you create a Moodle site it is set to be “not available to students” to give you time to add site content before students can access the site.
Unfortunately, the “availability” setting can be a bit hard to find in Moodle settings. To make this important setting easier to change and its current state more visible, you can now set its value from right in the Course Hub when creating or editing the Moodle Resource:
Imagine yourself back in the 2002-2003 academic year. There is no MySpace yet, let alone Facebook, YouTube, or Twitter. Most websites are being created by typing HTML markup or using desktop programs like Dreamweaver. WordPress doesn’t exist yet and won’t support more than a single blog for another three years. Moveable Type and Manilla (early blogging systems) are available, but don’t support the unicode character set needed to properly display text in foreign languages. Each summer numerous faculty would work with students in LIS to build a class website, a process that required many meetings as the faculty member developed the content, then gave it to the student to put on the web. Changes to the content required yet more meetings.
In June 2003 after about a year of development we launched Segue, a content management system that has supported our learning environment for almost a decade. Segue was designed to meet two specific needs. It allowed faculty to create and update their own course websites on their own schedule without requiring a continuous back and forth with support staff. It also allowed web content to be created in all of the languages taught at Middlebury, even Japanese, Chinese, Russian, and Arabic.
Years later unicode support has become common and there now exist a plethora of learning management systems to choose from. In May of 2009, Middlebury decided that Segue had completed it’s tour of duty and that it was time for decommissioning. Today, August 31st, 2012, Segue has served its last page and is now offline.
We want to take this moment to thank Alex Chapin, Adam Franco, Gabe Schine, Christopher Shubert, and Dobromir Radichkov, who developed Segue over the years and supported the service as a resource for our curricular environment.
When you put files in the HANDOUTS/ or SHARE/ folders of your class folder, a “Middfiles Class Folder” resource will automatically be added to your Course Hub site. This resource provides a link that allows students to easily browse the files without having to mount a network drive. There is nothing extra you need to do. Read on for more details.