Highly secretive print screen tips

Okay, so maybe they aren’t that secretive, but they are definitely helpful and not as well known as they should be!

Everyone has used that magic Print Screen button (PrtScn) at one point or another. Contrary to my belief as a child, no it does not send anything to the printer as the name implies!

In case you don’t know, the Print Screen button simply takes a “snapshot” of everything on your screen and copies it to the clipboard, where you can paste it (Ctrl-V) into your photo editing software for example. continue reading

Expanding content area of WordPress TwentyFourteen theme

I stumbled upon a post on a blog run by David Lehman (NowhereLAN) the other day that caught my attention. It was regarding changing the page content area in WordPress’ TwentyFourteen theme.

Like David, I used TwentyFourteen as the base for my theme, and have been editing it to suit my needs. One of the things that bothered me was the excessive padding around the content area. As David points out in his post, its not so much a padding issue as it is the max-width set in the css file.

Two things I did differently. continue reading

Lightweight GA (Google Analytics) on WordPress installation

Today was time to install Google Analytics onto this blog. As you can imagine, there is far more than a “handful” of WordPress plugins to enable something as simple as GA Tracking.

I wanted to go for something a little more lightweight. Let’s face it, a plugin is a little overkill for two reasons. First of all, without tearing down into the source code of each plugin, you really don’t know what all its doing in the background. And second of all, Google gives you the Analytics code, so why make it harder than it has to be? continue reading

Force secure connection (SSL/HTTPS) using .htaccess and mod_rewrite

It recently came up where I wanted to force users visiting the IdleDev page to use a secure connection (https) domain wide (mostly for the development of Zero Day to ensure a secure connection is used at all times).

Unfortunately this was something that did not appear to be directly supported by my host. Luckily they do allow .htaccess and mod_rewrite, so from there it was easy.

By placing that text into your .htaccess file, and replacing “www.exampledomain.com” with your own domain, it will redirect the user to use an secure connection throughout the entire domain (essential for sending encrypted passwords, or any other data over the web that requires a secure connection). continue reading