Timeline for Gutenberg and FSE: How to exclude a block from full site editing
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 17, 2023 at 9:46 | answer | added | Saulius Vikerta | timeline score: 0 | |
| Jan 19, 2022 at 20:11 | vote | accept | Marc | ||
| Jan 19, 2022 at 19:13 | answer | added | Tom J Nowell♦ | timeline score: 4 | |
| Jan 19, 2022 at 19:03 | comment | added | Tom J Nowell♦ | is your block rendered in javascript or in PHP server side? Note this will eliminate/allow options. Also keep in mind that posts can be edited from within full site editing, and templates can be inserted into posts and gain that posts context. Posts and pages can also have custom templates defined via full site editing, so the idea that a block either is or is not in the full site editor doesn't make sense unless you're very careful about how you use a block | |
| Jan 19, 2022 at 16:52 | comment | added | WebElaine | It doesn't look like there is a setting or hook to prevent a block from being available in FSE, but you could check within the block so that if it is not within a Page or Post (or Editor for those contexts) it returns either a warning that it can only be used in Pages and Posts, or else nothing so it's invisible if it's in the wrong context. | |
| Jan 19, 2022 at 16:09 | history | asked | Marc | CC BY-SA 4.0 |