cPanel v94 - Error Pages deployed by default with cPanel branding

Andrew Moras shared this idea ago

Open Discussion

Hello,

As of cPanel v94, error pages (400.shtml, 401.shtml, 403.shtml, 404.shtml, 413.shtml, 500.shtml, cp_errordocument.shtml) get automatically deployed to all users that you create on the server. This is a new "feature" and it seems linked to: CPANEL-34417. As a hoster I would like to turn those off, especially because they are not white label and they have links to cPanel.com. I know they can be replaced using a cpanel3-skel setup, however I'd like to have the option to turn them off completely from WHM instead of creating unnecessary files.

I like this idea 0

Replies (6)

Pete Schaefers ●

I 100% agree! This "feature" is a bug for me. At the very least it should be able to be turned off in WHM.

Reply URL

Jason Hitesman ●

Really need a way to disable this. We have custom account creation scripts that clone a git of our development code when we deploy new sites. Now that's failing because public_html is no longer empty. This kind of change with no warning is pretty disruptive - I can change our custom scripts to delete the contents of public_html before cloning...but this kind of sudden change is really disruptive when you get an automatic update over night and suddenly vital operations stop working.

Reply URL

Pete Schaefers ●

cPanel dev team: Read this! (Now, read it again!) Pass this info up your food chain until someone takes notice, and stops this trend! It causes (or potentially causes) real grief to us.

This is similar to the WP management you baked in a while back. (Except there you also hoped to make buck by charging for the functionality that would make it worth even using - ha! - no way!) In that case you did notify us with the option to update to it or not, but WITHOUT full details. (It wasn't ready yet, and IMO you ru$hed it out.) Then when the disappointment hits we were left with manual workarounds/removal to deal with it. Not that it's "too hard" for us, but we simply SHOULD NOT have to deal with stuff like either of these issues.

These practices are counter to your intent - to make it easier and safer - and when you force newer admins to deal with it you frustrate them, and more importantly you send them places that could cause security and/or server issues. (Yes, they should learn to work on the CLI properly, but that doesn't mitigate your error in practices like this.)

URL

G.L. ●

Yeah this should be removed it adds a bunch of files that are unnecessary IMO. I don't even know what they are used for and I don't know how to replace them using a cpanel3-skel setup. They just started appearing after updating my cPanel and creating a new cPanel account.

Reply URL

David M. ●

We need solve this fast!!!, this generate problems and confusions to clients and scripts that have files with same name.

Reply URL

cpaneladam ●

Hey Folks. We're going to return to the previous behavior and allow you to enable the new behavior by toggling a Tweak Setting. The case for tracking this change is CPANEL-34417.

Reply URL

Pete Schaefers ●

*standing applause*

Thank you!

Reply URL