Request for Upgrade Guide (v8.2.0 → v8.3.1, Theme Demo16)
Hello,
Could someone please provide a guide on how to safely upgrade our codebase to the newer version?
Our application is currently built on Laravel 9, v8.2.0 using Theme Demo16, and we would like to upgrade to v8.3.1.
We’d like to understand:
- What breaking changes to expect during this upgrade
- What adjustments will be required in our existing Demo16 code
- Best practices to ensure a smooth transition
I came across a related ticket that outlines some of the changes:
Upgrade from 8.1.9 to 8.3.1 – Keenthemes
Key notes from that thread:
Menu Changes
config/menu.phphas been removed.- Menus are now defined in Blade templates:
resources/views/layout/partials/sidebar-layout/sidebar/_menu.blade.php
- The structure now uses Laravel’s route-based approach:
- Direct Blade rendering
- Route-based active states (
request()->routeIs()) - Icon helpers (
getIcon())
- Configuration handled via:
app/Core/Bootstrap/BootstrapDefault.phpapp/Core/Theme.php
Build/JavaScript Conflicts
- Conflicts can occur from duplicate script includes.
- Ensure
webpack.mix.jsisn’t including both compiled and source files.
Recommended steps:
npm cache clean --force
rm -rf node_modules package-lock.json
rm -rf public/assets/*
npm install
npm run dev
- Verify only one validation library is active.
- Ensure files aren’t being loaded from both
public/assets/and source.
Any official documentation, migration notes, or upgrade best practices specifically for Laravel 9, Demo16 would be greatly appreciated.
Thank you!
Replies (2)
Hi Stefano madrigal
Sorry for the delay. Could you please clarify which Laravel version you are using now? Do you find the laravel is in the starterkits folder? I need to know if the Laravel is part of the released Metronic starterkits.
Thanks