Table of Contents

1. Frequently asked questions and resources
2. How to upgrade your site
   1. Step 1
   2. Step 2
   3. Step 3
3. Website Changes
   1. .Net 4
   2. sites with database
   3. sites with authentication
   4. https only
   5. UW branding
   6. includes site
   7. a note about testing
4. Timeline
   1. January 23^rd
   2. January 23^rd - May 19^th
   3. May 19^th

 

Frequently asked questions and resources

How do I change my site to a CMS site?

• To change your Central Site to a CMS site, please follow the Steps to migrate your site into the CMS.

I no longer need my site; how do I request it be removed?

• You can request your site be deleted using the delete a site request page.

My website has a database, what do I need to do?

• The new testing sites will point to the current production databases. For more information or clarification please see the sites with databases section.Should you have a technical difficulty, please contact helpdesk.

Why are you contacting me for this update?

• We are reaching out to all site authors and site owners. If you believe that this is not you, you can update your site information here or request assistance from the helpdesk.

How do I update the owner and author information for this site?

• If you are the owner or content manager of this site, you can update site information here. If you are not the current owner but need to request changes, please contact the helpdesk.

 

How to upgrade your site

 

Step 1

• UW IT has copied your current development and production web files to the new environment.
• You will need to validate the look and functionality of you site in the new environment. For guidance on testing and changes see this page.

Step 2

• If you are confident your site is working as desired on both https://wwwnew.uwyo.edu/sitename and https://wwwdevnew.uwyo.edu/sitename, you can request you site be moved to the new environment here.

Step 3

• Validate the look and functionality of you site in the new environment. For guidance on testing and changes see the Website Changes section.
• Note the old environment will no longer be available, and you will need to update your sites using the \\webnew and \\webdevnew going forward.The https://www.uwyo.edu/sitename and https://wwwdev.uwyo.edu/sitename will now point to the new environment.

 

 

Website Changes

.Net 4

In the new Central Sites environment, the default .Net version is .NET 4.0 CLR. This is an upgrade from the existing .Net version of .Net 2.0 CLR. While Microsoft does a good job of maintaining compatibility, if your site uses .Net, you will want to test it thoroughly. Microsoft has a migration page available to users.

What to test for:

• If your site uses ASP.NET pages, you should verify the functionality of these pages on your site.
• If your site requires ASP.NET version 2, please contact helpdesk to open a ticket for your site.

sites with database(s)

Sites that use a database back end will want to verify full functionality and resolve possible issues with your sql connection string.

What to test for:

• Check pages that display or update database information. Please note that unless you have explicitly coded your site to use a development database, the code that was copied will likely point to your PRODUCTION database. Test with caution.
• Connection strings may need to be tested and modified.We have seen successful classic asp connections with 'Provider=MSOLEDBSQL19;Use Encryption for Data=Optional', and aspx sites with 'providerName="System.Data.SqlClient"'.
• Microsoft Access database are no longer supported. If your site uses a Microsoft Access database, please contact the helpdesk to open a ticket for your site.

sites with authentication

Sites that use authentication will need to verify a Target Framework of .net 4.0 or higher

What to test for:

• If you develop your site in MS Visual Studio, be aware that changes to the Target Framework may overwrite your web.config.
• Verify authentication works as desired after modifications to your code.

https only

With the upgrade to sites served on www.uwyo.edu, all sites will now be served as https only.  Previously, websites were available as either http or https, however https provides a number of security benefits, allowing end users can be confident that University of Wyoming sites haven’t been spoofed and are encrypted.

What to test for:

• Verify that any hard links on your page use https rather than http to avoid mixed content warnings.
• Test using multiple browsers to verify users aren’t getting content warnings if some links are http.

UW branding

Most Central sites follow the look and feel of the main www.uwyo.edu website. To avoid issues with future branding changes, make sure you are following best practices and receiving updated branding information.  Please note that the UW header and footer will most likely be changing with the new CMS and this page will offer update information when it is available.

What to test for:

• Verify that branding links are not referencing other sites that may change as style guides are updated.
• Verify that branding is being served from local web files rather than links to other sites.

includes site

Some sites utilize a global includes directory that was available virtually in the current Central Sites environment. This directory will not be available in the upgraded Central Sites environment.

What to test for:

• Verify full functionality of your site and remove any references to #include virtual = "/includes/…
• If files in the global includes were used previously, please evaluate if they are necessary and use local site copies.

a note about testing

Please note that hard coded URLs may lead you off the site. For example, while testing https://wwwnew.uwyo.edu/sitename, clicking on a link that goes to https://www.uwyo.edu/sitename/page will direct you to the existing production environment and you will no longer be in the new environment. To avoid issues, we recommend relative links to sites and files so they continue to function correctly in development and production. This also avoids having images and other content that reference materials in other environments.

 

 

Timeline

January 23^rd

The new Central Sites environment is available for testing

Websites will be available for testing in the new Central Sites environment. Central sites owners and authors should begin reviewing their sites and code. The current development sites will still be available for authors needing to test changes prior to the upgrade.

January 23^rd  – May 19^th

Website transitions

Once authors and owners are comfortable with their site’s behavior in the new environment, they can request their site be upgrade.  To request your site be upgraded, please submit a ticket.  Once received the web team will work to upgrade your site.  Please see the How to upgrade your site section for more information.

May 19^th

Final Website Conversion

Sites that have not been upgrade will be transitioned automatically.