The filename is not really relevant. You should check block.json to see where the file is actually being used. I would guess that it’s being used for the viewScript property, in which case you can check its purpose by looking for the documentation for that property, rather than anything about “view.js” alone. As noted in … Read more
I would say that the proper process for this would be: Create a Dynamic Block according to the documentation. The article doesn’t mention it, but you will need to use a tool like @wordpress/scripts to be able to write block JavaScript in the style shown in the documentation. The process for creating a block with … Read more
Actually, you do not need to worry about adding the Masonry’s script handle to the dependencies array in the asset file (index.asset.php). All you needed to do to make your Masonry code work properly is by using the script property to add the masonry (and imagesloaded) as dependencies for your editor and view/front-end scripts. “editorScript”: … Read more
Here is one approach to point the form’s action of your Search block to any custom FSE page on your site, including the current path. It should be possible to use the query attribute in the Search block’s markup in your archive template: “query” : { “post_type” : “fs_ski_resort” } to add the public WP_Query … Read more
I didn’t declare the viewStyle for frontend and thus the css wasn’t being enqueued. { “viewStyle”: [ “file:./view.css”, “example-view-style” ] } build/view.css had all the needed css for swiper – it just wasn’t being declared with viewStyle https://developer.wordpress.org/block-editor/reference-guides/block-api/block-metadata/#view-style . view.css: /*!*******************************************************************************************************************************************************************************************!*\ !*** css ./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[2].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[2].use[2]!./node_modules/swiper/swiper-bundle.css ***! \*******************************************************************************************************************************************************************************************/ /** * Swiper 11.0.7 * Most modern mobile touch … Read more
The simplest solution is to get all the existing rewrite rules, match the requested URl to one of them, and then convert it into a query. Like so: // Get all the rewrite rules global $wp_rewrite; $url_path = “2020/04/test-post”; // Or “tag/whatever” or “feed/atom” etc // Match the URL against WordPress rewrite rules $rewrite_rules = … Read more
I ended up writing a function that wraps the <p> tags in the block comments. This forced the content to be individual paragraph blocks in the editor. My content was only paragraphs but other block types would need to be implemented as well. function blockify_content($content) { //remove empty <p> $pattern = “/<p[^>]*><\\/p[^>]*>/”; $content = preg_replace($pattern, … Read more
As we know WooCommerce product reviews are essentially WordPress comments with a specific comment_type. Firstly we hook into the Comment Submission and then we will check If the Comment is a WooCommerce Product Review and then we trigger our Custom Action. Could you please try to add this to your theme’s functions.php or in your … Read more
You just need to hook your function to the hook you named in the second parameter of wp_schedule_single_event function. See the following example: add_action(‘woo_kala_order_note_added’,’woo_kala_order_note’, 10, 2); function woo_kala_order_note( $comment_id, $kala_order_id ){ // do whatever your logic needs. }
The WordPress REST API includes a ‘status’ parameter that can be used to retrieve posts based on their status. By default, the API only returns posts with a status of ‘publish’. If you want to query ‘pending’ posts, you’ll need to add ‘status=pending’ to your API call. However, please note that you will need appropriate … Read more