Problem/Motivation
Belgrade is increasingly used as a focused checkout theme, often activated only on Commerce checkout routes via Theme Switcher or recipe-based setups (e.g., Commerce Recipe: Focused Checkout).
In this mode, Belgrade is not the default site theme and may not have access to the same assumptions as when it is the primary front-end theme. Some templates, libraries, and settings rely on global configuration that isn’t present when Belgrade is used as a secondary theme.
Resulting issues:
- Checkout pages may show a different logo than the rest of the site.
- Site builders must duplicate logo configuration manually.
- There is no clean region to place a branding block if a site wants consistent logo/brand presentation.
- Recipes and theme-switcher setups cannot guarantee consistent branding without custom overrides.
Issue fork belgrade-3558654
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
zaporylieComment #5
majmunbog commentedI've added a theme setting so Belgrade’s focused checkout can optionally reuse the default site logo instead of its own. Updated the preprocess logic to honor that toggle, falling back to Belgrade’s logo when the option is off or the default theme lacks a logo.
Comment #6
zaporylieI tested this using the recipe mentioned in the issue summary. With the new setting enabled, the logo is always inherited from the default theme—whether it’s the theme’s built-in logo or a custom one.
However, when I disable this option and set a custom logo in the Belgrade theme settings (with Belgrade still acting as the secondary theme), the logo does not appear on the focused checkout pages.
I also checked the 3.x HEAD, and it looks like this isn’t a regression introduced by this MR but rather an existing bug in Focused Checkout.
Comment #7
zaporylieSince this is not an issue with this MR, I am moving this to RTBC. I run a few more tests with the focused checkout, and the issue I mentioned in #6 seems to only affect custom logos that are uploaded in a non-SVG format.
Surprisingly, non-SVG logos uploaded to the default theme are correctly inherited by Belgrade, when it is used as a secondary theme for the focused checkout.
Comment #8
zaporylieCreated a follow-up issue in #3559050: Non-SVG logo doesn't show in focused checkout
Comment #9
majmunbog commentedI have already made a fix in this MR. Could you please review this again?
Inline SVG logo settings were causing the issue.
Comment #10
zaporylieAll good now.
Comment #12
majmunbog commentedComment #13
zaporylieThanks