WordPress Plugins are a great way to extend your blog. With literally hundreds, even thousands of plugins available for WordPress, you can make WordPress do pretty much anything you want it to do. There are plugins to get blog stats, Twitter apps, show popular posts, even to help you make your blog SEO friendly. And these are all great to have and use. I use quite a few of them myself.
However, there are a few things you need to be careful of when using WordPress plugins. One of these is your blog’s load and response times. If you are running a lot of plugins, especially ones that load information to your blog when someone visits, this can severely put a damper on your blog’s load and response times. This can deter visitors to your blog from coming back, as a lot of us are impatient with load times on a broadband connection. Those on dial up connections (yes there are still a few of them out there) may never bother with your blog again.
Another thing to be wary of is how much bandwidth a plugin uses. A friend of mine on Twitter recently had an issue where her host took down her blog stating that she had used too much bandwidth. As she told me she does not have a monthly bandwidth limit, I was surprised until she said that her host claimed that she used so much bandwidth that she took the entire server down. She knew it had to be one of the plugins she was using, and when the host finally put her blog back up, she narrowed it down to StatsPress. She disabled the plugin and has not said anything about having any issues with bandwidth usage since.
However, it just goes to show that you do need to be careful. While I would not say StatsPress is a bad plugin (I do not use it myself, I use WordPress.com Stats and my WordPress.com API key), I would caution anyone who does decide to use it to watch their bandwidth consumption closely to see if there are any changes or any spikes in consumption once the plugin is activated.
I admit, it is possible that my friend was running an older version of WordPress or even an older version of the plugin which could have been exploited by a hacker, thus causing the sudden bandwidth usage spike. I am not discounting that possibility. However, I have seen plugins cause excessive bandwidth usage, slow load/response times, and in some cases, even break WordPress. So use caution when adding plugins.
Check the comments left about the plugins, check the rating the plugin has been given. Make sure when installing a new plugin that you are installing the latest version. Be aware that if the plugin states it has not been tested with your current version of WordPress or says it is compatible up to a version of WordPress lower than what you are using, that it is a possibility that it could break the blog until it is removed.
By all means, use plugins to make WordPress do what you want it to do. Just make sure you keep an eye on your blog to make sure they are not causing issues.
Posted in Plugins, WordPress.
Tagged with Plugins, WordPress.
One of the things I see a lot is people talking about hosting their blogs. I have more than one person on Twitter that I follow that talks about website/blog hosting. One thing that they all fail to mention: just because you pay for your hosting does not give you the right to do whatever you wish with your hosting.
Just like the free website hosts like Tripod and Angelfire, and the free blog platforms again like Tripod, Angelfire, LiveJournal, WordPress.com, Blogger, etc, paid hosts also have “terms of service” or “TOS” attached to them. Just because you are paying them does not mean that they will not remove your site, suspend your account, or ban you from their service for violating their TOS.
Free blogging/website hosts generally have TOS that include not removing their ads (unless you pay for an upgrade), no paid ads (aka, you can’t monetize your site or blog), no pornography (although it seems the Blogger does allow risque content, as long as you tell Blogger about it first), etc. For example:
- WordPress.com does not allow any sort of monetization of their blogs. This means no AdSense, Chitika, paid posting, nada. They do put ads on some of their blogs, although personally, I have yet to see one.
- Tripod & Angelfire which offers both straight website hosting & a blogging platform do not allow you to do anything that removes the ads from your site/blog, nor do they allow any sort of adult content.
But paid hosting will also have TOS that may prevent you from keeping your site/blog up and running. Commonly these include things such as:
- Banned scripts. Some hosts have lists of scripts that are not permitted to be run on their servers. These include anything from PHP scripts that are outdated and insecure (such as PHPFanBase), to blogging platforms that are outdated and insecure (such as Greymatter). If you are unsure if a script is allowed, contact tech support for your host to make sure.
- Adult content. Contrary to popular belief, not all paid hosts allow adult content. I know someone who found this out the hard way when she set up a friend of hers with a website that had burlesque dancing videos as part of the content. They lost their site within a month of setting it up due to the no adult content rules.
- MP3 & warez files. These are two biggies. I have yet to find a host that allows them. Both software files & MP3 files generally have to be able to be proven to be yours to distribute – meaning you hold the copyrights to the files and you were the creator of the content of the files. If you didn’t write it/record it/program it yourself, you’ll probably lose your hosting if you’re found to have it on your site.
- Plagiarism. Think snagging other people’s blog posts won’t get you booted from your paid host? Think again. There are numerous ways to find out where a particular site is hosted and it is very easy to let the tech people at that hosting company know that you’re stealing content from others. If you aren’t going to write your own stuff, don’t bother.
Yes, the TOS for your hosting, whether free or paid, is long, boring, and filled to the brim with legalese. But it is important to know what your TOS allows and what it does not. Pleading that you did not know will not get your site turned back on.
Also be aware that some hosts claim ownership of your domain if they registered it for you. Not all hosts are nice enough to turn that domain name over to you if you leave them. I have lost domains that I wanted to keep because the hosting company would not let me have them. A good, reputable host will give you the domain because you paid for it (even though a lot of them say it is free with your hosting, it is not) with your hosting package. However I have seen a few disreputable hosts that because the package listed the domain as being “free” with the purchase of the package would not turn over the domain name when asked. So if you lose your site with a host, you may not be able to get your domain name from them. This is something else you will want to check the TOS for, and if it is not mentioned, ask them before you host with them how they handle domain names if the customer wishes to transfer. If all else fails, register your domain yourself and tell them you have in existing domain you want to use with your hosting account.
Another thing – always make sure you have backups of your site/blog files to make moving to a new host easier. I see a lot of people who whine and cry on Twitter because they lost their blogs/sites for whatever reason and did not have backups of files/databases so they could not just go somewhere else and set it all up again. I have even been on forums where someone has come into the forum complaining that their blog host locked them out of their blogs because of something that was posted that the blog host felt was out of line with the TOS and would not grant the blogger access to get their database so they could take the blog elsewhere.
Now I realize that sometimes it is nothing to do with the above that causes you to lose your hosting. Sometimes the hosting company goes under and you are left to scramble to find new hosting. This is just another reason to a) know what happens to the domain if the hosting goes bye-bye and b) keep backups of your site/blog.
To make a long post short – stay hosted – check your TOS, go with a reputable host that is transparent about what will happen to your domain if registered through them and you leave or lose your account due to TOS violations, and always make sure that you have backups of your site/blog so that you can easily go somewhere else if necessary.
Posted in Blog Hosting, Blogging Tips, Blogs, Domains, Free Webhosting, Web Hosting.
Tagged with Blog Hosting, Blogging Tips, Blogs, Domains, free hosting, hosting, paid hosting, site hosting, terms of service, TOS.
WordPress has made version 2.9.1 available today as anyone who has logged into their dashboard on their self-hosted WordPress blog has probably already seen. If you haven’t, the upgrade is there. Don’t forget to do a database backup just in case!
This release addresses that pesky scheduled post issue where scheduled posts did not properly process. So if you use scheduled posts, try this new version of WordPress – your problems should be fixed!
There is one issue however that I cannot seem to get a fix for. That is the issue with the WP-Backup plug-in. You see, I schedule my backups for once per day to be emailed to me at my Gmail account. However, they are not being emailed to me. At all. And when I log into the backup area, it shows me that my next scheduled backup is anywhere from 2 hours ago to 3 months ago. I am not sure if this was an issue that went with 2.9 or what, but I am hoping that the 2.9.1 upgrade will fix the issue!
Posted in Plugins, WordPress.
Tagged with plugin, WordPress.