UNLcms website editing unavailable Sat May 18, 2019

On Saturday, May 18, 2019 we will be performing maintenance on the web content management system, https://unlcms.unl.edu. During this time logging in will be disabled and editing will not be possible.  The maintenance window is scheduled for 10 am CDT to 4 pm CDT, however we except the unavailability will be significantly shorter than this.  We expect to be finished before 11 am.

During this time sites will remain online and available to the general public.  Once editing resumes, some users may continue to see old content while DNS changes propagate across the internet over the ensuing hours.

To see a list of websites you have editing access to that will be affected, log in to https://unlcms.unl.edu/mysites

October 1, 2018: Decommissioning login.unl.edu

You may have received a notice from Identity & Access Management that your website is using login.unl.edu for user authentication and needs to be updated prior to October 1, 2018.

The entire CMS and all websites on it will be updated this Sunday, September 16.  No action is required by Site Admin.

Previewing your site to the new 5.0 version of the UNLedu Framework

Preview

If you are a Site Admin you can preview your site in the latest development version of the 5.0 release of the UNLedu web framework and templates.

Doing these steps will only convert the theme for your user account (end-users will still see the site as it is now) and you can switch back and forth any time.

Oct 1, 2017: Switch to https://

On October 1, 2017 we will be forwarding all http:// requests to their https:// equivalent. Serving over HTTPS is now increasingly viewed as a best practice for user privacy and security. Starting later in October, the Google Chrome browser will label pages with a "Not secure" warning in the address bar when users enter data on an HTTP page. This will impact all UNLedu Framework pages (and hence all UNLcms pages) since the UNL site search bar is in the header of every page.

What You Need to Do

tl;dr

Make sure that any Javascript file references or iframe embeds use https:// in their URLs.