### Button doesn't work / feature stopped working after updating
-
Your browser might have cached an older version of a JavaScript(JS) file which is no longer compatible with the current version of LubeLogger. Clear your browser's cache and retry. Certain web browsers will persist the cache for a period of time despite the cache being cleared, in that case, you should try to navigate to your LubeLogger instance using incognito mode and it will force the cache to be cleared.
+
### Feature(s) Stopped Working After Updating to Latest Version
+
Your browser might have cached an older version of a JavaScript(JS) file which is no longer compatible with the current version of LubeLogger. Try the following steps:
+
+
1. Verify - Try navigating to LubeLogger in Incognito mode.
+
2. If everything functions as expected in Step 1, you have a caching issue.
+
3. Clear your browser's cache or perform a hard reload(hit CTRL+SHIFT+R multiple times on most browsers)
### Can't Send Email via SMTP
Note that for most email providers, you can no longer use your account password to authenticate and must instead generate an app password for LubeLogger to be able to authenticate on your behalf to your email provider's SMTP server.
@@ 12,7 16,9 @@
If you've downloaded the .env file from the GitHub repo, there is an issue with how the file gets formatted when it is downloaded, you will have to copy the contents and re-create one manually on your machine.
### Console shows Authentication Errors
-
Those are purely informational, add a line in your environment variables to prevent information logs from showing up in the console.
+
Those are purely informational, add this line in your environment variables to prevent information logs from showing up in the console.
