I think the problem might be that the spread operator is missing in a couple of places. This line: return { meta: { currentMeta, editedMeta }, }; in withSelect should be: return { meta: { …currentMeta, …editedMeta }, }; This makes the meta object be a copy of currentMeta (have all the same properties and … Read more
I managed to come up with a solution myself. To get a list of posts of a specific post type one must wrap the wp.data.select( ‘core’ ).getEntityRecords() selector inside the withSelect higher order component, which is a function that provides props to a component using selectors. Then, we can populate a SelectControl with this data. … Read more
First thing that jumps out is that in: <!– wp:mvc/block-mvc-offer-details {“data_offer”:”2426″} /–> the data_offer value is stored as a string while it’s defined attribute type is number. This could be why it’s stripped after reload. While select(‘core’).getEntityRecords does return IDs as integers it’s possible that after passing that data to <SelectControl> and then receiving the … Read more
I don’t think this is possible in Gutenberg for the gallery block. There still isn’t a unified way to modify these types of settings for blocks either (the panel, typically on the right-side of a desktop screen, is collectively called the Inspector Controls)
Uploaded images are already posts, a gallery is just a list of post IDs with some display options In WordPress, when you upload an image it creates a post of type attachment, and these posts have URLs, templates, etc If you just link the gallery items to their attachment page rather than the media file … Read more
Adding it the way you’ve suggested is not possible, and adding inline style attributes would be bad practice. However, what you want is possible by adding CSS classes, e.g. array( ‘core/heading’, array( ‘level’ => 3, ‘className’ => ‘biggerh3’, ‘placeholder’ => ‘Bigger Heading Placeholder’ ) ), Then this CSS: .biggerh3 { font-size: 1.34em; } Or by … Read more
seems my problem was in my array ‘level’ => ‘3’, should’ve been ‘level’ => 3,
This data is not passed into Gutenberg by default. You should create custom REST API endpoint and data store. This article might help with some code examples.
There may be several other issues interacting here, but the big one is here: function onSelectImages(media) { const imagesUrl = values({…media}).map((item, i) => { return ({id: item.id, url:item.url}); }) setAttributes({ selectedImages: (values({…imagesUrl})) }); } When images are picked, you grab the images and set them as the selected images. This is not the same as … Read more
Yes and no, it depends… The WP Scripts package depends on the @wordpress/dependency-extraction-webpack-plugin package at: https://github.com/WordPress/gutenberg/tree/master/packages/dependency-extraction-webpack-plugin What this will do is search for packages from @wordpress and list them in a file to make it easy for you to load the list of dependencies when enqueuing. It also adjusts webpack so that it knows not … Read more