In V7 these were my instructions to change the logo on the login page:-
Logo
Images are in: umbraco\assets\img\application
and the login view is in: umbraco\Views\common\dialogs\login.html
<img ng-src="assets/img/application/logo.png" ng-srcset="assets/img/application/[email protected] 2x, assets/img/application/[email protected] 3x">
Unfortunately the login view is now empty in V8 and if I search for <img src="assets/img/application/umbraco_logo_white.svg"> or just the file in the whole solution, any file type, I get nothing.
So, how do we change the login page logo without having to rename the logo you want to use as umbraco_logo_white.svg?
If I'd have included the Umbraco folder in the project the search would have told me it's in \umbraco\views\components\application\umb-login.html !
Having changed the path to the image I want, I can't get it to show. I've touched web.config, bumped the clientdependency number, restarted the app pool, flushed all caches and rebuilt indexes but the Umbraco logo still stands proud. How can I get rid of it? lol In the browser dev tools if I replace the umbraco logo path with mine the new logo shows up fine so I know the path is correct in code, just can't get it to show.
Found a further reference at \Umbraco\Js\umbraco.directives.js Ln: 635 which I also changed, restarted site, etc as before but still get the Umbraco logo on the login page instead of my client's.
If I rename umbraco_logo_white.svg then it disappears immediately. Somewhere some code is caching or forcing it to be shown over and above the two places I've already changed it.
If I were you I would either redirect the url /assets/img/application/umbraco_logo_white.svg to the location of my own logo using rewrite rules in web.config, or add some CSS to work with the logo through a package.manifest file.
The css file is then referenced in a package.manifest file in a folder in App_Plugins like so:
{
// array of files we want to inject into the application
"css": [
"~/App_Plugins/Ecreo.Branding/branding.css"
]
}
With this, I get my own logo next to the Umbraco logo (the first CSS rule), and a custom background image automatically tinted in Umbracos colours, just by adding the image as /App_Plugins/Ecreo.Branding/login.jpg
It's not that streamlined if there's code being downloaded that's not used ;)
The login page isn't really something I'd thought of as having to be super quick and efficient. It's not like it's going to be hit concurrently a thousand times a minute.
Rebranding is a reasonable thing to be able to do so it should be either easy (obvious) or documented. I'll see about raising an issue on GitHub.
Why would you have thousands of editors logging into the same site at once, like you might well have thousands of actual visitors trying to open any client page on a site at once? I don't get it at all.
Whenever Umbraco boots up and goes into upgrade mode (because the Umbraco.Core.ConfigurationStatus application setting is empty/different than the assembly version or migrations are missing/not run), every client page will be redirected to the Umbraco back-office login page!
An administrator needs to login and accept the upgrade, but untill then: all website visitors will see the login screen...
Companies don't care nor want to know about the pipework. All they want to see is their own logo so they get that warm and cosy feeling. The IT dept know it's Umbraco, sales and marketing couldn't care less.
Implemented the redirect as Søren suggested, worked a treat thanks. Code is:-
<rule name="Redirects umbraco logo to client's logo on login page" stopProcessing="true">
<match url=".*" />
<conditions>
<add input="{REQUEST_URI}" pattern="/assets/img/application/umbraco_logo_white.svg$" />
</conditions>
<action type="Redirect" url="/images/logo/company_logo.png" appendQueryString="false" redirectType="Permanent" />
</rule>
How to change the Umbraco logo on the login page
Umb V8.6.0
In V7 these were my instructions to change the logo on the login page:-
Unfortunately the login view is now empty in V8 and if I search for
<img src="assets/img/application/umbraco_logo_white.svg">
or just the file in the whole solution, any file type, I get nothing.So, how do we change the login page logo without having to rename the logo you want to use as
umbraco_logo_white.svg
?Thanks,
/ Craig
If I'd have included the Umbraco folder in the project the search would have told me it's in \umbraco\views\components\application\umb-login.html !
Having changed the path to the image I want, I can't get it to show. I've touched web.config, bumped the clientdependency number, restarted the app pool, flushed all caches and rebuilt indexes but the Umbraco logo still stands proud. How can I get rid of it? lol In the browser dev tools if I replace the umbraco logo path with mine the new logo shows up fine so I know the path is correct in code, just can't get it to show.
Any advice anyone?
TIA
/ Craig
Found a further reference at \Umbraco\Js\umbraco.directives.js Ln: 635 which I also changed, restarted site, etc as before but still get the Umbraco logo on the login page instead of my client's.
If I rename
umbraco_logo_white.svg
then it disappears immediately. Somewhere some code is caching or forcing it to be shown over and above the two places I've already changed it./Craig
Hi Craig
If I were you I would either redirect the url
/assets/img/application/umbraco_logo_white.svg
to the location of my own logo using rewrite rules in web.config, or add some CSS to work with the logo through a package.manifest file.This is what I have in my baseline project:
The css file is then referenced in a package.manifest file in a folder in App_Plugins like so:
With this, I get my own logo next to the Umbraco logo (the first CSS rule), and a custom background image automatically tinted in Umbracos colours, just by adding the image as /App_Plugins/Ecreo.Branding/login.jpg
Thanks Søren, I'll give it a try.
They've sure made it awkward. Used to be a doddle lol
/Craig
They've made the backoffice load a lot faster by inlining much of the html in the js bundle, that is what they've made :)
It's not that streamlined if there's code being downloaded that's not used ;)
The login page isn't really something I'd thought of as having to be super quick and efficient. It's not like it's going to be hit concurrently a thousand times a minute.
Rebranding is a reasonable thing to be able to do so it should be either easy (obvious) or documented. I'll see about raising an issue on GitHub.
/ Craig
Celebrate and embrace the "Umbraco-ness"
No need to hide it :-D
You'd be amazed at how many people might need to load the login page, as Umbraco redirects everyone to this page when it's in upgrade mode!
You'll have to explain that one to me Ronald.
Why would you have thousands of editors logging into the same site at once, like you might well have thousands of actual visitors trying to open any client page on a site at once? I don't get it at all.
/ Craig
Whenever Umbraco boots up and goes into upgrade mode (because the
Umbraco.Core.ConfigurationStatus
application setting is empty/different than the assembly version or migrations are missing/not run), every client page will be redirected to the Umbraco back-office login page!An administrator needs to login and accept the upgrade, but untill then: all website visitors will see the login screen...
Ok, but surely that's a bit of an edge case.
Anyway, we have strayed away from the post's original intent which has been satisfied. Thanks to all contributors ;)
/Craig
Companies don't care nor want to know about the pipework. All they want to see is their own logo so they get that warm and cosy feeling. The IT dept know it's Umbraco, sales and marketing couldn't care less.
Implemented the redirect as Søren suggested, worked a treat thanks. Code is:-
hahaha cool!
Hope you sent in that invoice then :-)
I know this is old, but here is how to change the logo and background image of the login page.
Umbraco > assets > img
folder.config
folder, openumbracoSettings.config
.<loginBackgroundImage>
and change the filename to the image name you pasted.<loginLogoImage>
I hope this helps.
is working on a reply...