We made the upgrade yesterday to WordPress 3.3 (and 3.3.1). The video below gives an introduction to the changes and new features in version 3.3. We tested as many features as we could think of before applying this change, but please let us know if something’s not working as it should be.
As an added bonus, we now show videos from MiddMedia using the HTML5 video player in browsers supporting WebM playback: Firefox, Chrome, Opera, and browsers on Android devices. Internet Explorer 9, Safari and iOS users also get the HTML5 video player, playing the video in MP4 format while Internet Explorer 7 and 8 users will still see the flash-based player.
Refer to Facebook’s documentation to determine what are appropriate values for each of these items. Note that the Admins and App ID are now multi-valued fields. Previously there could only be one admin for a page. Now there can be as many as you’d like. Admins will have access to use Facebook Insights for your page to see information on what content is being shared.
I had not realized that the Custom Advanced Segments that I created as an administrator would not be available to other users. Here are links to each custom segment that you can import into your account. In order for this to work, you have to (at least temporarily) switch back to the Old Version of the Google Analytics interface, since segment sharing hasn’t been added to the new version yet. You can switch back to the New Version as soon as you’re done importing the segments you want.
The reason we’re using Advanced Segments here instead of separate profiles with filters is that we’ve reached the internal limit of 50 profiles and would have to delete some of the historical data in order to create new ones. Chris is in touch with our Google reps about increasing our quota and, if he’s successful, we’ll create profiles for each of these services. You’ll still be able to use these Advanced Segments on the main profiles and, personally, I find them a lot easier to work with.
You can also create your own Advanced Segments to filter the Analytics data. Here’s how I created each of these to filter on Hostname (these steps use the New Version):
Click on Advanced Segments in the Standard Reporting screen.
Click on + New Custom Segment.
Give it a name like site.middlebury.edu
Choose Hostname from the green drop-down box.
Choose Matching RegExp from the next drop-down box.
In the text field enter ^site\.middlebury\.edu
Click Save segment.
The “^” character means “at the start of” in a regular expression. This way we can filter on, say, m.middlebury.edu and not have it conflict with museum.middlebury.edu. The “\” is used as an escape character for the period, which has a special meaning in regular expressions.
To kick off the new year, we’re beginning to combine tracking of web analytics under a single Google Analytics tracking code. This will allow us to better understand how visitors to our many web sites and applications browse between them. When someone visits our homepage, clicks on a link to a story in the Middlebury Magazine blog, which then links them to an event with tickets for sale at the Box Office, we’ll be able to visualize the entire visit to the site. We’ll also be able to easily do side-by-side comparisons of traffic across our sites.
The screenshots below show the new version of the Google Analytics interface, which you may choose to enable in the upper-right corner of their page.
When you log in to Google analytics you’ll now want to select “middlebury.edu (all)” (or internal / external) under “UA-993303-1 – http://www.middlebury.edu”. This “middlebury.edu” profile includes traffic from the sites we’ve moved over.
On the Standard Reporting page, you can select Advanced Segments at the top and then narrow the reporting data to include only the sites you want to view.
We have not yet moved over all of our services into this tracking code and some we’ve only moved today, so you’ll only see data for them from January 5 onward. Here’s the list of services we’ve moved at the time of this post:
We have not removed any of the historical data for these services, so you can still check the other profiles you had access to previously to examine that information. This change does not affect any domains other than middlebury.edu, so there will be no changes to miis.edu, davisprojectsforpeace.org, alumniconnections.com, etc. at this time.
If you’d like to learn more about using Google Analytics, there is a great course available on our online learning system at http://go.middlebury.edu/lynda.
Segue’s decommissioning will culminate on Friday August 31st, 2012 when Segue is taken offline. In preparation for this deadline, as of January 1st, 2012, faculty will no longer be able to create Segue websites. We recommend that all new sites be created in either Moodle or WordPress. Segue migration workshops will begin in Winter Term and continue into the Spring and Summer 2012 semesters. More →
The default email template for the Drupal Webform module will send out the date the form was submitted, the name of the person submitting the form (if they were logged in to the site) or their IP address, the value of each field in the form submission and a URL to a page on the site where the form submission can be viewed or edited. This information is usually sufficient, but you might want to have different fields sent to different people when the form is submitted, or provide a custom message to the person who submitted the form, like a “thank you” note.
I’ve received this question from several people now. Below are two videos from Matt Cutts who works on Google’s Webspam team explaining how tagging content mostly does not affect their search results. This also means that tagging largely will not affect how results appear on Middlebury’s site, since we use Google to provide our search results.
This does not mean that you shouldn’t tag content at all. Tags can still be useful for humans who want to find other posts and pages on a topic. However, if you want your page to be easier to find, your time is better invested in making sure that the content is well written, structured and relevant to a particular topic.
To give our colleagues a better idea of what’s changed in our web applications each week, we’ll be preparing this quick list for publication each Friday. Not all of the details of each change are included below, but we’ll be happy to answer any questions you might have in the comments. More →