Homepage cover image not displayed with "Landing" header style (Ghost 6.10.3, Theme default source (v1.5.0)

[Tiritibambix]

Issue Summary

When using Ghost 6.10.3 with the default theme Source (v1.5.0) (via ghost:latest Docker image), the homepage cover image fails to display if the "header_style" is set to "Landing", even though the "use_publication_cover_as_background" option is enabled. The image only appears when the header style is switched to "Search".

Steps to Reproduce

1. Deploy Ghost 6.10.3 using Docker (see docker-compose.yml below).

2. In Ghost Admin, set:

• header_style = "Landing"
• use_publication_cover_as_background = enabled

3. Upload a publication cover image.

4. Visit the homepage: the cover image does not appear.

5. Change header_style to "Search": the cover image appears as expected.

Ghost Version

6.10.3 (ghost:latest Docker image)

Node.js Version

v22.21.1

How did you install Ghost?

Docker Debian

Database type

MySQL 8

Browser & OS version

Win11, Librewolf, Chromium

Relevant log / error output

Nothing relevant in the logs. Here is my docker-compose, deployed through Portainer:


version: "3"

services:
  ghost:
    image: ghost:latest
    restart: on-failure
    environment:
      - database__client=mysql
      - database__connection__host=db
      - database__connection__user=ghost
      - database__connection__password=password
      - database__connection__database=ghost
      - url=https://my.ghost.domain
    volumes:
      - /srv/Files/Ghost/ghost-content:/var/lib/ghost/content
    ports:
      - "2368:2368"
    depends_on:
      - db

  db:
    image: mysql:8.0
    restart: on-failure
    volumes:
      - /srv/Files/Ghost/mysql-data:/var/lib/mysql
    environment:
      - MYSQL_USER=ghost
      - MYSQL_DATABASE=ghost
      - MYSQL_PASSWORD=PaSsWoRd!!!!!
      - MYSQL_ROOT_PASSWORD=password

Code of Conduct

• I agree to be friendly and polite to people in this repository

[cathysarisky]

That header image doesn't appear if you're signed in in the "Landing" layout, because the whole section isn't rendered. Users sometimes find that behavior surprising, but it isn't really a bug -- it's as the theme dev intended.