Problem/Motivation

When using the Paragraphs Entity Embed module, system messages related to embedded Paragraph entities appear to editors or end-users after saving content. These messages, such as:

EmbeddedParagraphs 05bc4edb-1217-4b7b-85f4-15abfafe6d46 has been created.
EmbeddedParagraphs 05bc4edb-1217-4b7b-85f4-15abfafe6d46 has been updated.

are unnecessary and confusing, for two reasons:

  1. The UUIDs are meaningless to content editors.
  2. They clutter the UI with a message for each embedded entity, each time its edited. even though those entities are part of the parent content (e.g., an article). Editors expect to manage the article as a whole, not receive updates for each embedded sub-entity.

These messages should be logged to watchdog only and not shown to the user. The user should only see the main entities update messages (e.g., Article [name] was updated)

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

loze created an issue. See original summary.

loze’s picture

Issue summary: View changes
loze’s picture

Issue summary: View changes
loze’s picture

I just realized that the UUID for title I am seeing is due to the patch here #3132549: Add an option to only let paragraphs be used once. I still feel that there should be an option (maybe per embed button) to disable displaying these status messages.

loze’s picture

Status: Active » Needs review

This MR prevents the status messages from displaying when editing from within the ckeditor dialog

smustgrave made their first commit to this issue’s fork.

  • smustgrave committed d553919e on 4.0.x
    feat: #3535885 EmbeddedParagraphs create/update messages should not be...
smustgrave’s picture

Status: Needs review » Fixed

I'm fine with this change. Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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