The Drupal 7.37-cws-1.0.0 update was released to our development environment on Tuesday, May 11th, 2015, and will be released to production sites on Tuesday, May 19.  This release includes:

OSU Drupal Bug Fix

  • In the previous release, which included a major update to the Media module, it was discovered that the Colorbox module no longer worked, which affected the display of our Video Carousel feature. Videos themselves still worked, but they would not open in the “lightbox” that we were using for the Video Carousel feature. The fix for this required the inclusion of a new module, media_colorbox. This allowed us to simplify the View that displays the videos, so in the end we now have a better solution. This fix has already been pushed out to all of the development sites, and many of the production sites that were using videos. The rest of the production sites will get the update on Tuesday May 19 during the normal update cycle.

Drupal Core Bug Fix

  • In Drupal 7.36, a regression occurred which caused certain kinds of content to become disabled if they were originally defined by a module that is no longer available.  This has been corrected.

Major Version Upgrade

  • Drupal core 7.37

Security Updates

  • None

CWS Custom Module Updates

  • live_feeds-7.x-2.3.1 – the Beaver Job parser has been added
  • doug_fir-7.x-2.9.0 the LPI theme variant has been added

Contributed Module Updates

  • faq-7.x-1.0 has been updated to its first stable release

New Modules

  • job_scheduler-7.x-2.0-alpha4 added to support Feeds module


If you have questions or concerns please contact us though our contact form.

The Drupal 7.36-cws-1.2.0 update was released to our development environment on Tuesday, April 28th.  This release includes:

Major Version Upgrade

  • Media -> 7.x-2.0-alpha4
  • File Entity -> 7.x-2.0-beta1

The long-awaited update for media handling has been provided with the adoption of Media 7.x-2.0-alpha4.  Please visit the OSU Drupal Community site  to learn more about the Media module, through our Making Media Manageable article and the Media Component Overview, which provides rudimentary instructions and evaluation information.

Security Updates

  • Display Suite 7.x-2.8
    • This update was actually pushed out to production immediately last week to address a Cross Site Scripting vulnerability in production. It has been added into the update package for this week’s dev environment updates.

CWS Custom Module Updates

  • doug_fir 7.x-2.8.5
    • Updated Google Analytics javascript code
  • live_feeds 7.x-2.3.0
    • Added a new parser plug-in for Beaver Careers
  • osu_editor 7.x-1.0.0
    • New module to include all Media module and File Entity related configurations
  • osu_manager 7.x-1.1.3
    • Back-end updates, added permissions for Media and File Entity modules
  • osu_author 7.x-1.2.3
    • Back-end updates, added permissions for Media and File Entity modules
  • osu_architect 7.x-1.2.3
    • Back-end updates, added permissions for Media and File Entity modules
  • osu_editor 7.x-1.0.0
    • New module to include all Media module and File Entity related configurations
  • osu_groups 7.x-1.4.2
    • Fixed query used to determine the top-level book page

Contributed Module Updates

  • Advanced help 7.x-1.2
    • Mostly back-end fixes, though a few different, small CSS issues within the module were corrected.
  • Better Exposed Filters 7.x-3.2
    • Fixed AJAX issue that was failing with BEF links
  • CAPTCHA 7.x-1.3
    • Fixed issues with session reuse errors, improved image markup, provided environment specific CAPTCHA disabling
  • Features 7.x-2.5
    • Fixed back-end issues
  • reCAPTCHA 7.x-1.12
    • Fixed back-end issues
  • Webform 7.x-4.7
    • Fixed some conditionals related bugs, corrected some incompatibilities with Media module and other token-like markup, addressed several back-end issues

New Modules

  • Plupload    7.x-1.7
  • Multiform   7.x-1.1

These modules were added to provide bulk upload functionality for the Media module.

If you have questions or concerns please contact us though our contact form.

The Drupal 7.36-cws-1.0.0 update was released to our development environment on Tuesday, April 14th.  This release includes:

Security Updates


CWS Custom Module Updates

OSU Groups Module

An “Hours of Operation” field has been added to the Group node type.

Highlights Feature

The background fill that displays when a mouse hovers over a transparent background highlight has been fixed.

Contributed Module Updates


If you have questions or concerns please contact us though our contact form.

