The user stance455 encountered spacing and functionality issues after updating Discourse, with corrupted assets visible in the dashboard and on the site. After attempting a rebuild via ./launcher rebuild app, the issue persisted. Falco suggested rebuilding again, which resolved the problem. JammyDodger recommended safe mode to diagnose theme or plugin conflicts, though it wasn’t needed here. stance455 confirmed the site is now working and appreciated the advice, noting the usefulness of safe mode for future customization. Canapin asked about causes of asset corruption during rebuilds, highlighting a potential underlying concern.
I can’t access your site link at the minute, but I think it may be a theme component that is interfering with the core code. You could try safe mode to check (The FlyNumber Forum), and if everything works with the theme and plugins disabled then that should help you to be able to pin down which one it is.
I think you may have tried while rebuilding ( its back up now and working OK ) - at the time I did disable the Header links component ( I think that’s what its called ) - I’m not sure there were any other plugins to disable
I think it would have been while you were rebuilding - it works perfectly now. Safe mode is really useful for checking if any custom themes or plugins are the cause of anything, and can often give you a hint as to what might be the issue.
Though in this case I don’t think it would have helped. As @Falco identified, it seems you got some corrupted assets during your first rebuild and needed to do another. I’m glad it’s up and running now though.
That’s what I was thinking as far as any future tinkering I do with discourse. I plan on really getting into the customization features so safe mode will be useful
I’ve had the software since 2013 and it’s aged like fine wine, more refined, with more flavor.