WiscWeb CMS - WordPress - FAQ

This document is for frequently asked questions regarding the WiscWeb CMS service transitioning from OpenText to WordPress.

Why is the WiscWeb CMS service transitioning from OpenText to WordPress?

The WiscWeb CMS team decided that WordPress offered a better opportunity to serve all of campus, as WordPress is already being used on campus by many departments. In addition to continuing to provide the core WiscWeb CMS service (training, support, hosting, domain registration, etc.), WordPress also allows us to serve these other campus departments by:

  • Purchasing shared university licenses to shared plug-ins
  • Developing custom plug-ins that will be available to all of campus
  • Saving money by not having to purchase as many plug-ins or pay for custom development

Do I have to move my existing OpenText site to WordPress?

If you would like to continue using the WiscWeb CMS service, you will eventually have to move to WordPress. Transitions at other universities have taken as many as five years. There will be no rush or pressure to move as we get the service established. The WiscWeb CMS team will work with you to migrate your site's content and ensure all of your key functionality persists in WordPress.

When will WordPress be available for use via WiscWeb CMS?

There is no timeline at this point. Those details will be included in this document and the information site when a timeline is set.

Will I be able to login with my NetID?

Yes. There is a Shibboleth plug-in for WordPress that the WiscWeb CMS team intends to incorporate with WordPress to allow users to login with NetID. Details will be published once the plug-in is installed and working as intended.

Which WordPress plug-ins will you be using?

We do not know which plug-ins we will be purchasing or implementing at this time. We will update this document, and our information site when we have those details.

Will file names in WordPress match my OpenText file names?

No. WordPress publishes .php files, and will publish in a file structure without a file name at the end. For example, using OpenText, your homepage would publish as http://yoursite.wisc.edu/index.htm. In WordPress, your home page will simply be http://yoursite.wisc.edu.

The WiscWeb CMS team will work with all current OpenText customers to create re-directs for your key pages so that users with bookmarks to old pages will be automatically re-directed to the new WordPress equivalent page.

Will the new WordPress theme be based on the UW home page?


Will training be available for WordPress?

Yes, we will continue to provide classroom, group, and one-on-one training and consultation as we make the transition to use WordPress. This will include just-in-time online training materials as well.

Will OpenText training still be available?

Initially, there will still be OpenText training sessions available as we begin this process, however classroom training sessions will be phased out as more WordPress offerings are created. However, we will still work with you to train new users to your project to ensure your content can continue to be updated.

Where can I send feedback on this process?

You can send feedback to cms-wordpress-feedback@lists.wisc.edu.

Keywords:transition migration opentext website hosting   Doc ID:63436
Owner:Ryan H.Group:WiscWeb CMS
Created:2016-05-16 12:17 CDTUpdated:2016-06-09 08:53 CDT
Sites:WiscWeb CMS
Feedback:  0   0