Problem/Motivation

Currently the Reusable Blocks view is using the default formatter for the body field, which causes a weird issue, the first time you create a Reusable block it renders properly in that view, but after edit the reusable block is shown as HTML code.

Steps to reproduce

  • Create a reusable block.
  • Check the block looking good in the reusable blocks view.
  • Go to the content and edit the reusable block.
  • Check the block is not looking good in the reusable blocks view.

Proposed resolution

By changing the formatter to Gutenberg the problem disappear.

Issue fork gutenberg-3284050

Command icon 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

jidrone created an issue. See original summary.

jidrone’s picture

Status: Active » Needs review

PR created and moved to needs review.

deepalij’s picture

Status: Needs review » Needs work
StatusFileSize
new185.17 KB
new221.35 KB

Applied merge request !31 from #2.
Applied successfully but with the warning as shown below:

Checking patch config/install/views.view.reusable_blocks.yml...
Checking patch gutenberg.install...
31.patch:77: new blank line at EOF.
+
Applied patch config/install/views.view.reusable_blocks.yml cleanly.
Applied patch gutenberg.install cleanly.
warning: 1 line adds whitespace errors.

The patch didn't resolve the issue.

Steps followed:
1. Install and enable Gutenberg
2. Create content where Gutenberg is enabled -> Add paragraph -> click on 3 dots to add the block in reusable block -> Select Add to reusable block -> Save
3. Go to content listing -> Reusable block tab
4. Observe the block (check before patch screenshot)
before
5. Now, edit the block content
6. Go to content listing -> Reusable block tab
7. Observe the block (check after patch screenshot)
after
8. Issue still exists

Needs work

jidrone’s picture

This patch contains a hook update, did you run database updates?

marcofernandes’s picture

I confirm that it works after running database updates.

marcofernandes’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.