Skip to main content Skip to navigation
Web Communication WSUWP Platform

Open Lab for April 18th, 2019

Topic: Using Gravity Forms to automatically create posts from user submitted content.
Location Change: ITB 2071
Time: 9:30 am – 11:00 am

For open lab this week we’ll spend some time walking through how to set up Gravity Forms to automatically create posts from user submissions including approval and review workflows.

If you have any general website support questions open lab is a great place to bring them!

Open Lab for April 12th, 2019

Topic: Brainstorming session on SEO for the WSUWP Platform and WSU websites.
Location Change: ITB 2071
Time: 9:30 am – 11:00 am

For open lab this Friday we’d like to spend some time discussing search engine optimization needs for WSU websites. Specifically we’d like to hear from you what tools, features, and training you think would be beneficial to improving SEO on your site(s).

If you have any questions about SEO or general website support Open Lab is a great place to bring them!

Open Lab Location Update & Adams Spine Template Available

Open Lab

Topic: Quick intro to Adams Spine Template.
Location Change: ITB 2071
Time: 9:30 am – 11:00 am

Adams Spine Template

The Adams spine template is now available for any website on WSUWP (WordPress Platform). The new template can be previewed or applied from the customizer.

Details about the new template, are located in our Confluence Knowledge Base.

This is a 1.0 release, and we would like to get feedback on any suggestions you might have to make the template better. Please submit feedback to our Jira Service Desk.

WordPress 5.1 Update & New Spine Template Available

WordPress 5.1

The WSUWP (WordPress Platform) is now running WordPress 5.1! If you are interested in learning more about changes and updates check out the WordPress post detailing the release.

Currently Gutenberg (the new editor included in 5.0+) is disabled for all sites while we work on a rollout plan. We’ll post additional updates/timelines about Gutenberg as we have them.

Baker Spine Template

The Baker spine template is now available for any website on WSUWP (WordPress Platform). The new template can be previewed or applied from the customizer.

Details about the new template, are located in our Confluence Knowledge Base.

This is a 1.0 release, and we would like to get feedback on any suggestions you might have to make the template better.

Issues & Feedback

If you experience any issues with your sites after the update or if you have feedback on making the Baker template better please submit them to
to our Jira Service Desk.

Events site update

The WSU Events site was recently overhauled to provide an improved experience for visitors and users alike. Feedback is welcome and appreciated as the site continues to be developed!

New design

The most obvious change is an updated design. All events for the given day are displayed in the home page header, a search field and filters for viewing events by type or campus are provided below that, and a curated set of events is featured in the body.

All other pages include the given day’s events in the footer, and the entire site has a persistent footer with a calendar for quickly viewing which days have events, “Submit an Event” and “Contact Us” buttons, and a mark that links back to the home page.

Event entry

The new event submission form was designed to be more intuitive and easier to use. Built using WP Event Calendar as a base, some additional fields were added for capturing further details visitors might expect to see.

The venue and organizer entry processes in the previous system led to the creation of multiple duplicates, so the new system offers a simpler interface for both.

  • For venues, there is now a list of buildings to select from, and a “Notes” field for entering more specific details (like a room number, for example).
    • If you don’t see your building listed, or notice that the name of a building isn’t quite correct, please don’t hesitate to contact us about it!
  • For organizer information, there are fields for entering a “Name”, “Email”, and “Phone Number”.

A completely new set of fields is available for creating a call to action link. These are optional and can be used for purposes like linking to a registration or RSVP form.

Users of the previous site might notice that “Tags” and “Categories” have been dropped in favor of “Types”. The “University Organization” taxonomy has been updated, too, and between these two changes, a majority of use cases for “Tags” and “Categories” from the old system are accounted for.

Event feeds

As with the previous site, the new site serves as a system-wide calendar and offers API endpoints that can be used for displaying specific subsets of events on any site.

For sites on the WSUWP Platform, the WSUWP Content Syndicate Events plugin is still the easiest way to display a feed of events. Support for the “Type” taxonomy has been added, and the documentation will be updated to include instructions on how to pull a feed by “Type” soon!

A new taxonomy interface

In an effort to provide a better experience when managing taxonomy terms for posts, we have consolidated the multiple taxonomy meta boxes into one easy-to-use interface.

Rather a complete departure from the default experience, the new interface leverages the Select2 library to simplify and enhance it. Each taxonomy is represented by a single input. Clicking or focusing on a given input will provide the complete list of terms for that taxonomy. The terms can also be searched by simply typing in keywords. Both of these features are exemplified below:

An animated screenshot showing an example of the search support.
Too many terms to scroll through? Just start typing to search!

The process for adding new terms to a taxonomy is largely the same as it was previously. For hierarchical taxonomies like Site Categories, click the “+ Add New Category” text and use the small form that pops up to add the new term. For non-hierarchical taxonomies – like Tags – simply type in the new term followed by a comma. While it may seem strange that the process is different depending on the taxonomy type, there are technical reasons for the differences (one being that Categories and other hierarchical taxonomy terms can theoretically contain commas). Aside from those reasons, keeping the two different processes seemed to make more sense than introducing something new and unfamiliar.