The next CWS Drupal release, 7.35-cws-1.0.0, will be deployed to production Drupal 7 sites on Tuesday Mar 24. This release includes:

Security Updates

  • Drupal core 7.35
  • Webform 7.x-4.5
  • Chaos Tools 7.x-1.7

CWS custom module updates

It was discovered that the varnish cache was not being cleared when the site cache in Drupal was cleared. In response, a hook was added to clear the varnish cache for a site when the site cache is cleared through using “Flush all caches”.
Lookup Module
After deleting the module, the content in the database was still present, including the tags data.  This has been corrected.
OSU Groups
Login redirection to dashboard was broken.  This has been corrected.
The appropriate Actions Permissions were added and provided to the group user role.  These permissions will allow group managers the ability to perform bulk operations when managing their users.
OSU Group Views
Every view that is a part of the OSU Group Views module has now been configured to cache for 1 hour, the same as Feature Story.  Therefore if changes do not immediately show after you make them, flush the cache.

Updates to contributed modules

New contributed modules

Domain Context
This will allow sites that use the Domain module to create Contexts that use the domain as a condition. This will be particularly helpful in

Removed contributed modules

We are no longer using this having instead gone with the Colorbox module.

If you have questions or concerns please contact us though our contact form.

Central Web Services is continuously making improvements to our Drupal platform. We’re fixing bugs, updating modules, adding new features, and enhancing existing features. For the past 3 years we have been on roughly a six week release cycle. If there were important security updates it could be shorter, but frequently it was longer. We want to change that. We want to be able get new features, and fixes out to the sites that requested them in a much more timely fashion.

As part of our Agile Development process we have been implementing procedures for automatic testing and deployment of changes to our Drupal modules and features. This has made it much easier for us to find and fix bugs and make sure that a feature is ready for prime time before it reaches your site.

This will allow us to move to a two week release cycle. We will update all of the Drupal 7 production sites every other Tuesday. Sometimes these updates will be minor and provide no additional functionality, sometimes they may only include security updates, but often they will include enhancements to existing features, or new features entirely. We will communicate these changes through e-mail announcements to site managers, through the Drupal Support e-mail list, and through a post here on the OSU CWS Blog .

As always our goal is to help you create the best websites we possibly can. We think this change will really help in that regard.

As we’ve been talking to people about consolidating Drupal sites into larger sites in Drupal 7, questions come up about how to set up navigation for a much larger site. With academic units the navigation breaks down nicely along the lines of colleges, schools, departments, and programs, but with administrative units it is not always that clear. When Information Services was faced with this task a decision was made to de-emphasize the organizational structure and instead focus on the services provided. This makes a lot of sense as most visitors to our websites really don’t care that much about our department structure but rather what we do and what services are available to them. As CWS was designing how we would use Organic Groups to combine the old Drupal 6 sites into the new Drupal 7 site for IS we wondered how well OG would work with this service oriented approach. Fortunately IS had already done the hard work of coming up with logical groups of service categories, and the services within each one. We then were able to map the groups directly to the services, and organize them into “parent units” which were mapped to the service categories. By including the names of the service. and the category, in the site name header, we accomplished the goal of having these appear as distinctive sections of a website.


Each title is a link back to that level of the site, just as the site name has always been a link back to the front page.

The services based navigation solves many of the problems of organizing a large website, but sometimes there is still a need to represent the department organization as well. For example to see where people work, and where they are located, you still might want to have an organizational view of your website. At first we were not sure how to approach this, but then realized that we could have a parallel structure of parent units and groups that matched the department structure. So for example a parent unit for Media Services, and a group for Central Web Services. Once we determined the right approach this was easy to implement and works well in practice.

To see this for yourself please visit the Information Services website at . The services and categories are all in the “Services” menu and the departments are under “Directory & Contacts” => “Organization”. As you explore this site think about how we can use this model on your Drupal site when it comes time to upgrade it to Drupal 7.



The close of Drupalcon 2013, held in Portland, has left me with lingering, fond memories of 3,300 nerds gathered in a glowing Drupalicious camaraderie.  The convention was a great success, despite the rain and ever present Wi-Fi issues.

