Back to Changelog
Panel Backend
v1.0.511
Databases can be created again on accounts without a plan, and a white-labelled panel no longer falls back to Panelica logos.
Improvement
1- While white-labelling is on, the panel appearance is decided once in Panel Settings → Branding and applies to every account: theme changes requested by other accounts are refused. Deploy the matching panel-frontend version alongside this one, which hides the theme customizer from every account except root.
Bug Fixes
2- Creating a database returned an empty HTTP 500 for any account with no plan assigned - typically an account created by a migration. The panel read the plan's database limit without checking that a plan exists, so the request crashed instead of skipping a limit that is not there, and the reply carried no message explaining why. Adopting an already existing database failed the same way.
- On a white-labelled panel, the logo and favicon fell back to Panelica's own files whenever the operator had not uploaded their own. Because that fallback is never empty, every "has a logo been set?" check saw one and rendered it - so our logo appeared on the login screen, the sidebar and the header of a reseller's own product. These fields now come back empty and the interface shows the operator's company name. A standard Panelica installation is unchanged.