How can I extend the Gutenberg table block transform to allow colspans/rowspans on pasted table elements?
How can I extend the Gutenberg table block transform to allow colspans/rowspans on pasted table elements?
How can I extend the Gutenberg table block transform to allow colspans/rowspans on pasted table elements?
The two variables $name and $email are unknown inside the function. You have to make them globally available inside it by changing global $wpdb into global $wpdb, $name, $email: require_once(‘../../../wp-load.php’); /** * After t f’s comment about putting global before the variable. * Not necessary (http://php.net/manual/en/language.variables.scope.php) */ global $name = $_POST[‘name’]; global $email = $_POST[’email’]; … Read more
You’ve just discovered an important feature of the core test suite: it forces any tables created during the test to be temporary tables. If you look in the WP_UnitTestCase::setUp() method you’ll see that it calls a method called start_transaction(). That start_transaction() method starts a MySQL database transaction: function start_transaction() { global $wpdb; $wpdb->query( ‘SET autocommit … Read more
These additional dropdowns are added via the restrict_manage_posts action hook. This means the dropdown output isn’t filterable, but you can remove the hooked action from Yoast SEO. The filter dropdown is added by the posts_filter_dropdown() method in the WPSEO_Metabox class. It’s added in the setup_page_analysis() method of the same class, which is hooked into admin_init … Read more
Perhaps there’s a manageable way to shift the images from being store as attachments (aka posts) to being stored in an array that’s kept at the parent post level. I think it’s going to depend on how much you need to manipulate the images, delete them, etc. Shifting to another table might help but it … Read more
That table is essentially the same as for all of the other “meta” tables in the WordPress architecture. It holds misc. bits of extra, usually optional, information about the associated post, user, or in this case comment. You can store whatever information you need to add to a comment– perhaps a plugin wants to implement … Read more
Ok, first of all, I feel like an idiot, although in my defense most of the articles that talk about this don’t mention a very crucial detail in making this work. The answer is that you need to set permission for at least one admin in the database. This info can be found in the … Read more
to_ping is a list of URLs WordPress should send pingbacks to. pinged is a list of URLs WordPress has sent pingbacks to. Do not use these fields for something else. They are parsed many times in core code (69 matches for to_ping); their format is fixed. You cannot reduce the query load by using these … Read more
It is mandatory, though it is not enforced. Consider the scenario when two WordPress site has been setup in the same database. One with prefix wp_ and another with wp2_. If you install your plugin in both of the sites with the prefix, your created tables will be wp_liveshoutbox for first site and wp2_liveshoutbox for … Read more
I finally found the custom post type data. It is stored in the wp_post table where post_type = custom post type (e.g. “products”). The field (column) data is stored in wp_postmeta where the meta_key is the column name and meta_value is the column value. This query will bring back all data associated with the custom … Read more