Preconditions and environment

M2.4.4

php8.1
nginx
Multi website store

Steps to reproduce

1. Setup Multi website store
2. Design Config (Content -> Design -> Config) - Edit Store view level - upload image under Header and save
3. Cache clean
4. Enable Single Store Mode
5. Design Config (Content -> Design -> Config) - Edit for Website - Upload another image under Header and save
6. Header tab expand -> Logo
7. Upload new logo file notdefaultlogo.jpg
8. flush caches
9. reload front end

Expected result

Display the new uploaded logo, notdefaultlogo.jpg

Actual result

Displays default fallback magento svg logo

Additional information

Related to Scope and SingleStoreMode

vendor/magento/module-theme/ViewModel/Block/Html/Header/LogoPathResolver.php
Logo Path Resolver explicitly passes store scope

/** * Return logo image path * * @return string|null */ public function getPath(): ?string { $path = null; $storeLogoPath = $this->scopeConfig->getValue( 'design/header/logo_src', ScopeInterface::SCOPE_STORE ); if ($storeLogoPath !== null) { $path = Logo::UPLOAD_DIR . '/' . $storeLogoPath; } return $path; }

Debugged: 

$this->scopeConfig->getValue('design/header/logo_src','store');
returns: "stores/1/logo_1.png"
$this->scopeConfig->getValue('design/header/logo_src','website');
returns: "websites/1/notdefaultlogo.jpg"
$this->scopeConfig->getValue('design/header/logo_src');
returns: null

I did not mark as S0 severity, but I believe it is considering it is site identity(logo) and an admin user can not resolve this without disabling single store mode - which is not a real resolution to the issue.

Additionally it looks like single store mode and scope has been an ongoing issue across many items:
#22344

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.