Why is custom.css overwritten on update?

The customization doc http://developers.whmcs.com/themes/css-styling/ says to make css changes to custom.css and that "This file is included after styles.css allowing you to override any of the CSS defined within it and will not be affected by future updates to the WHMCS software." Am I misreading this or is there an error in the documentation or update process?

https://forum.whmcs.com/showthread.php?125882-WHMCS-v7-1-2-upgrade-bug

the updater assumes that if you've modified custom.css, you've also renamed the template to something other than "Six" - which in my opinion is stupid... I know users that are using custom.css, nav hooks and language overrides, but haven't changed any of the templates - they're happy to keep the template called "Six"... but the updater ignores that and tries to wipe the custom.css file on update (though it at least warns you).

best thing you can do is either make a backup of custom.css before updating, or rename the template from "Six" to something else - that would prevent the updater from modifying it, but would also mean you'd have to update the templates manually.

it's ridiculous either way, but I wouldn't hold your breath waiting for WHMCS to change their policy on this.

https://forum.whmcs.com/showthread.php?125882-WHMCS-v7-1-2-upgrade-bug

 

the updater assumes that if you've modified custom.css, you've also renamed the template to something other than "Six" - which in my opinion is stupid... I know users that are using custom.css, nav hooks and language overrides, but haven't changed any of the templates - they're happy to keep the template called "Six"... but the updater ignores that and tries to wipe the custom.css file on update (though it at least warns you).

 

best thing you can do is either make a backup of custom.css before updating, or rename the template from "Six" to something else - that would prevent the updater from modifying it, but would also mean you'd have to update the templates manually.

 

it's ridiculous either way, but I wouldn't hold your breath waiting for WHMCS to change their policy on this.

Thanks for that link. Why would I want to create a copy of the six template and need to keep it in sync with changes in the automated update process? Why would you bother to have a custom.css file if it gets overwritten anyway? This automated update process is awfully manual.

Thanks for that link. Why would I want to create a copy of the six template and need to keep it in sync with changes in the automated update process?

https://developers.whmcs.com/themes/getting-started/

The default template that ships with WHMCS 6.0 and later is called the Six theme.

Before you begin customising it for your needs, the first step is to create your own copy of the template. This ensures your customisations are not lost when updating.

Why would you bother to have a custom.css file if it gets overwritten anyway? This automated update process is awfully manual.

logically, it shouldn't get overwritten if the file already exists... but far too often, logic and WHMCS don't go together.

The more popular a suggestion becomes, the more likely our development team is to consider it for potential inclusion in a future release!

with one vote after 11 months ??

i'll pass and create my own solution.

This is like the child's template in WordPress.

Until keep the template css changes after updating.