Appsettings.json and custom login page

Questions
1

Moved to Umbraco 16 and the settings to customize the login screen seem to not take affect anymore.

appsettings.json
“LoginLogoImage”: “/media/…”,
“LoginLogoImageAlternative”: “/media/…”,
“LoginBackgroundImage”: “/media/…”,

login page
<umb-auth-layout background-image=“/umbraco/management/api/v1/security/back-office/graphics/login-background” logo-image=“/umbraco/management/api/v1/security/back-office/graphics/login-logo” logo-image-alternative=“/umbraco/management/api/v1/security/back-office/graphics/login-logo-alternative”…

those values don’t change anymore based off the setting in appsettings.json

previously those values were inserted like:

<umb-auth-layout background-image=“/media/5b3pl5ot/login-banner.jpg” logo-image=“/media/5cije2jp/logo-color.svg” logo-image-alternative=“/media/5cije2jp/logo-color-small.svg” …

2

They still work, I use them in every project.

  • Make sure the settings are correctly nested in the config as detailed in the documentation, in Umbraco:CMS:Content.
  • The LoginBackgroundImage and LoginLogoImage and LoginLogoImageAlternative are according to the documentation “relative to the wwwroot/umbraco path“. So in other words: your images need to be in wwwroot/umbraco or a subfolder to work.

This is my login screen in Umbraco 16.3.4:

image
image1618×979 132 KB

The appSettings.json:

{
	"$schema": "appsettings-schema.json",
	"Umbraco": {
		"CMS": {
			...
			"Content": {
				...
				"LoginBackgroundImage": "assets/img/proudnerds-background.jpg",
				"LoginLogoImage": "assets/img/application/Proud-Nerds-logo-RGB-wit.svg"
				...
			}
		}
	}
}

The images are located here:

image
image318×137 2.04 KB

2 Likes
3

My paths are all relative, it’s the same format as several other sites running <v16. Only thing I can see is that the three images (/umbraco/management/api/v1/security/back-office/graphics/login-logo etc…) come back as a 404. Not sure if that causes this or not.

if i move the images to wwwroot/umbraco/login_images/… they work fine but in older versions I could just target the media folder. I guess more of a feature request really, that and just putting the images in the plugin’s folder

4

Looks like here’s your blocker…