Make WordPress Core

Opened 5 years ago

Closed 2 years ago

#54842 closed enhancement (reported-upstream)

inconsistent handling of align settings on Pages / Templates

Reported by: tinomueller Owned by:
Priority: normal Milestone:
Component: Editor Version:
Severity: normal Keywords:
Cc: Focuses: ui, administration, template

Description

Maybe i'm not getting the full concept behind but it feels a bit clumsy to setup the alignment/wide settings for the blocks on pages/posts or templates/template-parts.

Example:

  • setup a header template using Gutenberg on a normal page
  • - create Cover block with background color
  • - insert a simple text
  • - set alignment to full-width
  • - copy the cover and insert it into a template-part

Now, if i want to edit the template part the alignment/sizing option is not available anymore. (see screenshots)

Attachments (2)

template-editor-screen.PNG (18.7 KB ) - added by tinomueller 5 years ago.
template editor
page-editor-screen.png (22.6 KB ) - added by tinomueller 5 years ago.
page editor

Download all attachments as: .zip

Change History (6)

@tinomueller
5 years ago

template editor

@tinomueller
5 years ago

page editor

#1 @tinomueller
5 years ago

  • Summary inconsitent handling of align settings on Pages / Templatesinconsistent handling of align settings on Pages / Templates

#2 @tinomueller
5 years ago

  • Component GeneralThemes

#3 @tinomueller
5 years ago

  • Type defect (bug)enhancement

#4 @poena
2 years ago

  • Component ThemesEditor
  • Milestone Awaiting Review
  • Resolutionreported-upstream
  • Status newclosed

Hi @tinomueller.
You are not alone in expressing this, it is a frequently asked question about working with blocks in the different editors.

Blocks have alignment options depending on their parent. In the Site Editor, the blocks need to be placed inside a container like a group block with specific settings enabled.
In the Post editor, this is not needed, because the blocks are, in a sense, already inside a post content block.

This is a known issue, the contributors who are working on the editor have not found the best way to solve it yet.

I am closing this ticket as a duplicate of an issue reported in the Gutenberg GitHub repository, because there are more discussions and a better explanation there:
https://github.com/WordPress/gutenberg/issues/55799

Note: See TracTickets for help on using tickets.