UW Blogs Network

News


January 23, 2018

Upgrade coming to UWBlogs on Wednesday, January 24th at 11 am

Notice to UW Blog owners At approximately 11 am Wednesday, January 24th, 2018, the UW Blogs Network will be updated to the current version (4.9.2) The Blogs Network may temporarily be unavailable or require a page reload once the update is finished. Further information will be posted at http://blogs.uw.edu/ as necessary. If you have any questions, please…


January 5, 2018

Blogs Network has been upgraded to WordPress 4.9.1

At approximately 1:00 pm Friday, January 5th 2018, the UW Blogs Network was updated to the current WordPress version (4.9.1) for a security and maintenance release. Read More about the changes at WordPress.org Occa­sion­ally, sites with one of the older UW based themes do not update correctly.  If your site is one of them, there is a…


January 4, 2018

Upgrade coming to UWBlogs on Friday, January 5th at 11 am

Notice to UW Blog owners At approximately 11 am Friday, January 5th, 2018, the UW Blogs Network will be updated to the current version (4.9.1) The Blogs Network may temporarily be unavailable or require a page reload once the update is finished. Further information will be posted at http://blogs.uw.edu/ as necessary. If you have any…


December 5, 2017

WP-Typography plugin to be removed from Blogs Net­work

At approximately 12 pm Tuesday, December 5th 2017, the UW Blogs Network will be removing the WP Typography plugin due to problems with server logging software. We apologize for the short notice of this change.  A new option to consider is moving to the UW Sites WordPress Network, which is the replacement for Blogs: sites.uw.edu If…


November 1, 2017

Blogs Network has been upgraded to WordPress 4.8.3

At approximately 3:00 pm Wednesday, November 1st 2017, the UW Blogs Network was updated to the current WordPress version (4.8.3) for a security release: Read More about 4.8.3 at WordPress.org Occa­sion­ally, sites with one of the older UW based themes do not update correctly.  If your site is one of them, there is a sim­ple workaround: Login…



Previous page Next page