You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WP Pattern Directory Pattern Editor not working properly due to store core/interface' already registered error #723
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.
Use the editor to add any blocks (e.g., Paragraph, Image, Columns).
Observe that the added blocks are not working as expected; their styling is incorrect or they fail to render properly.
Open the browser's developer console (usually by pressing F12 or right-clicking and selecting "Inspect" then navigating to the "Console" tab).
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.
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?
@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
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 :)
Activity
dd32 commentedon Jul 17, 2025
Looks like #725 didn't fix this, it's fixed the warning, but the styles still aren't being loaded. FYI @gigitux
gigitux commentedon Jul 17, 2025
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?
dd32 commentedon Jul 18, 2025
@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
gigitux commentedon Jul 18, 2025
No worries! I noticed that @ryelle is working on that PR. Please ping me here or on Slack if I can assist you.
ryelle commentedon Jul 18, 2025
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 :)
supernovia commentedon Apr 13, 2026
@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!