Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: social links registration logic. #17494

Merged
merged 1 commit into from
Sep 20, 2019

Conversation

jorgefilipecosta
Copy link
Member

Description

Blocks may be registered on WordPress core and Gutenberg. When we load a block in Gutenberg we need to unregister the equivalent core block to make sure the one implemented on the plugin is loaded.
This PR fixes this logic to work with the social link(s) blocks that register multiple blocks in a single PHP file.

How has this been tested?

Run the Gutenberg plugin on WordPress develop trunk and verify there are no errors saying social link blocks were registered multiple times.

@jorgefilipecosta jorgefilipecosta added the [Type] Bug An existing feature does not function as intended label Sep 20, 2019
@youknowriad
Copy link
Contributor

Looks like there are some failing tests, otherwise, this fixes the issue for me.

@jorgefilipecosta jorgefilipecosta force-pushed the fix/social-links-registrarion-logic branch from 4ed9cc3 to 0db3b70 Compare September 20, 2019 09:20
@jorgefilipecosta
Copy link
Member Author

Looks like there are some failing tests, otherwise, this fixes the issue for me.

Hi @youknowriad, I think the failing test was a lint error and I fixed it meanwhile.

@jorgefilipecosta jorgefilipecosta merged commit c8e1da4 into master Sep 20, 2019
@jorgefilipecosta jorgefilipecosta deleted the fix/social-links-registrarion-logic branch September 20, 2019 09:56
@youknowriad youknowriad added this to the Gutenberg 6.6 milestone Sep 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants