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

Block Directory: Explore linking to the block directory when a block is found in the content but now is not installed. #24759

Closed
jorgefilipecosta opened this issue Aug 24, 2020 · 2 comments · Fixed by #22631
Labels
[Feature] Block Directory Related to the Block Directory, a repository of block plugins [Status] In Progress Tracking issues with work in progress [Type] Enhancement A suggestion for improvement.

Comments

@jorgefilipecosta
Copy link
Member

Currently, when in the content of post we find a block that is not installed, we don't provide a good fallback and just have a generic validation error.

I guess with the block directory we may search for a block and allow the user to install that block again.

@jorgefilipecosta jorgefilipecosta added [Type] Enhancement A suggestion for improvement. [Feature] Block Directory Related to the Block Directory, a repository of block plugins labels Aug 24, 2020
@mcsf
Copy link
Contributor

mcsf commented Aug 25, 2020

I believe this in the plans for @StevenDufresne and @tellyworth. No? Worth a link from #23378?

@ryelle
Copy link
Contributor

ryelle commented Aug 25, 2020

There's this work in progress to allow installation from the missing block warning: #22631 (comment)

90553542-c744d900-e151-11ea-8a09-290449c21536

@mtias mtias added the [Status] In Progress Tracking issues with work in progress label Aug 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Block Directory Related to the Block Directory, a repository of block plugins [Status] In Progress Tracking issues with work in progress [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants