Quoting from the WordPress VIP Development Best Practices: Remember that the database is not a tool box. Although you might be able to perform a lot of work on the database side, your code will scale much better by keeping database queries simple and performing necessary calculations and logic in PHP. That said, you might … Read more
This is what I just used, maybe there was a problem in past versions of WordPress or your theme. function allow_contrib_upload() { // get the role $contrib = get_role( ‘contributor’ ); // add the upload capability $contrib->add_cap( ‘upload_files’ ); } add_action( ‘admin_init’, ‘allow_contrib_upload’, 11 );
The currently logged in user The \WP_User object/instance can be retrieved via: $user = get_current_user(); There’s a shortcut API wrapper to fetch the ID: $user_id = get_current_user_id(); $wpdb and the WP “DBAL” WP basically uses $wpdb as DBAL/Database Abstraction Layer. It got plenty of public methods and some higher level wrappers for convenient access. One … Read more
add this code to your function.php <?php function showMessage($message, $errormsg = false) { if ($errormsg) { echo ‘<div id=”message” class=”error”>’; } else { echo ‘<div id=”message” class=”updated fade”>’; } echo “<p><strong>$message</strong></p></div>”; } function showAdminMessages() { showMessage(“This is my message.”, true); } add_action(‘admin_notices’, ‘showAdminMessages’); ?>
You could try something like this. DELETE FROM wp_users WHERE ID in ( 5506, 5507,… ); Make sure to try it on a staging area first and backup your database.
If you’re using WooCommerce, they have a shortcode that displays the logged in user’s account details on a front end page: [woocommerce_my_account]
It gives an array with objects. So in_array() won’t find anything, you have to convert it before. After you get the results from wbdb: $employees_array = array(); foreach($employees as $employee) { $employees_array[] = $employee->meta_value; } if(in_array($company, $employees_array)) { … }
s_ha_dum’s answer prompted me to look into this a little further. I checked the users in the database. It turns out that the dropdown list in Posts -> Edit is using the Display Name, not the User Login, as I had expected. So, the problem was not that WordPress was functioning incorrectly, but that my … Read more
No, there isn’t. WordPress login “sessions” are cookie-based and work on each device as if they were the only one in existence.
Many plugins (and themes) use user levels, you shouldn’t use them in yours. They are still used in WordPress probably to offer backward compatibility with the huge number of plugins and themes that use them. WPCS will throw a warning whenever it busts user levels in code.