Ok, I found the answer myself thanks to Can you filter posts by meta key with the getEntitityRecords selector? Despite my first understanding the >>>query<<< parameters for list posts given in the Reference do >>>not<<< contain the meta. I followed the article and created a query filter for the CPT, i.e. function mycustomposttype_meta_query_filter() { add_filter( … Read more
WARNING: There be dragons ahead Changing the allowed innerblocks of the core/buttons block can be done, but it will make your life harder and introduce lots of new problems. Note that it would be faster, easier, and safer to implement a new buttons block that only accepts your custom block. To do this you would … Read more
Set the group property of InspectorControls to styles: <InspectorControls group=”styles”> // etc. </InspectorControls> The other possible groups are described in this article.
To achieve your goal: All of your React logic will need to be in your edit.js file and not your save.js file. The save.js file is only for viewing the final data on the WP Admin after you save a post or on the live post. The view.js file can only contain Vanilla JavaScript (from … Read more
When you return $post->post_content you’re returning the raw content from the database. Things like shortcodes, dynamic blocks and responsive image markup will not exist in the content. To prepare content for output you need to run it through the the_content filter: ‘content’ => apply_filters( ‘the_content’, $post->post_content ), That being said, there is already an endpoint … Read more
Finally,I have found a solution. I can pass my custom block to the InnerBlocks inside a template prop. const TEMPLATE = [ [ “core/columns”, {}, [ [ “core/column”, {}, [[“custom/Block A”, { url: “this is a url” }]], ], [ “core/column”, {}, [[“core/paragraph”, { placeholder: “Enter side content…” }]], ], ], ], ]; <InnerBlocks template={TEMPLATE} … Read more
Yes. [class*=”wp-block”][class]:hover > img { filter: none; } That ruleset works for hover on either Image or Cover blocks but you may want to write less generic selector for it depending on your intent.
You may have a Wood block that describes the type of wood used in a woodturning item, or a Minerals block to list the minerals used for a jewelry work. You don’t want this two blocks to be used at the same time, because jewelry is not about wood and woodturning is not about minerals, … Read more
As I am extending core/group block to add option for setting different image for smaller displays I used render_block_core/group filter to add style tag. I am already adding data-mobile-background-image to each group for its mobile view background image so there is no need for updating it through ID as suggested by Tom J Nowell. Final … Read more
After reading through a lot of documentation/discussion, I found that the “official” way of requesting data for a block is useSelect. In my case, the answer would be: const posts = useSelect(select => { return select(“core”).getEntityRecords(“postType”, “post”, { per_page: 3, sticky: true }); });