v6 to v7 upgrade - don't get new css files

[tabacitu]

I've just upgraded a website from v6 to v7 (again), so I go through the upgrade process. It's taken EXTREMELY little time, and I'm very happy about that. But... upgraders don't get the new CSS files.

Our docs say this:

But my admin panel hasn't actually received the extra skins in the config file, so I can uncomment them. I suggest we add those lines (commented out)... if it's easy? Alternatively, we should edit the docs here to tell the user to add one/more of these CSS files there if they want:

        base_path('vendor/backpack/theme-tabler/resources/assets/css/skins/backpack-color-palette.css'),
        base_path('vendor/backpack/theme-tabler/resources/assets/css/skins/glass.css'),
        base_path('vendor/backpack/theme-tabler/resources/assets/css/skins/vertical-lines-background.css'),
        base_path('vendor/backpack/theme-tabler/resources/assets/css/skins/pinstripe-background.css'),
        base_path('vendor/backpack/theme-tabler/resources/assets/css/skins/paper-background.css'),
        base_path('vendor/backpack/theme-tabler/resources/assets/css/skins/dotted-background.css'),
        base_path('vendor/backpack/theme-tabler/resources/assets/css/skins/fuzzy-background.css'),

But a bigger problem might be that I still have these 2 files in my config, right? And I should be instructed what to do about them:

I've removed those files and everything works GREAT for me... but other devs might have changed them. So we should adapt the docs for this.

[backpack-ai-bot]

CrawlChat Answer:

This appears to be a feature request or bug report about the v6 to v7 upgrade process, rather than a support question. Based on the issue you've raised:

The Problem: When upgrading from v6 to v7, users don't automatically receive the new CSS skin files in their config, and may still have outdated CSS file references that need to be removed.

Your Suggestions:

1. Add new CSS skin paths as commented-out lines in the config file for easy uncomment
2. Update docs to explicitly instruct users on adding new skin CSS files if desired
3. Document which old CSS files should be removed during upgrade

Recommendations:

• Report this through the proper Backpack channels (GitHub issues, forums, or support) so the team can either:
  • Auto-publish the commented skin paths during upgrade
  • Update the upgrade documentation with clear migration steps for CSS files
  • Create a Basset cache clear explanation for assets that may need removal

The cache clearing commands mentioned in the upgrade guide (php artisan basset:clear) should help, but explicit documentation about outdated CSS file removal would be valuable for developers migrating from v6.

Would you like guidance on reporting this as a feature request to the Backpack team?

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

Upgrade Guide :: 7.x Docs :: Backpack for Laravel
New basset() helper (yes, helper) :: Backpack for Laravel
How to add WebAuthn Passkeys To Backpack For Laravel Admin Panel :: Backpack for Laravel
FAQs for the admin UI :: 7.x Docs :: Backpack for Laravel
[Bug] Call to undefined function views_path() WHEN STTING NEW CUSTOM THEME