Skip to content
This repository has been archived by the owner on Feb 11, 2021. It is now read-only.

Backend error: Limited naming options for custom editor block plugins #238

Open
neropha opened this issue May 19, 2020 · 1 comment
Open
Labels
type: bug 🐛 Issue is a bug; PR is a bugfix

Comments

@neropha
Copy link

neropha commented May 19, 2020

I followed the instructions in the wiki to create a custom editor block plugin.

In my blueprint setup of th parent page I have the following:

fields:
  blockfield:
    type: editor

Desspite doing everthing as suggested in the example, I got this error in the backend:

The field type "blockfield" does not exist

I figured, if I rename the plugin folder from "custom-block" to "editor-custom-block", my custom plugin worked.

Following folder names didn't work: custom-block, button-block, cta-block, aaa, bbb, ccc and many more. I think it has to do with the starting letters

I ended up prefixing all my custom editor blocks with "editor-block-" Then the plugin works without further modifications.

Maybe I'm missing something here, but I should be able to name my block plugin however I like, right? Kirby and Editor are both in latest version

@olvrbrown
Copy link

I have experienced this too, I believe it's because Kirby loads its plugins in alphabetical order - any editor extensions loaded before the editor plugin itself (i.e. those sorted before it alphabetically) don't work.

@bastianallgeier bastianallgeier added the type: bug 🐛 Issue is a bug; PR is a bugfix label Jul 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug 🐛 Issue is a bug; PR is a bugfix
Projects
None yet
Development

No branches or pull requests

3 participants