Today I went to work expecting a great day. My young friend Chris Merris was coming back to TheraDoc, and it’s always a good thing to have sharp people around you.
The mood of the day suddenly shifted as I found out that Jeff Knell, another new friend at work had died over the weekend. I felt extremely sad all day, not so much because I’d lost a close friend (although I thought that Jeff and I were going to be good friends).
Instead I think it has more to do with the loss of that growing friendship, and the reminder of the transience that is life.
Out of the box these images have their timezone set to UTC, and since my end users are in California, and I’m not doing anything on the client to handle timezone conversion, the times that come up in the application are off by 7 or 8 hours (depending on whether it’s Daylight Savings time or not. Continue reading
I’m always fascinated by unintended consequences, especially when they are an artifact of trying to do something right.
In moving to Salt Lake City from California, I’ve been reminded that good intentions and planning do not a perfect world make.
I live close to downtown, so I’ve started walking to work. It’s a nice walk, gives me a bit of exercise, and makes me feel I’m being a bit more “green” by not driving.
The sidewalks have those nice ramps into the crosswalk, which lets a wheelchair roll across. And they keep somebody who’s not quite paying attention from tripping on the curb …
It’s all great until it snows …
Recently I’ve been seeing a lot of the annoying message about pages dying on Chrome. For the most part it’s just annoying, and clicking “wait” lets the page load.
Until this morning, when for some reason Chrome just stopped letting me get to any of my hosted web sites. Whenever I would go to http://www.accuweaver.com, http://accuweaver.com, http://www.cozybabycare.com or http://www.incdpc.com, I would immediately see a “No data received” message:
I was setting up a temporary WordPress site for a client as a placeholder for their business. All they wanted was their logo, a link to an existing product page, and a message about the site being under construction.
I had to set up a WordPress instance on a server where my only real access is via cPanel, so I Googled a bit and found this article: http://www.howtogeek.com/howto/20859/install-wordpress-manually-on-your-website-using-cpanel-wizards/
First step is to log in to the cPanel, which is typically at some arbitrary port on your server, and log in with your admin credentials. If you go to the right URL, you’ll be prompted with something like:
So, just like any WP installation, the first thing you need is a database, so you look for the Database Wizard (in the Databases section):
This will bring up the Wizard which will ask you for a name. In this case I’m creating a test wordpress, so I type in “WP_test” just so I know which DB I’m using. This can really be anything, just has to be unique.
If you’re on a shared host (which I am) this name gets prepended with your admin account name (this is how the server knows which databases belong to you and keeps you from seeing other people’s database schemas).
Going to the next step, you’ll be asked to create the database users. Again this can be anything, but also needs to be unique to the schema you’re creating. At this point the database has been created, but there are no users. The user name also gets prefixed with the account on a shared host system:
You can give the user any name and password you want, you will need those along with the database name once you are ready to fire up WordPress. I believe it is possible to use the same user for multiple databases by skipping this step and manually adding them to the newly minted database later instead, but it’s probably not the most secure way to set up access.
In my particular setup, I want to attach this new WordPress to a specific host name, so the next thing I do is my Subdomains panel in order to create the directory and tell Apache where to send the users. The default behavior is for the directory to be a folder under public_html with the same name as the subdomain, so in my case “WPtest” causes a folder named /public_html/WPtest to be created:
In my case I prefer to keep them separate physically, so I remove the “public_html/” part and call the folder something more meaningful. Depending on your setup, you may also need to add this new host name to DNS, although for testing you don’t even need that (more on this later).
The next thing to do is to get the latest WordPress binary and upload it to the newly created folder, which you can do using the cPanel folder manager:
I next see a popup that asks me where I want the File Manager to start, so I pick my new subdomain:
In reality it displays all of your folders, just starts up opened to that particular one which might save you a click or two. At the top of the file manager, you’ll see the menu bar where you can choose “Upload”:
You’ll get the typical button to choose the file with, and a status bar that will tell you when the upload is complete:
Once it is uploaded, go back to the file manager and with the file selected, click the “Extract” icon, or right click on the file and choose that option:
You can actually choose to extract it somewhere other than where you uploaded it, which could be useful for creating multiple copies or updating WordPress into multiple folders:
Now this ends up creating a wordpress folder under the one where you really want it, so I do a bit of cleanup that involves moving the contents of that folder up one level. I use the File Manager’s drag and drop to move the files, and then delete the empty folders and zip as shown in this video:
After that, the rest of the configuration is a standard WordPress setup through the browser (see: http://codex.wordpress.org/Installing_WordPress#Famous_5-Minute_Install)
Recently after an upgrade of my Plesk panel, my web site was down.
They had it fixed in a moment, and then went the extra step to send me the command to fix this myself in the future:
That simple command reset all the server config files and got all of the domains working again.
A huge thanks to the 1and1 Server Support guys and Khristian Byrd specifically !!!