So what, you may ask, was my personal highlight?  Maybe it was the tantalizing sneak previews of Drupal 8 with all its built-in mobile goodness?  Perhaps it was the really excellent sessions that were provided in the brand new and much needed Education and Government track?  Or, was it possibly getting my photo taken with User-1 himself, Dries Buytaert, and giving him some of our very own OSU Drupal swag?

These were all great things.  Really they were.  But, ultimately, they all pale in comparison to the keynote address given on Day Two, in my eyes at least.

This particular keynote, “Thriving in a World of Change: Future-Friendly Content with Drupal”, was presented by Karen McGrane, a world-renowned user-experience designer and content strategist who has led content projects for The New York Times, Conde Nast, and Time.  In addition to spearheading projects for enormous publishing corporations, she’s also a managing partner at Bond Art + Science, a UX consultancy she founded in 2006, and she teaches Design Management in the Interaction Design MFA program for the School of Visual Arts in Manhatten.

In short, this lady knows her stuff, folks.  If you’re a content author, site architect, or web developer on any platform, I strongly suggest taking a peek at what she has to say regarding content structure and strategy.  You will leave more informed.  You might even be a little entertained.  You certainly won’t be sorry.

Please note that the actual keynote begins at 11:30 minutes into the video.

This was the biggest DrupalCon yet with over 3,300 people, and a substantial number of them were from Higher Ed. My presentation on how we do Drupal at OSU, was the first day of the conference, so I had people connecting with me the rest of the week to talk about how they are doing Drupal at their school. For the most part we are ahead of most of the other universities I talked with as far as our use of Drupal for our campus websites. Some schools have accomplished more on the technical side of what can be done with Drupal, but do not have the buy in from the majority of campus the way we do. Few schools have been as successful in providing centralized Drupal hosting and development as we have. I attribute this to our partnership with Web Communications. It is clear that the schools in which the IT and Marketing departments have formed good working relationships are the most successful when it comes to providing a high quality unified web experience across the institution.

Another big topic of discussion was in the way Drupal is used, not just in education but everywhere. We call Drupal a content management system, and indeed it is a very powerful content management system, however for the most part we, and others, don’t really take advantage of these capabilities. We tend to use Drupal more as a Web Publishing System, which really is very different. What people have wanted out of Drupal is for it to be like a word processor for the web. People like the wysiwyg tools and the familiar Word-like tool bar. The problem is that the web is not like a printed document. It was a fairly easy leap from print publishing to web publishing when web pages were viewed on desktop systems that provided roughly the same page size as a printed page. We have now irreversibly moved beyond that to where we need to be able to deliver our content to devices of every size and configuration. The old word processor model fails miserably in this new environment. Many of us in web development have strived for years to separate content from presentation. This has become more important now than ever and Drupal can really help with this, but not if we continue to embed HTML markup into our content through the use of a wysiwyg editor. Rather content needs to be managed with metadata that semantically describes what the content is, not how it should look. So we say that a piece of content is an address or a phone number, or a course description, or a an event title, etc. Then we can present the data in the best possible way for whatever device is displaying it. For the web this is still HTML markup, but for other devices it may not be HTML at all.

In working with departments on their websites recently we have been trying to put this more into practice. We still see so many sites where people have hard coded directory information like names, phone numbers, and e-mail addresses. This data then is  carved in stone in that it is really difficult to keep up-to-date. What we want to do instead is to treat the content as data, and store it in fields, and then use views to present the data in a variety of formats. Drupal is really good at this, but we’re not fully taking advantage of it’s strengths. If we start now we’ll be in a much better position to deal with the next game changing device that comes along and needs to display our web content.

This was a great DrupalCon for OSU. On Wednesday night there were about 15 of us that went out to dinner. We rarely get a chance to socialize like this a work and we really enjoyed it. We vowed to continue building the OSU Drupal community and to include some social gatherings at least every couple of months. We don’t want to have to wait until the next DrupalCon to get together again. So if you work with Drupal, or the web in general. Please join our community group and attend the next meeting. More information is at

