If you were in the process of making any changes when the bot came by, it may have picked up something bogus from the site. You can request a review in search console, I think they should either green-light it or tell you more specifics on what the problem is.
It doesn’t work because that is old behaviour and Gutenberg changed a year ago. Where The Confusion Comes From This commit: https://github.com/WordPress/gutenberg/commit/00cb38c3655daffd429ad4acfc57d6ee3b7f2d83 On Apr 20, 2022 code was removed that made it fallback to the plugin icon. Now an icon has to be explicitly passed as a prop or no icon is shown. Why? https://github.com/WordPress/gutenberg/pull/40355 … Read more
isset() checks to see if a variable is set, ie, has a value other than null. The way you’re using it will always return true because you’ve set $posttags to ‘animali permessi’, which is not null. I think you’re looking for the WordPress function has_tag() instead. if (has_tag( ‘animali permessi’, $post ) ) { $supplemento_animali … Read more
Use the action hook edit_form_after_title The display:none rule might cause some JS issue so it might be best to use visibility:hidden so the element is still accessible to whatever scripts in the DOM. This condition will hide the form fields and show the title and URL statically. add_action(‘edit_form_after_title’, function($post) { if( !empty($post->post_title) && !current_user_can(‘manage_options’) ) … Read more
It’s only a good pratice to adopt this naming convention. As long as you have in the header of your main file the meta (at last Plugin name: Name of Your Plugin, WordPress will automatically recognize this file for being the main one. Be aware that at the top of this file you should write … 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
Yes, the nonce is by default always being sent via the X-WP-Nonce header – see the source here and here on GitHub. wp.api.WPApiBaseModel.prototype.sync and wp.api.WPApiBaseCollection.prototype.sync can technically be extended or modified, but I would instead disable the nonce header like so, i.e. using <Collection or Model object>.endpointModel: Collection example: const Posts = new wp.api.collections.Posts(); // … Read more
If your option is enabled in the REST API, e.g. by using register_setting() with ‘show_in_rest’ => true, you can use wp.data.select( ‘core’ ).getSite() to retrieve the value of your option, and to update the option, you can use wp.data.dispatch( ‘core’ ).saveSite(). So for example in your case: To get the option value: wp.data.select( ‘core’ ).getSite()?.autoupdate … Read more
No commands are safe when ran as root. Even the help screens aren’t safe as root. The reason the –allow-root flag is considered dangerous is not because of what the CLI commands themselves do, but because your entire sites code is loaded when WP CLI runs, but now as root. This would mean any hidden … Read more
I ran into this same problem and did some digging. The jQuery selector to find the checkboxes includes an iedit class on the table <tr> elements. I assume this class is added via JavaScript on tables that have inline editing, but my <tr> elements had no classes as I’m not using inline editing. I was … Read more