UB WordPress (UBWP) is a multi-tenant, shared WordPress implementation specifically designed to provide a Web blogging platform to supplement other web content management platforms such as UBCMS.
UBWP is not intended as a general-purpose content management system for official university Web communications or for personal weblog pages. Departments are directed to UBCMS as an official web communication platform.
Owing to the multi-tenant nature of the UBWP system, there are certain restrictions: child themes cannot be created (there are optional themes available designed to support the UB brand as styled within UBCMS); no custom coding can be supported; and, plug-ins must be requested, approved and installed by UBWP system administrators to ensure system stability. Also e-commerce and financial transactions cannot be processed via UBWP since the system has not been architected to be PCI compliant.
UB departments, organizations and departmental programs that do not fit the criteria for a site on UBCMS will have UBWP available as an alternative tool for hosting a website. UBWP is restricted to active university faculty, staff and authorized students whose role is to author or publish official university web pages.
Individual UBWP sites requested by faculty, staff and authorized students must use the sites for the purposes of academic, teaching, learning and research.
Requests for access to UBWP must be made through the online form
located at www.buffalo.edu/ubit/forms/request-wordpress-site.html.
Requestors must have an active UBITName.
UBWP service is available 24 x 7. Support for UBWP service is restricted to business hours, 8:30 a.m. to 5:00 p.m.
Availability of the UBWP service may be interrupted for maintenance and other updates during maintenance windows. Announcements and alerts are posted through the Alert System and communicated with the UBWP listserv.
WordPress upgrades and patches to will be applied to the WordPress environment as they are released.
Application related updates will occur in the development environment first, time will be given for testing in this environment and then applied to production. Timeframe between the development and production upgrades will be based on criticality. Production upgrade will be 2 weeks from the date of the development upgrade.
Tenants are strongly encouraged to verify the functionality of their sites in development environment when the changes are announced and production after the upgrades. Sites that are not functioning will need to be corrected by the tenant/site developer. Rolling back to previous versions of a plugin may not be honored depending on the criticality of the patch release of the product/plug-in.
Plug-ins will be part of the application upgrade process and will follow the schedule as outlined above. Individual plug-ins may require additional updates if a patch is released to address a security vulnerability. These patches will be fast tracked based on the criticality of the issue.
Access to the development environment is from UB address space
The support of the WordPress infrastructure is a joint
responsibility for CIT (EIS) and the tenant.