Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Webtools.uconn.edu has been sunset. K9 Olympics website used to pull assets (JS/CSS/images) from a global theme, residing on Webtools. 

Below, you will find all the steps taken in order to not only address the issue at hand, but rather using this as an opportunity to also bringing the project up to code.

Current state (PROD)


Troubleshooting

Server Logs


As can be seen, server logs were of no help!

Console Logs


As can be seen, there are missing assets (JS / CSS / etc.) — this was a dead giveaway as to what the problem was...

Sources

Looking at the source code, there are a bunch of references to Webtools:


Yet another confirmation was provided by looking at the parent CSS file "screen.css" (which was sourced locally, already) — this is the file that imported all the other CSS files from webtools.

Solution

  • Check-in the code; this is for multiple reasons
    • Version control is non-existent — not following the standard
    • See exactly what changes were made (especially over time) 
    • Other developers can access the latest version, readily
    • etc.
  • Hunt down the missing assets
    • Either by reaching out to previous owner of Webtools or
    • Grab a cached copy on the interwebs — I chose to to this!
  • Modify the code
    • All files that are referencing Webtools (biggest one being screen.css, remember)
  • Test
    • We do not have a DEV or TEST environment for K9-Olympics website...
      • However, since the project is simply HTML(+CSS/JS/etc.) + PHP, I do have a WAMP stack running on my local machine... so we will rely on that to get the testing done
  • Commit code
  • Push the code onto Server

 — AT THIS POINT, WE HAVE A WORKING K-9 Olympics WEBSITE! — 

  • Bring it up to code
    • Fix existing code
      • Inspecting the project, I noticed that
        • There are many files within the project structure that are just unnecessary and is just bloating the project
        • The code itself is
    • Test (using the same method, as above)
    • Push to PROD

Solution Walkthrough

Check-in the code

Hunting down missing assets

All missing assets have been tracked down

Modifying the code

Each affected file was modified to reference resources locally.

Testing

Finally, the modified project was thoroughly tested on the local WAMP stack and no problems were visible


PageResult
Landing / Home Page

About Page

Contact Page

Event Info Page

Application Info Page

Photos Page

Committing modified code

Pushing the code to PROD

Prior to extracting the fixed code, let's verify the structure:

unzip -l k9_fixed-no-git-dir.zip

Looks good! Let's extract and refresh the K9-Olympics Website!

NOTE: we have made a backup of the original... so if the fix does not go as planned, we can quickly revert to how it was!

Looks like the old site is still cached... after doing a hard refresh (CTRL + F5), we see:

ALL GOOD! (for now!)

  • No labels