On Net Neutrality (2014)

There’s been a lot of hubbub about Net Neutrality again lately now that Obama has officially come out in support of it (something he supported when he ran in 2008, then seemed to not when he appointed Tom Wheeler to chair the FCC in 2013). This week I put together some notes for my students to review so that next week, we can have a class discussion about Net Neutrality and how it can affect us moving forward. After the jump, you’ll see the resources I provided to them.

Links Round Up for 03/28/11

Links Round Up for 03/20/11

Manifest Development Redesign 2011: The Portfolio

For the second part of this series, I want to talk about putting my new portfolio together. The portfolio is the most important area for a web developer because it gives the user insight into the type of work he or she does, so I wanted to do it right. It’s now in two places, and is managed a completely different way on the backend.  Let’s take a look.

My Thoughts on Twitter for Mac

I’ve been using Twitter for Mac for a few days now after TweetDeck went AWOL and started using up all of my CPU on me; I’ve got some thoughts on it. I used Tweetie (the amazing Twitter app for Macs) for a while and loved it (who didn’t?); when they stopped updating it, I stopped using it. Now that it’s back as the official Twitter app for Macs, I’m back in and have high hopes. Here’s what I think.

Manifest Development Redesign 2011: The Homepage

[singlepic id=7 w=320 h=240 float=right] Last week I launched a redesign of my freelance site, Manifest Development. I started developing it in late November, and wanted to revamp the site completely from design to content. I got some feedback from my students during one class when we were talking about the importance of a small business’ website, and I wanted to integrate that, as well as some of the new things I learned over the last two years. I’m planning on making this a multipart series, and in today’s installment, I want to talk about the most important part of a website: The Homepage.

Quick Tip: How to Move a WordPress Site

I won’t go too in-depth here, but I will describe the steps you need to take to move a WordPress website to a different host.

  1. Download all of the site files from the old host
  2. Export the entire database WordPress is using. If you’re not sure how to do that, there are instructions here.
  3. If there are existing files on the new host, back them up by downloading them. Do the same for any databases on the new host.
  4. Upload the site files from the old host to the new one.
  5. Create a new database on the new host. Each host is different, but you’ll have to create a database, a database user, and then give the database user all privileges on the new database.
  6. Import the database from the old host to the new database.
  7. Change the wp-config.php file info to the new database name, host, username, and password.

Some Things to Consider:

  • Most hosts keep the database host as localhost but not all of them. If you’re not sure what your host is, you should contact the new host’s support.
  • This is just moving WordPress to a new sever; I assume you’ve already pointed the domain. If you’re changing domains, you will also have to change all of the domain references in the WordPress database, most notably in the wp_options table (there are two references there). If you don’t change the wp_options table, your site will not work. The best way to change all of the references (most of which being in the posts table) is probably to do a Find/Replace on the .sql file in your favorite text editor after you complete step 2.
  • If you’re moving a WordPress MU/Multisite install, you will also have to configure the sever to handle subdomains. The codex has instructions on how to do that here.