The following document outlines the current known issues and updates with the migration from MU Domain Mapping to WordPress’s native domain mapping functionality (scheduled for Wednesday, July 17 at 8am). This list is being regularly updated so please check back if you experience a new issue.
[REVISED 7/17/19 at 12:44pm]
**We are currently working on a fix that will update broken URLs for all live WiscWeb sites.
In the meantime, you can follow these steps to manually fix important broken links in your projects:
- Remove the broken link by clicking on it once and selecting the remove link button
- Highlight the word or words you’d like to link to
- Select the Insert/Edit Link button
- Start typing the name of or a keyword for the internal page you would like to link to. A list of related pages should populate.
- Select the page you would like to link to from the list that appears.
- Click on the blue arrow to implement the link
- Update your page
Similar to broken links, there is a chance that the buttons you created for your site will break if you used the full .wiscweb.wisc.edu path for the URL portion of the code.
To update your buttons, toggle to the Text tab in the Text Block and locate the code for your button. Find the portion of the code that starts with href=. Leave the quotation marks. Remove the https:// and your WiscWeb URL but leave the page path information.
URL Example 1:
If your before URL is
"https://mysite.wiscweb.wisc.edu/page-name/" then your updated URL path should just be
URL Example 2:
If your before URL is
"https://mysite.wiscweb.wisc.edu/parent-page/page-name/" then your updated URL path should just be
Button Code Example 1:
<a class="uw-button button-cta button-cta-reverse" style="background: #c5050c; border: 0px; color: #fff !important;" tabindex="0" href="https://sitename.wiscweb.wisc.edu/page-name/">Button Name</a>
<a class="uw-button button-cta button-cta-reverse" style="background: #c5050c; border: 0px; color: #fff !important;" tabindex="0" href="/page-name/">Button Name</a>
Button Code Example 2:
<a class="uw-button button-cta button-cta-reverse" style="background: #c5050c; border: 0px; color: #fff !important;" tabindex="0" href="https://sitename.wiscweb.wisc.edu/parent-page/page-name/">Button Name</a>
<a class="uw-button button-cta button-cta-reverse" style="background: #c5050c; border: 0px; color: #fff !important;" tabindex="0" href="/parent-page/page-name/">Button Name</a>
Registration Page Display
If you are logged in to WiscWeb and click through to the live view of a page, you may see the WiscWeb Registration page:
To fix this issue, please navigate to https://wiscweb.wisc.edu/wp-admin and login with NetID credentials (if prompted).
If you are not logged in when you see the Registration page, there’s a good chance the link you selected is broken. Please follow the steps above to fix the broken link or email us to let us know: firstname.lastname@example.org.
Logged In View – Absence of Gray Nav Bar
Users may notice that they are periodically missing the gray navigation bar at the top of their page while logged in to a live page of websites. This is a result of the browser caching the unauthenticated version of the page.
Follow these steps to view your gray nav bar:
- Confirm that you are logged in to WiscWeb (https://wiscweb.wisc.edu/wp-admin)
- If you are logged in and still seeing the issue, refresh your page. The gray bar should appear on refresh as this will clear your previous page cache.
Redirects for Those with Multiple Domains
If you have more than one live domain reserved for your site, your secondary domains were recently moved from the MU Domain Mapping plugin to an Apache config file. We pulled your domain information from the plugin prior to the change to the native domain mapping functionality, but there is a chance we missed one.
If you are noticing that your secondary domain(s) is/are no longer redirecting to your primary production domain, please email us to let us know. Include your site name and any of the production domains that are no longer working.
Logged In URL
Prior to the change to native domain mapping, users saw a *.wiscweb.wisc.edu web address in the address bar of the browser when logged in to the editing environment in WiscWeb (ie. history.wiscweb.wisc.edu). After the change, if your site is launched/fully live, you will see your regular production domain in the address bar – even when editing in the Dashboard.
In addition to the improved page load performance for unauthenticated (non-logged in) WiscWeb site users, we anticipate that the change to the WordPress native domain mapping functionality will allow for better integration with major caching plugins like WP Total Cache. This means that we will be able to better research, troubleshoot, test, and deploy changes that should make our environments run faster.