LIst the main cPanel index.html in /etc/cpanelsync.exclude? Dangerous?

[jols]

Hi all,

I have made a rather important change to the <cpanel News="displaynews()"> area of the index.html file by working with the branding editor. This holds a button to a web builder, working with a custom module on the server, and I am unable to use the regular WHM modify news feature for this one.

Anyway, in spite of working within the branding editor for and then clicking the buttons, e.g. "Apply to all accounts..." etc. the recent upgrade wiped this particular change.

So now I am wondering about adding the file and path:

/usr/local/cpanel/base/frontend/x3/branding/index.html

to /etc/cpanelsync.exclude

... and if this would cause any critical issues in the future?

Thanks much.

 

[cPanelPeter]

Hello,

It would be best to download a current copy of the X3 theme, rename it (something like Myx3) and re-import it. Then make your changes to that theme instead. cPanel updates won't update custom themes, and in this way you will always have an up to date x3 theme from cPanel.

 

[jols]

Thanks. Actually I could just clone the theme, make the changes to clone (using the branding interface), thus not hassle with downloading it, etc. Right?

However, the problem with the entire approach is going to be, is there a way to change, en masse, everyone's cPanel theme on a the server?

I know we can put together another account package with the newly cloned theme, but then we would need to go each and every account and manually side-grade them, right?

There's got to be an easier alternative....