If you are not database-savvy, you should definitely not be running SQL queries. It’s like trying to launch a rocket space ship (leave that to the pros). The consequences of a mishap, related to your own doing, are not worth it.

Ok, I’m going into explanation mode for the benefit of the community so they can get a bit of perspective on migrations, so bear with the wordiness.

Every site is different. I get a lot of folks that tell me:

• I just have a WP site – why is it different than anyone else?
• It’s just a simple site – why is it that instructions A or B don’t work?
• I just want to move the site – how hard can that be?

The problem with those statements is that even though we ALL run WordPress, none of us do so in EXACTLY the same way. In fact, no two sites are the same – here’s why:

1. All content (posts / pages) reside in a WP database (most beginngers / users don’t know that’s really where it is stored). But to their credit, they don’t really need to think about it UNTIL a data disaster occurs or they want to migrate their site. So basic point here is that all your data resides in a database.
2. Each user has different plugins he/she prefers. The data those plugins create, as well as the data tables, are all created in that main WP database. For example, I recently logged into a user’s site with 107 plugins. Talk about scary!
3. Over time, your database becomes less optimized as you store more data, activate / install / deactivate / delete plugins, etc. This is why users should backup and optimize databases regularly.
4. The content (posts/pages) may be corrupt but user might not know it yet. This is why users should only use quality content entered directly into WP.
5. etc. etc. etc. the list can go on and on…

So when all those factors add up, you have a very different site than the next person. Which is why no 2 sites are really the same ever.

This is also WHY most hosts will NOT touch your database and most developers will not offer such a service. Because it truly is a case-by-case service and must be handled very carefully. Hosting providers want to avoid users claiming their site doesn’t work, or X or Y plugin doesn’t work, etc. You can just imagine the possibilities, especially when the technical jargon behind what’s happening isn’t fully understood. So now we know why this is not a juicy service to provide.

Ok, so where does that leave the user?

• To be extremely careful with their awesome site!
• Understand that moving files and folders does NOT mean your database is moved too
• Plan the move step-by-step. If possible, do a test first.
• Hire someone who knows what they’re doing! It should not cost much.

If you are looking for a good source that explains how to move your WordPress site, start with the WordPress Codex. I found most other sources on the net out-dated, inaccurate, untrustworthy, or just wrong.

I tried to upload an video to WordPress today and realized that I needed to increase my WordPress PHP memory limit. This is an easy step and can be performed by beginners.

1) Simply open up a text editor such as TextEdit or Notepad++.
Note: MS Word is NOT a text editor.

2) Copy the following into a new file:

memory_limit = 96M
post_max_size = 96M
upload_max_filesize = 96M
file_uploads = On

3) Save the file with the following name: php.ini
Note: If you are using GoDaddy, you may have to name it php5.ini instead as they upgraded their servers to run PHP5. But why would you be on GoDaddy anyway? :)

4) FTP to the root directory of your site. This is where your wp-admin and wp-content folders reside on the server. Upload the php.ini file to the wp-admin directory.

5) That’s it!

Let me know if it worked for you? If not, I may be able to offer some guidance. Enjoy.

Yesterday, I was looking for ways to grab the current category ID so that I could display a custom image at the top of each archive page. While there are many different ways to achieve this, I did not want to run an additional query. After reviewing the solutions mostly, I stumbled upon this gem on the WordPress Codex:

<?php get_query_var( $var ); ?>

With that template tag, you can simply pass the variable cat to grab the Category ID of the current category (i.e., within archive.php):

<?php echo get_query_var('cat'); ?>

You can use it to grab the Page ID of the current page as well (i.e., within page.php):

<?php echo get_query_var('page'); ?>

That snippet will accept any parameter that can be used within the WP Query class.