According to WordPress, I wrote a total of 190 posts in 2011. To see all the articles written in 2011, simply access:
This feature is possible using one of the nicest features in WordPress called permalinks, which is short for permanent links. With permalinks, you can customize your own URL structure the way you want it. I happen to use this format:
which makes it easier for me to display articles by year, month and day. To access all articles written in 2011, I just provide the year and all articles written in 2011 will be displayed. Most WordPress users already use permalinks.
If you are not, do it early. Over the years, you’ll see the benefit of using such a structure.
The WordPress development team met last week and laid out the plans for WordPress 3.1 scheduled for release on December 15. Here are the details:
The finalized goals for WordPress 3.1 are “to have a very short dev cycle, a decent amount of testing time, and a release in mid-December. Low on new features, heavy on ui and code cleanup, and avoidance of schema changes. Save the big ideas for 3.2 where we’ll have the liberty to implement those ideas in PHP5. No schema changes and no big new APIs.”
Besides bug fixes and code cleanup, users can look forward to a new WordPress.com inspired admin bar and theme browser, as well as post templates and styles, and a separate network dashboard.
The team plans to halt new feature submissions on October 15th, followed by a primary code freeze on November 1st, and a string freeze on December 1st. The beta period will begin November 15th until the estimated final release date of December 15th.
There is not a lot of cosmetic changes, but I’m looking forward to the new Admin pages that’s similar to WordPress.com.
Spam seems to be everywhere. It’s in your email, blogs, social networks and even text messages. Spammers are getting creative in terms of getting around spam blockers, captchas and even fooling unsuspecting bloggers like myself.
A typical comment such as “Great post” or “Great article” or “I’m a little confused about what you wrote” or “Can you explain what you meant by this” don’t seem harmful. Some even manage to make intelligent comments. But if you look at the author’s link, it’s a dead giveaway.
I usually smell a comment spam a 100 miles away because of the author’s link or website. If the commenter’s website is a non-personal or non-blog website, I usually remove the link, but I let the comment stay if it’s within topic.
The main reason comment spammers leave comments on blogs is to promote their own businesses, blogs, sites, etc by means of a link back. Spammers are merely trying to improve their search rankings. One of the things I have been doing to fight this type of comment spam is to delink the spammer’s link.
Comments may seem legit and even make sense, but the commenter’s link is removed. I use the Delink Comment Author by Alex King, an excellent plugin WordPress Plugin to delink comments.
All it takes is one click of the mouse. It’s very effective.
WordPress just released version 2.0.7, ten days after releasing version 2.0.6. Why? Due to a security hole running certain versions of PHP. I just upgraded several WordPress installs the night before when I saw version 2.0.7 was out. Arg! I should have waited for a week or two. Version 2.2 will be out soon.