Link to configuration edit form after config entity has been saved

Created on 29 September 2017, over 6 years ago
Updated 21 December 2023, 5 months ago

Problem:

Currently, when you save a configuration entity, you might not be able to find it again easily.

I.e after you save a block, you will get the following message: "The block configuration has been saved". If you had accessed the block configuration from the contextual links and adapted the visibility conditions, you are likely to not be able to adapt the block settings, if the block doesn't show up on the screen anymore. Of course, you can still find it via the admin backend, but site admins might not even be aware of this path.

Proposal:

Similarly to content entities, it would be nice if the configuration entity save message, would contain a link to the entity. As configuration entities don't have a canonical url to be displayed, instead, I would suggest to add a link to the edit form.

Current (before patch):

After patch:

πŸ“Œ Task
Status

Needs work

Version

11.0 πŸ”₯

Component
Configuration entityΒ  β†’

Last updated 4 days ago

Created by

πŸ‡¨πŸ‡­Switzerland dasjo Zurich

Live updates comments and jobs are added and updated live.
  • Novice

    It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.

  • Needs usability review

    Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request β†’ as a guide.

    Seems like an excellent feature and helpful

    #29 appears to have done the manual review so I'll do the code

    No new functions so nothing to typehint.
    Tests have been updated for the new link.

    I don't think such a feature would need a change record but maybe?

    Tagging for usability review as it is a UI change

    Also tagging for screenshots to be added to the issue summary for before/after.

    Thanks!

  • πŸ‡ΊπŸ‡ΈUnited States capysara

    I embedded the screenshots provided in #29 into the issue summary and removed the screenshots tag.

  • πŸ‡ΊπŸ‡ΈUnited States capysara

    I embedded the screenshots provided in #29 into the issue summary and removed the screenshots tag.

Production build 0.69.0 2024