I should blog more often (among many other things I should do more often). At least, then I'd probably remember the naming convention I use for my posts, since I like to name them by date. Ah well.
A couple years back, I created a custom
This year, due to some things, I tried out WordPress and wanted to switch the site to it after liking it. Reality soon set in. For some reason, I couldn't access the site's CPanel, so I (thought I) couldn't upload WordPress. My connection isn't the most stable in the world, and after trying to upload it via
My friend is a busy person, and when he got round to it, he had the same issue, and contacted the provider. He told me he'd gotten round to getting the issue fixed, but on my next attempt to use the CPanel, the same thing came around. I contacted him, but decided to try to get the WordPress working myself. Uploading via
Today, I got an idea: Since the webhost has internet, I could download WordPress remotely and unpack it on the server. I got a solution for downloading the archive and created for unpacking it, but I kept getting errors. When I downloaded Unzipper, I also got problems unpacking. So I cooked up my own script for the remote download. Once I confirmed that
fopen wrappers were built on the webhost, it became a simple issue of opening the WordPress download with one file pointer, and copying it to a local archive in 8kB chunks. Unzipper helped greatly with unpacking WordPress (zip archive), and I uploaded a wp-config.php file, and now WordPress' installed! Owing to the instability of my connection, uploading themes has been a challenge, but WordPress' ability to download themes for itself has come in handy. I'll start migrating the site to WordPress and soon move the whole to WordPress. And yes, another attempt to upload a theme to the site just failed. Later.