If a King Devick web based application is accessible but not performing correctly the best course of action is to attempt a hard refresh of the code running in the background of the webpage as the app may have been updated but your browser may have a cached version of the site. How to do this can vary by browser:
- In Google Chrome press ctrl+F5.
- In Mozilla Firefox press ctrl+shift+F5.
- In Microsoft Edge press F12 to pull up the console menu, press the button highlighted in red below (always refresh from server) and then press F12 again to close the console menu, press F5 to refresh the page and then re-open the console a final time via F12, press the same button again to disable the setting (leaving it enabled will do no direct harm, but may cause frequently accessed pages to load slower than they normally would due to the browser always pulling it directly from the server rather than cache).
If the app is still behaving poorly the next solution would be to clear web history and browser cache. How to do this, once again, varies by browser:
NOTE: This process will log you out of all websites and clear some site specific settings.
- In Google Chrome select the 3 vertical dots button on the top right (pictured below), then highlight history and select history again to open the history page.
Select clear browsing data (highlighted in green below).
- Set the drop down to all time. Select Hosted App data, cookies from other side data, cached images and files, and content settings.
- In Mozilla Firefox Select the 3 lines button in the top right corner of the screen.
- Select Library from the drop down.
- Select History.
- Select Clear recent history.
- Select All time.
- Select the time range to clear option of Everything and hit Clear Now.
- In Microsoft Edge Click the ... button in the top right.
- Select settings and then Choose what to Clear under Clear browsing Data.
- Select at least Cookies and Saved Website Data and Cached Data and Files.
If you are still encountering issues with the web app not loading properly, the next solution would be attempting to use a different browser. We recommend Chrome or Firefox for best performance. If you have more questions or need further assistance reach out to firstname.lastname@example.org.