draft is not a post_type, it’s a post_status. So you should use your second block of code with that substitution: DELETE a,b,c FROM wp_posts a LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id) LEFT JOIN wp_postmeta c ON (a.ID = c.post_id) WHERE a.post_status=”draft”
No, there is no inherent security flaw in $wpdb, or using it within a shortcode. However, you can introduce vulnerabilities if you aren’t careful how you use it. There are primarily two issues that you should be thinking about. The first is escaping. You need to make sure that any potentially user-controlled values are escaped … Read more
You can use wpdb to setup a new connection. Add something similar to this below in your functions.php and you can then query just like you would normally but using the new connection. $second_db = new wpdb(DB_USER, DB_PASSWORD, $database_name, DB_HOST); $results = $second_db->get_results($your_query); references: https://wordpress.stackexchange.com/a/1673/86845 https://stackoverflow.com/a/36759606/3204142
While it is VERY bad practice to have spaces in the object names, there are times where it may be out of your control. You can use the syntax of $object->{‘Property Name’}, like this: // add the shortcode [pontoon-table], tell WP which function to call add_shortcode( ‘pontoon-table’, ‘pontoon_table_shortcode’ ); // this function generates the shortcode … Read more
When you use add_post_meta, no column in database is created. All post meta data is stored in wp_postmeta table (https://codex.wordpress.org/Database_Description#Table:_wp_postmeta). Here’s the structure of that table: post_id is the ID of post that this meta data is assigned to meta_key is the key of meta (in your case favourite_fruit_code) meta_value is the value of that … Read more
This actually happens to me. I usually resolve this via string replace function. First one replaces the WordPress Content area. The second filter is replacing the Title area. Check out the str_replace array and insert your œ to your own string before the $content array. function replace_the_content_filter( $content ) { if ( is_single() ) // … Read more
plugin_dir_url() returns the URL directory path for your plugin, so this won’t work as expected (the function won’t be called): register_activation_hook(plugin_dir_url(__FILE__) . ‘frequentVisitorCoupons.php’, ‘Utilities::createTablesIfNotExists’); You should have used plugin_dir_path() which returns the file-system directory path for your plugin (e.g. /var/www/public/<user>/wp-content/plugins/your-plugin/). But if the code is in the main plugin file, then you could simply use … Read more
The short answer is yes. Having a secure username and password is paramount to keeping your site secure.
There are a few things to note: there is no error checking on wp_insert_user, so there’s no way to know if it failed and why wp_insert_user can be used to set the role etc, the follow up calls aren’t needed, if you read the official docs, there are parameters for those fields Never modify the … Read more
Yes, WordPress checks for duplicate emails internally, but not duplicate usernames To test this I ran this several times via wp shell: wp_create_user( ‘test’, ‘password’, ‘[email protected]’ ); The result on the second attempt was: => class WP_Error#1962 (2) { public $errors => array(1) { ‘existing_user_email’ => array(1) { [0] => string(42) “Sorry, that email address … Read more