Default end-of-post text in Gutenberg (how?)
-
?Before Gutenberg, I modified function my_editor_content($content) in ?functions.php to pre-fill a post with text I want at the bottom of each post, effectively creating a default template for new posts. (Invicta theme)
After Gutenberg, that doesn’t work so well, because that text is in the bottom of the first block. New blocks then come after the boilerplate, instead of before.
So when a post is created, I now need two blocks. One at the top with the summary, and one at the bottom with ending text.
How (or when) do I do that, with my existing theme and Gutenberg?
-
I am not talking about how content is output.
Nothing about that has changed.My ISP upgraded to 5.0, which is fine. So I’m figuring it out now.
I do see that the generated text is shown in the classic editor,
when I edit — because it contains more than one “block”.In the “…” menu, there is an option to “Convert to Blocks”.
Doing that puts each section in its own block. That’s more than
I wanted, but it will work. It gives me the option of using blocks
when I went them.It would have been nice to generate content that was in two or
three main editor-blocks, though…You could try creating that template content in Gutenberg using blocks, then switch from the visual editor to the code editor (from the ‘three dots’ menu in the top right corner of the editor), and finally use that markup in your function. It should result in blocks being created in your new post (the comments in the markup delineate the blocks).
There’s also another feature in Gutenberg called Reusable Blocks which might be interesting to you. If you, again, create your template in Gutenberg using blocks, select the blocks, then from the block settings menu (‘three dots’ at the top of the first select block), choose ‘Add to reusable blocks’. Give it an easy to remember name (e.g. ‘New Post Template’). Now when you start a new post you can insert the reusable block (fastest way is using the slash inserter by typing ‘/New Post Template’ in a new paragraph and hitting enter). If you want to edit it, you can use ‘Convert to Blocks’ to make it editable. Reusable blocks are really like creating a stamp from content.
Granted, reusable blocks are not as automatic as your existing way, but it might also be useful for other content you want to reuse across posts.
There is another way to do this, which is probably the right way for blocks. Gutenberg has a concept of block templates. More about that here:
https://www.ads-software.com/gutenberg/handbook/designers-developers/developers/block-api/block-templates/You can assign a template to be the default for a particular post type, specifying the blocks you want within that template. The tricky bit is that you need to figure out what the attributes are for the blocks. Here’s what I attempted for your content (this should replace your existing function):
function my_add_template_to_posts() { $post_type_object = get_post_type_object( 'post' ); $post_type_object->template = array( array( 'core/quote', array( 'value' => '<p>...summary goes here</p>', ), ), array( 'core/more', ), array( 'core/paragraph', array( 'content' => '...content goes here', ), ), array( 'core/paragraph', array( 'className' => 'copyr', 'content' => '…Copyright notice, etc…', ), ), ); } add_action( 'init', 'my_add_template_to_posts' );When I tried this, it seemed to work correctly and the class name was preserved.
Stumbled across the ability to create a new topic once again.
The key is to skip past the “Welcome to Support” link (so appealing, so right there…)
and go down to one of the “View Forum” links. That takes you to an actual forum, where you can review and create topics!(Writing these notes for myself, so I’ll remember them!)
> Where did you find the API details?
My example was lifted pretty gratuitously from the one in the handbook:
For finding the block attributes I had to look through the Gutenberg codebase.
The block-library folder contains each of the blocks. Under the subfolders for each block there’s an index.js file that contains the specification for each block, part of that is the attributes object (sometimes also called schema). Some examples:
– https://github.com/WordPress/gutenberg/blob/master/packages/block-library/src/paragraph/index.js#L34-L73
– https://github.com/WordPress/gutenberg/blob/master/packages/block-library/src/quote/index.js#L20-L40
– https://github.com/WordPress/gutenberg/blob/master/packages/block-library/src/more/index.js#L41-L49There is an issue that tracks adding documentation for blocks, so hopefully that will be resolved at some point in the near future and it’ll make this easier:
https://github.com/WordPress/gutenberg/issues/6190
- The topic ‘Default end-of-post text in Gutenberg (how?)’ is closed to new replies.