0.8.11 Release
Merge Request Guidelines
- Please fill this form out to the best of your ability.
- Follow the principle of "One Merge Request, One Concern"
- Merge Requests must be complete in total.
- Contributed Code must be universal in scope, ie: Able to be used for all installs / install environments.
Description
Version Update Release 0.8.11
Motivation and Context
- OSP-Core: Fixed Topic URL link link to point to /topic/ not /topics on DarkCow Live Page #421 (closed) - 348f96cd
- OSP-Core: Fixed an issue where System Settings Cached DB Calls were not invalidating properly #422 (closed) -2417a748
- OSP-Installer: Fixed an issue where osp-config.sh was not performing the correct update procedure due to duplicate entries #419 (closed) - 7ed83d77
How Has This Been Tested?
Tested on Demo site
Screenshots (if appropriate):
Types of changes
-
Bug fix (non-breaking change which fixes an issue) -
New feature (non-breaking change which adds functionality) -
Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
-
My code follows the code style of this project. -
Merge Request Follows the Merge Request Guidelines -
My change requires a change to the documentation. -
I have updated the documentation accordingly.