In my blueprint there is a blocks field with certain content blocks to make up a blog post. Through PagePermissions another user is not allowed to edit my article. This works fine so far. The block field correctly shows
However the blocks contained in the blocks field gets not disabled automatically
Although the block is almost disabled through CSS it is not really
disabled=true which causes the markdown editor (markdown-field plugin) still to be editable.
I am wondering why the disabled prop isn’t propagated down the line into the blocks contained in the blocks field?
Best, Thomas E.-E.
I’m afraid this appears to be a bug:
07:55AM - 14 Mar 23 UTC
type: bug 🐛
When blocks field is disabled (with `translate: false` or `dis
… abled: true`), editable blocks are still editable like text-heading-quote blocks.
## To reproduce
Use following blueprint for blocks field:
Or you can use `translate: false` on secondary language.
Then try to edit the editable fields like text-heading-quote blocks.
For more complicated bugs, sample code makes it a lot easier for us to reproduce and fix a bug.
Please clone our https://github.com/getkirby/starterkit or https://github.com/getkirby/plainkit as base to create a minimal verifable setup that repoduces the bug.
## Your setup
3.6.x - 3.9.x
thanks for your quick reply and for creating the issue