Skip to content

WP Pattern Directory Pattern Editor not working properly due to store core/interface' already registered error #723

Open

Description

@jhimross

Describe the bug
When attempting to create a new pattern using the WordPress Pattern Directory editor, an error "Store 'core/interface' is already registered. i@registry.js:220" appears in the browser's developer console. This error prevents blocks added to the editor from rendering and styling correctly, leading to a broken visual experience where blocks do not appear as expected or lose their intended styling.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://wordpress.org/patterns/new-pattern/'
  2. Use the editor to add any blocks (e.g., Paragraph, Image, Columns).
  3. Observe that the added blocks are not working as expected; their styling is incorrect or they fail to render properly.
  4. Open the browser's developer console (usually by pressing F12 or right-clicking and selecting "Inspect" then navigating to the "Console" tab).
  5. See the error message: Store "core/interface" is already registered. i@registry.js:220

Expected behavior
When using the WordPress Pattern Directory editor, blocks should render and apply their styling correctly without any console errors. The editing experience should be smooth, allowing users to accurately preview the pattern they are creating.

Screenshots
Windows - Edge Browser: https://share.zight.com/5zuk0xWP
Windows - Chrome: https://share.zight.com/eDupNq95
MacOS - Chrome: https://share.zight.com/7KulYOdz

Desktop (please complete the following information):

  • OS: Windows 10/11, macOS (Latest versions)
  • Browser: Chrome, Firefox, Edge
  • Version: Latest stable versions (e.g., Chrome v138.0.7204.63 , Edge v138 as of July 2025)

Activity

  1. dd32 commented on Jul 17, 2025

    @dd32
    Member

    Looks like #725 didn't fix this, it's fixed the warning, but the styles still aren't being loaded. FYI @gigitux

  2. reopened this on Jul 17, 2025
  3. gigitux commented on Jul 17, 2025

    @gigitux
    Collaborator

    Looks like #725 didn't fix this, it's fixed the warning, but the styles still aren't being loaded. FYI @gigitux

    Yep, as I mentioned in the description, the PR fixes only the registration error. IMHO, we should invest our time into #719. Is there a slack channel to sync about this work?

  4. dd32 commented on Jul 18, 2025

    @dd32
    Member

    @gigitux Ohh gotcha :) Sorry I wasn't fully insync.

    We don't have a dedicated patterns team, nor slack channel.
    Pattern Dev discussion can take place in #meta on W.org slack, and moderation/submission/etc questions occur via #themes

  5. gigitux commented on Jul 18, 2025

    @gigitux
    Collaborator

    No worries! I noticed that @ryelle is working on that PR. Please ping me here or on Slack if I can assist you.

  6. ryelle commented on Jul 18, 2025

    @ryelle
    Contributor

    I really just rebased it, still need to figure out what the immediate next steps are. Happy to coordinate in #meta if you want to work on it together :)

  7. supernovia commented on Apr 13, 2026

    @supernovia

    @ryelle is this related to these? The first one seems similar and the second seems partially solved.
    #737
    and #741

    also noting we now have a #patterns slack channel to coordinate!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions