Updating a-blog cms from 3.0 to 3.1? Then Clear the Cache
This article is about “Clearing the Cache if the Admin Menu is Incorrect After Updating a-blog cms from Version 3.0 to 3.1.”
Recently, I updated a site that uses "a-blog cms" from version 3.0 to 3.1.
After overwriting license.php with the latest version and updating the CMS, I noticed that the left side navigation in the admin panel looked different.
The Config menu was missing.
I thought something was wrong, so I cleared all the cache from the Cache Clear option in the Dashboard, and the issue was resolved.
The menu for the new Audit Log feature added in version 3.1 also appeared.
In this case, I suspect the Config Cache might have been the issue. But I think clearing the cache is a good first step if there are any odd behaviors on the frontend or backend during major or minor version updates.
Menu before clearing the cache after the update.
The config is not displayed.
Clear the cache in the CMS admin panel.
The menu is now displaying correctly.
