Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cover Block: Settings Unavailable When Using Featured Image in Site Editor #100142

Open
pauloeaquino opened this issue Feb 21, 2025 · 1 comment
Labels
[Feature] Full Site Editor The site editor. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. Groundskeeping Issues handled through Dotcom Groundskeeping rotations [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Auto-allocated [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. [Status] Escalated to Product Ambassadors [Status] 3rd Party Fix Needed A fix from a 3rd party is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@pauloeaquino
Copy link

Context and steps to reproduce

Issue Description

When a Cover block is set to use the Featured Image in the Site Editor, the block settings panel does not display options such as:

  • Fixed Background (parallax effect)
  • Resolution (Full Size, etc.)

This prevents users from applying these settings when designing page templates.

CleanShot.2025-02-21.at.20.53.40.mp4

Expected Behavior

The Cover block settings (e.g., Fixed Background, Resolution) should be available whether or not the block is set to use the Featured Image. This would allow users to configure their designs without needing a workaround.

Themes Tested On

  • Assembler
  • Twenty Twenty-Five
  • Twenty Twenty-Four

Additional Context

This issue impacts users designing page templates in the Site Editor and prevents full customization of Featured Image-based Cover blocks.

Site owner impact

More than 60% of the total website/platform users

Severity

Moderate

What other impact(s) does this issue have?

No response

If a workaround is available, please outline it here.

Workaround

Users can bypass this issue using the following steps:

  1. Add a Cover block in the Site Editor.
  2. Select any image from the Media Library or upload one manually.
  3. Adjust settings as needed (Fixed Background, Resolution: Full Size, etc.).
  4. Click Save.
  5. Click Replace in the Cover block settings.
  6. Select "Use Featured Image" instead of a manually chosen image.
  7. Click Save again.

This workaround successfully applies the desired settings to the Cover block, but the settings panel remains unavailable while the block is set to "Use Featured Image."

Observation in Code Editor

Before applying the workaround, when the Cover block is initially set to use the Featured Image, the corresponding block code lacks key attributes such as hasParallax and sizeSlug:

{
  "useFeaturedImage": true,
  "dimRatio": 0,
  "customOverlayColor": "#FFF",
  "layout": { "type": "constrained" }
}

After completing the workaround and re-selecting the Featured Image, the block code does retain the missing settings:

{
  "useFeaturedImage": true,
  "hasParallax": true,
  "dimRatio": 0,
  "customOverlayColor": "#FFF",
  "isUserOverlayColor": false,
  "isDark": false,
  "sizeSlug": "full",
  "layout": { "type": "constrained" }
}

This suggests that the settings are supported, but the UI does not expose them when the block is set to use the Featured Image by default.

Platform

Simple, Atomic

@pauloeaquino pauloeaquino added [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Feature] Full Site Editor The site editor. [Product] WordPress.com All features accessible on and related to WordPress.com. [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Feb 21, 2025
@github-actions github-actions bot added [Status] Escalated to Product Ambassadors [Pri] High Address as soon as possible after BLOCKER issues labels Feb 21, 2025
@Robertght
Copy link

Thank you @pauloeaquino !

It looks like this was already reported in core WordPress/gutenberg#69179

The good news is that there's also a PR available for it here: WordPress/gutenberg#69178

@Robertght Robertght added [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels Feb 21, 2025
@matticbot matticbot moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Feb 21, 2025
@lsl lsl moved this from Triaged to Needs Core/3rd Party Fix in Automattic Prioritization: The One Board ™ Feb 24, 2025
@lsl lsl added the Groundskeeping Issues handled through Dotcom Groundskeeping rotations label Feb 24, 2025
@matticbot matticbot moved this from Needs Core/3rd Party Fix to Triaged in Automattic Prioritization: The One Board ™ Feb 24, 2025
@inaikem inaikem added the [Status] 3rd Party Fix Needed A fix from a 3rd party is required to resolve this issue. label Feb 24, 2025
@inaikem inaikem moved this from Needs Triage to Needs Core/3rd Party Fix in Automattic Prioritization: The One Board ™ Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Full Site Editor The site editor. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. Groundskeeping Issues handled through Dotcom Groundskeeping rotations [Pri] High Address as soon as possible after BLOCKER issues [Product] WordPress.com All features accessible on and related to WordPress.com. [Status] Auto-allocated [Status] Core Fix Needed A fix within the Core WordPress or Gutenberg project is required to resolve this issue. [Status] Escalated to Product Ambassadors [Status] 3rd Party Fix Needed A fix from a 3rd party is required to resolve this issue. Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Status: Needs Core/3rd Party Fix
Development

No branches or pull requests

5 participants