Thread

I can’t find an answer to this by searching - are you permitted by the license to remove all the ExpressionEngine references, logos, and links from the control panel (e.g. by creating your own CP theme for your client)?

(The intention is not to pass of EE as my own work, but to remove potential sources of confusion for clients - the EE name, copyright statement, User Guide link, etc.)

Quick answer is no. The license explains a little more about what you can and can’t do.

You can however add in anything you want to the Control Panel. A helpful extension in regards to this is the LG Add Sitename extension.

Best wishes,

Mark

Thanks, Mark.

I wonder whether the ‘User Guide’ link is really “copyright and proprietary notices and logos”. Is there any way that can be removed, as it’s really misleading to clients of developers? 😊

Edit - Oops sorry posted incorrectly. You can actually change that link if you like by going to :

Admin->System Preferences->General Configuration->URL to Documentation Directory

Hiya,

I’ll have to leave that one up to EllisLab to answer and I could be wrong but I think that link is in the core files and there isn’t an easy way to turn it off. That said I’m not sure if that is covered by the license or not so a quick e-mail to .(JavaScript must be enabled to view this email address) should get you the answer.

I’m sure one of the moderators will be in here soon enough though to answer that question directly though.

You may not remove the logo or copyright information in the footer of the control panel.  You can change the information presented in the top left corner (safest done through an Extension such as Mark linked).

I wonder how much “confusion” there has been over the past five years with an EE-brand popping up on the Control Panel? I’ve never had it come up in conversation from any of my client sites, some with many, many users.

Still, some kind of CP customization might be nice to have.

I wonder how much “confusion” there has been over the past five years with an EE-brand popping up on the Control Panel? I’ve never had it come up in conversation from any of my client sites, some with many, many users.

You don’t know how stupid my clients are… 😉

😉

I’ve been there, too. Just trying my best to avoid those kind. They don’t pay as much and cost more.

I wonder how much “confusion” there has been over the past five years with an EE-brand popping up on the Control Panel? I’ve never had it come up in conversation from any of my client sites, some with many, many users.

Still, some kind of CP customization might be nice to have.

mmm, a themed control panel would be cool!

I wonder how much “confusion” there has been over the past five years with an EE-brand popping up on the Control Panel? I’ve never had it come up in conversation from any of my client sites, some with many, many users.

Still, some kind of CP customization might be nice to have.

mmm, a themed control panel would be cool!

Have a look here 😉

EE already has the ability to “theme” the control panel, and more customization is on the way for EE 2.0x. I’m thinking more of a custom logo ability for organizations, web site, etc. to dress up the CP. As it is now, logging into the CP for one site is pretty much the same as another sited—you’re not always sure which site it is.

My sarcasm is lost on you both :D

My sarcasm is lost on you both.

Paraphrasing from The Treasure of the Sierra Madre**, circa 1948—“Sarcasm? We don’t need no stinkin’ sarcasm!!”

Or, put another way, “Themes? We don’t need no stinkin’ themes!!”

** and from YouTube.

I’d like more theme capability in EE.

We straight up tell our clients we’re using ExpressionEngine. We use the Site Name extension, clean it up and give it a customized feel, put a few links to our site, a help screencast, etc… but we’re proud of the product and it makes our clients feel the same way.

we’re proud of the product and it makes our clients feel the same way.

I couldn’t agree more. I’d say it’s even a selling point - when the client is aware that there is an enormous and talented worldwide community of EE developers, designers and users it gives them the confidence that their CMS is at least reasonably future-proof and if necessary they can switch from one developer to another without too much fuss.