I’m sharing my solution here in case it can help someone, as I believe this type of shortcode transform is a common use case. As fetching data inside a transform is not possible right now, I’m creating the block inside the transform by passing just the carousel id attribute from the carousel shortcode. I then … Read more
If we stick to your exact example, I would define the value as a custom property in an inline style: <div class=”item” style=”–my-gap: <?php echo esc_attr( $attributes[‘gap’] ); ?>;”> Then in CSS use a media query to use the property as the appropriate margin: .item { margin-bottom: var(–my-gap); } @media ( min-width: 768px ) { … Read more
To pass the current post type to your AJAX request, you need to modify your JS to include the post type information in the AJAX request. You can achieve this by adding the post type as a parameter when calling the filterPosts() function JS import Alpine from ‘alpinejs’; Alpine.data(“filterPosts”, (adminURL, postType) => ({ posts: “”, … Read more
This approach should work, Modify it for your use case. //JQuery Code jQuery( document ).on( ‘change’, ‘.from-this’, function( e ) { e.preventDefault(); jQuery( ‘.change-this’ ).text( this.value ); } ) HTML Code: <input type=”search” class=”from-this” /> <div class=”change-this”></div>
Problem solved. If there’s anybody that has the same problem as me, go into the *.php file where you’re trying to render the block. Make sure that you’re using the_content() in order to render the page content and not get_the_content().
I found the solution: I removed addFilter(‘blocks.getSaveContent.extraProps’, ‘luxuryconcept/add-custom-props’, addCustomProps); as @TomJNowell recomended. I added the add_filter(‘render_block’, ‘theme_custom_add_custom_attributes’, 10, 2); PHP code to functions.php: So, here all the working code: JS: /** * * Extends Core Gutenberg Blocks functionalities * * @description Add data-delay and data-duration attributes to every Gutenberg Core Blocks * @package luxuryconcept * … Read more
You’re not actually updating the block. You’re just updating the current state of the block component in the editor. To have an option persist you need an attribute to store whether the option is toggled, and then you need to call setAttributes() to save that attribute. This is what the editor will recognise as a … Read more
So I finally figured out my problems. One mistake I was making was not structuring $options properly. This is WRONG what i did: $options = array( ‘http’ => array( ‘header’ => “Authorization: Bearer $api_key\r\n”, ‘method’ => ‘GET’, ), ); I’m not supposed to use http. This is the CORRECT WAY to do it: $options = … Read more
Yes, but you have to do it Redux- way. Subscribe to post saving action (there are separate actions for save and auto-save) and dispatch a message using dispatch function. Edit: Inside blocks, there are better hooks to use, like useSelect. But, outside the block, in general block editor environmentm you have to use subscribe. In … Read more
configure additonal build files in the @wordpress/create-block