One of the most powerful comment-editing solutions for WordPress just got a major upgrade. Ajax Edit Comments enables your visitors to “self-edit” their own comments, greatly improving the usability and “coolness” factor for your site. And with the latest upgrade, AEC gets even better, with a revamped popup box, easy “undo” options, comment-blacklist feature, new icon themes, increased security and tons more.
Going the self publishing route with our book meant that we didn't have a big fancy book editor going over our text. We of course strive to be the best writers we can be, but we are clearly better WordPress wranglers than we are wordsmiths. If you find any typos or any other kind of mistake in the book, you can submit them here in our new Errata section. We'll be incorporating all fixes into subsequent releases of the book (which as book buyers, you get for free!). Much appreciated!
WordPress 2.9 should really be a nice release. Check out this article for some interesting stuff like
the_post_image(), the trash can, image editing, oEmbed, and some other cool features and improvements.
Jeff and I launched this blog back in May of this year, after we decided we were going to self-publish the WordPress book we were working on. After weighing all the options, we decided going it on our own was best because we would have 100% control over everything. From the content of the book, to the layout and design, to the blog, sales site, everything. Today, it all comes together!
One of the best ways to ensure strong security for your WordPress-powered site is to secure its foundations during the installation process. Of course these techniques can be implemented at any point during the life of your site, but stetting them before the game starts prevents headaches and saves time. We’ll start with the WordPress database..
I think one of the biggest WordPress myths is that you need a bunch of plugins to control comment spam. Pretty much all of the posts out there on preventing WordPress comment spam are telling you to install some list of “must-have” anti-spam plugins. Some authors insist that you need only a few “choice” plugins, while others advise you to load up on everything you can get your hands on. Such advice is all well-intentioned, I’m sure, but it’s all based on the assumption that plugins are actually necessary to control comment spam. They’re not. WordPress is well-equipped to handle the job all by itself. Plugins may provide additional anti-spam functionality, but they are by no means essential to running a spam-free site.
Tim Haslam shares a very nice theme called "One Day At A Time" designed to promote awareness of breast cancer. Check out the demo, grab yourself a free copy, and support a good cause.
Editor's note: 404 link removed.
The month of November is National Novel Writing Month (or #NaNoWriMo). Joel Goodman is participating and thought that the WP Typo theme would be a good fit for it. Joel has expanded upon the theme by adding a settings page with various typography options, better integrated user registration, and some custom design tweaks.
You don't want to go putting HTML tags directly into post titles. It might show up OK on your own site, but it can be problematic. For example, your titles through RSS will show the tags as next, not render them. I was wishing for a plugin to handle this better, but until then, here is almost-as-simple way to go about it.
In this one we cover the GPL and how it benefits WordPress, why WP is under the GPL, commercial themes, how the GPL fosters innovation, creates value, and affects themes and plugins.
I certainly learned some stuff about the GPL. Like 1) You can sell/profit from themes that are GPL and 2) Anything built around an existing GPL product must also be GPL.
With WordPress, there are various distinct types of page views. For example, there are category-archive views, tag-archive views, author-archive views, date-archive views, single-post views, single-page views, and so forth. And of course you know that you can target single-post views in your theme template with the conditional tag,
One of the easiest ways to display your FeedBurner subscriber count number in plain text is to use the Feed Count plugin by Francesco Mapelli. I have been using this plugin at Perishable Press for a long time, and it has always been great. Unfortunately, Francesco's site seems to be suffering from malicious behavior these days, with tons of spam comments, weird files that are automatically downloaded to your computer, and even one of those scary warnings from Google: "Reported Attack Site," or whatever it says.
In any case, the Feed Count plugin is too awesome to let disappear into the ether, so it will be hosted here at Digging into WordPress until Francesco's site checks into a rehab center and cleans itself up. Hopefully that will be sometime soon. In the meantime, to download a squeaky-clean copy of the Feed Count plugin, simply click on the title of this post.
Vote on your favorites. I like the brownie bites!
Inside the loop, if you use the function the_date() to display the date the post was published, you may run into trouble. Specifically, if there are two posts published on the same day, the second one will return nothing for a date.