A screenshot showing how to add new terms.
Adding new categories or tags will be familiar to those who are used to the old interface.

For the developers out there interested in including their custom taxonomies in this interface, or using it on custom post types, the
wsuwp_taxonomy_metabox_taxonomies
and
wsuwp_taxonomy_metabox_post_types
filters, respectively, are provided for doing just that. The use of these filters will be documented soon!

Edit CSS updated with new features on WSUWP

Version 2.2.0 of WSUWP Custom CSS has been released and deployed to the WordPress platform at WSU.

This release contains a handful of things that may be interesting to anyone spending time editing CSS on their site.

Edit CSS now supports easy saving via AJAX. Rather than click “Save Stylesheet” every time you have a change to save, you can use CMD-s or CTRL-s on your keyboard. A message will briefly show at the top of the screen showing the progress of the save and then you’ll be able to continue working.

Support for full screen editing is also available. Hit ESC on the keyboard whenever the cursor is focused on the Edit CSS window and the code editor will fill the browser window. AJAX saving with CMD-s and CTRL-s works in this view as well.

Thanks to Nate Owen for both of those changes!

Also of note:

  • The CSS preprocessor settings have been removed. These never actually worked in our implementation, so now the clutter is gone. 🙂
  • The font-feature-settings property is now supported.
  • Multiple display properties are supported in a single CSS rule.

Enjoy the changes. If you have any requests for missing properties or new features, please open an issue on GitHub, stop by a weekly open lab, or leave a note in the WSU Web Slack.

Managing editorial access for pages on WordPress at WSU

In a default WordPress installation, users with a role of Author, Contributor, or Subscriber have varying levels of access to posts, but do not have access to create or edit pages. Users with a role of Editor or Administrator have full access to both.

At WSU, pages are frequently more useful than posts for managing large amounts of content on a site. We have made a few adjustments to the Author and Contributor roles so that more users have access to pages without having the full set of capabilities associated with the Editor or Administrator roles.

New Pages

Authors and Contributors can create new pages by default, but must submit them for review before they are published. An Editor or Administrator can review the content and then publish when ready. As long as the page has not been published, the creating Author or Contributor can continue to edit the page and resubmit for review.

Editors and Administrators can always create and publish new pages.

Existing Pages

Authors and Contributors are not able to edit existing pages by default, even if they are assigned as the page author.

If the administrator for the site enables the Editorial Access Manager plugin, which is available for all sites on the WSU platform, Authors and Contributors can be assigned as editors for the page by either role or user. Once assigned as an editor for a page, Authors and Contributors are able to edit all parts of the page and publish their changes at will.

If you have any questions about access to pages and posts by any of the user roles, please feel free to stop by open lab on Friday mornings or in the WSU Web Slack team at any time.

New WordPress Plugin: WSUWP Content Visibility

Management of page visibility has long been on the list of features in progress for WordPress at WSU. Today, the WSUWP Content Visibility plugin is available for activation on your site!

WSUWP Content Visibility is a WordPress plugin used to control the visibility of content for groups of authenticated visitors. The interface for managing the visibility of content is built into the Publish area of a page or post.

Four groups are provided by default:

  • Members of this site include anyone that appears in your site’s list of users. They can be subscribers, authors, editors, or administrators.
  • WSU Network ID (NID) includes anyone that has a valid WSU NID. They do not have to be members of the specific site.
  • WSU Students includes anyone that has a WSU NID and is a student.
  • WSU Employees includes anyone that has a WSU NID and is an employee.

If a non-authenticated user arrives on a page restricted by WSUWP Content Visibility, the user will be redirected to a login screen. If an authenticated user arrives on a page and is not a member of an assigned group, that user will be redirected to the home page.

For more details, check out the plugin documentation. If you have any questions or run into issues, please stop by open lab, join our Slack team, or open an issue on the GitHub repository.

Releases: WSUWP Platform 1.4.0, WordPress 4.4.2

WordPress 4.4.2 was released yesterday and the WSUWP Platform was immediately updated to match. There are no large changes, though several bug fixes and two security fixes were included. WordPress 4.5 is scheduled for April.

What follows here is the full release information for WSUWP Platform 1.4.0, from our open source project on GitHub.

This is the thirty-third production release of our open source WSUWP Platform project. The official tag of this release is 1.4.0.

A full comparison of changes is available is available. Here are the notes from the release:

Enhancements

  • Upgrade WordPress 4.4.2
  • Allow network admins to promote users of their network to network admins.
  • Search site URL as well as site name in each network’s quick search under My Networks.
  • Enable zip file uploads for all sites. “Extended” networks are no longer used.

Bugs

  • Clear the wsuwp:site cache key for a domain/path when a site is deleted.
  • Ensure the “View” link is consistently places in the admin header when editing a post/page.
  • Fix logic to determine if My Networks menu should be shown. Users of multiple networks will now see My Networks.
  • Fix mistyped branch used for provisioning in Vagrantfile.