At least 12 of us from OSU will be at DrupalCon next week in Portland. This is an exciting opportunity for us to connect with people from all over the world who are involved with Drupal. This year DrupalCon is offering a new track for Government, Non-Profit, and Education. For the first time at DrupalCon there will be sessions devoted to the unique challenges we face as a university, as well as sessions that showcase what some of our peers are doing with Drupal at other institutions. I have the honor of presenting the first of these sessions in which I will discuss how we’ve managed to support such a large scale Drupal environment, and some of the interesting things we are working on. My session has been selected as a featured session – . This really puts the spotlight on OSU as a leader in the Drupal higher-ed community, and extra pressure on me to represent the university in the best possible light. This is a great honor for me and I’ve been working hard to make sure I have a good presentation and that I’m well prepared to give it.

One of the challenges we always face at DrupalCon is to make sure we stay focused on the issues we need to solve here at OSU. This year there will be a lot of sessions devoted to the upcoming release of Drupal 8. Of course we are hard at work on Drupal 7 and still have a long way to go getting our sites onto that version. We know we have to balance our need to stay current and make sure we understand the new things that Drupal 8 brings to the table, with our need to find solutions to the things we’re encountering everyday as we move further into Drupal 7. Fortunately there will be a good mix of sessions that should allow us to do that, and even though there will be much buzz about Drupal 8, we know it will not see wide spread usage for at least two more years.

This will be a busy week, packed with lot’s of learning opportunities, and meetups with people doing the same things we are using Drupal. A couple of us may try and do some blog posts during the week so stay tuned to this spot for updates.

Paul Lieberman
Central Web Services

As we looked at how we would upgrade all of our Drupal 6 sites to Drupal 7 we realized we had a big problem. Big as in over a thousand individual Drupal sites. We have become the victim of our own success in that we made it too easy to create new Drupal sites whenever we received a request, without first asking if a new site was really necessary. Drupal itself scales very well. It can handle much bigger sites than we currently have. By creating so many smaller sites we were actually making it harder for people to get around on our pages because larger sites became fragmented with no global navigation between the various units. It also made it harder for people to share data across sites, which caused unnecessary duplication of data input. Finally it created a lot of administrative overhead for CWS to keep this many sites upgraded.

We made it a strategic direction for Drupal 7 to begin consolidating as many small sites into their parent units as possible. We knew the first issue we would have to face is how to divide up the authoring responsibilities while maintaining ownership for different parts of a site. It turns out one of the reasons we currently have so many sites is because different people are responsible for content creation and wanted to make sure other people would not be able to modify their work. While this problem could easily be solved by just getting some agreements between the various authors on a larger site, we wanted to be able to assure people that we could prevent this possibility through Drupal permissions. We also knew that people wanted the ability for their sites to have some distinctiveness. While all of our Drupal sites adhere to the branding guidelines set forth by Web Communications, there is still room for sites to provide certain characteristics unique to their department or unit. We set out to find a solution for this.

What we came up with is a Drupal module called “Organic Groups”. The organic part does not mean that the groups were grown with abundant amounts of compost, but rather that they are flexible enough so that groups can be configured in a variety of different ways. For example we knew that colleges would need to build groups for their schools, departments, and programs whereas administrative sites would have a variety of working units that will need groups. After some testing we were confident that the Organic Groups module was going to suit our needs and so we started the work of communicating with people about our plan, and get some sites on board.

Central Web Services is a devision of Media Services which is in turn part of Information Services. There are a number of other units under IS including Enterprise Computing Services, Network Servies, and Technology Support services. When we began the task of updating the IS site using Drupal 7 it was agreed that we would consolidate a number of separate websites into the IS site using Organic Groups. The IS site is organized around the services that we provide. Each service is a group. Each group is also part of a service category. We are still in the process of converting all of this to Organic Groups but it looks like its going to work very well.

On the academic side of things we also have been working with the College of Liberal Arts to upgrade and consolidate their sites. We currently have the parent college site in Drupal 7 and are working with them to migrate the departments one a time from the old Drupal 6 sites. For a college the groups map nicely to departments which group into schools. Each department can have it’s own set of rotating features, highlights, directory listing etc. The department and school name also show up as the site name along with the college. Departments can have their own content editors, or and editor can work for several departments. There can also be college wide editors who can help with all of the departments if that is the way they want it.

Art department site name showing the school and college

Department name becomes the main site name, while the College and School names are combined above, with each linking to its respective front page.

Once we have completed CLA and IS we will begin working with other departments to consolidate and upgrade sites to Drupal 7 at an accelerated pace. The end result will be better websites for everybody.