A Log of Coding Solutions
by Webhead
One way to easily vertically center a div is to set it to be absolute, set the width, height and then the top, bottom, left and right all equal to 0. Something like this:
.vertically-centered-box {
position:absolute;
top: 0;
bottom: 0;
left: 0;
right: 0;
width:100px;
height:100px;
margin:auto;
}
by Webhead
Go to Appearance -> Menus. Open up Screen Options in the top right. Click on the CSS Classes checkbox under Show Advanced menu properties. Now each menu item has a textbox where you can enter css classes.
by Webhead
Best way according to W3C standards:
http://stackoverflow.com/questions/19689715/what-is-the-best-way-to-detect-retina-support-on-a-device-using-javascript
by Webhead
I could not find any extensive documentation on the WordPress Heartbeat API, so I am writing here to remember what I have learned through various tutorials throughout the web.
The Heartbeat API is written in Javascript. Think of it like a javascript function that gets run every 60 seconds (depending on the interval) which sends data via POST to the server and then the server returns a response. All of which you can easily hook into. It was introduced in WordPress 3.6.
PHP
// server received whatever parameters from when javascript triggered the "heartbeat-send" event.
function myplugin_heartbeat_received( $response, $data ) {
if ( !empty( $data['myplugin_id'] ) ) {
$response['myplugin_got_it'] = true;
}
return $response;
}
add_filter( 'heartbeat_received', 'myplugin_heartbeat_received', 10, 2 );
Javascript
jQuery(document).ready(function($) {
wp.heartbeat.interval= 15;
// set some parameters when it's time to send data to the server
$(document).on('heartbeat-send.myplugin', function(e, data){
data['myplugin_id'] = my_id;
});
// do something when your page gets a response.
$(document).on('heartbeat-tick.myplugin', function(e, data){
if ( data.hasOwnProperty( 'myplugin_got_it' ) ) {
refreshPage();
}
});
});
The ‘heartbeat_settings’ filter gets applied in the ‘init’ hook, priority 0 in wp_default_scripts in wp-includes/script-loader.php. So if you do use the hook on the server-side and want to only run it on certain pages, be prepared to parse the URL because a lot of WP functions aren’t available at that time. Alternatively you can set the interval in javascript with wp.heartbeat.interval(15) where 15 is seconds. Note some other tutorials say to use ‘fast’, ‘standard’, ‘slow’, but that didn’t work for me for some reason.
I found these tutorials to be the most helpful.
http://code.tutsplus.com/tutorials/the-heartbeat-api-getting-started–wp-32446
http://code.tutsplus.com/tutorials/the-heartbeat-api-changing-the-pulse–wp-32462
http://code.tutsplus.com/tutorials/heartbeat-api-using-heartbeat-in-a-plugin–wp-32496
by Webhead
No matter how hard you try, if you add the edit_user capability to a user on multi-site and that user is not a super-admin, the user will not have the edit_user capability. This is hard-coded into WP_User’s map_meta_cap. There is a filter so after it’s all done, you can search for it and take it out if you want.
by Webhead
All these years I’ve been checking the “Remember Me” checkbox when logging in every once in a while in hopes that WordPress will one day actually remember me. I don’t think it ever did, but I didn’t really mind or notice much because I just thought it had something to do with my browser settings or I just didn’t come back soon enough. Well enough is enough. I finally had a project where I needed the Remember me functionality to work.
I made WordPress act as a web app on Apple devices by adding meta tags. But the problem was that every time the user went to the Home screen (exited the app) they would have to log back in when re-opening the app.
Silly WordPress. From as far back as about 5 years ago, (version 2.6.1), people have been having problems with WordPress not remembering them. The solution is simple but is a big quirk if you ask me. Simply drop the last slash (“/”) from the url you visit before logging in. People have reported Remember Me working on urls like “mydomain.com/wp-admin” but not “mydomain.com/wp-admin/”. Turns out it also works on other URLs like “mydomain.com/mypasswordprotectedpage” but does not work on “mydomain.com/mypasswordprotectedpage/”. Give it a try.
http://wordpress.org/support/topic/remember-me-does-not-remember-me