Disappeared sidebar after upgrade 0.49 - 0.57

[thclark]

What version of Unfold are you using?

Upgraded to 0.57

What version of Django are you using?

5.0

What browser are you using?

Chrome

Did you checked changelog/commit history, if the bug is not already fixed?

Yes

Did you searched other issues, if the bug is not already fixed?

No relevant issues

Did you checked documentation?

Yes, checked the sidebar settings.

Are you able to replicate the bug in the demo site?

No, the sidebar is present in the demo app

Describe your issue

Video here

I upgraded from 0.49 to 0.57 and found that the sidebar has disappeared, and the formatting on the login page has died.

• I ran collectstatic to make sure I'm up to date
• I looked at the change history for all releases in that range, and there are no breaking changes advertised.
• As we have a custom dashboard, I dropped in the template for the default example dashboard to make sure that wasn't it
• App is behaving as if it's decided all screens are mobile.

[lukasvinclav]

Hey Tom, are you using custom project level stylesheet where you are generating your own Tailwind classes which you are then mapping to UNFOLD["STYLES"] in settings.py? If yes, try to comment this line.

[thclark]

Update: the breakage is between 0.55 and 0.56

Yes! Commenting out the styles has brought the sidebar back. I guess I should go back through the guide for generating custom styles? Is there a way you suggest for preventing this from breaking in the future (eg do you tend to automate this in CI or similar?).

[thclark]

@lukasvinclav I just read this with dismay! Being able to use tailwind to style our admin is/was a massive benefit of unfold!!! Is it still possible to do it the old way?

It'd be worth adding a ⚠ 💥 note about the breaking change to the release notes for 0.56, this is an absolute doozy of a change for anyone using tailwind selectors not present in unfold itself!

[lukasvinclav]

@lukasvinclav I just read this with dismay! Being able to use tailwind to style our admin is/was a massive benefit of unfold!!! Is it still possible to do it the old way?

Of course it is still possible to compile your own Tailwind styles and add them into project. Your current tailwind.config.js has to be migrated to new Tailwind 4 syntax. I will update the docs in the near future.

It'd be worth adding a ⚠ 💥 note about the breaking change to the release notes for 0.56, this is an absolute doozy of a change for anyone using tailwind selectors not present in unfold itself!

Here you are right, it should be marked as breaking change. I already marked the PR as breaking with explanation mark in commit message but as I use custom changelog generator, it was for some reason ignored. This is another thing which I have to take a look at.

[thclark]

Thanks @lukasvinclav , I appreciate the help!!

[lukasvinclav]

@thclark I just updated the docs for Tailwind 4. Did some testing and it worked but as always everything depends. I don't know how exactly your project looks like so there might be issues. If you need to customize only few things in CSS, I recommend writing raw CSS.

https://unfoldadmin.com/docs/styles-scripts/customizing-tailwind/

PS: if you wrote tons of custom Tailwind 3 code you can use the upgrade tool: https://tailwindcss.com/docs/upgrade-guide#using-the-upgrade-tool

[lukasvinclav]

@thclark okay, so I found the issue in semantic release and I fixed the CHANGELOG with proper marking of breaking changes.

In your situation, I recommend pinning to 0.55, which should work as expected, and when you have more time looking at the Tailwind 4 migration. In case you have plenty of custom Tailwind classes, it can take a while to migrate but it would be a shame not to update as I'm preparing bunch of new visual changes in the future.

[thclark]

Thanks @lukasvinclav will do.