Planet WordPress — the Epicenter of Everything WordPress

I’m hoping that my boss Matt Mullenweg sharing the legal opinion on “Themes are GPL, too” will put the issue to rest for the majority of the community (emphasis mime):

“PHP in WordPress themes must be GPL, artwork and CSS may be but are not required.
…
Even though graphics and CSS aren’t required to be GPL legally, the lack thereof is pretty limiting. Can you imagine WordPress without any CSS or JavaScript? So as before, we will only promote and host things on WordPress.org that are 100% GPL or compatible. To celebrate a few folks creating 100% GPL themes and providing support and other services around them, we have a new page listing GPL commercially supported themes.”

The legal opinion was provided by Software Freedom Law Center. Council James Vasile provided the findings and blogs at hackervisions.org . James also has posted about this on his own blog in the article “CMS Themes and the GPL“. As I commented there, my fear is:

“people read what they want to get out of it, and case law is the only thing that moves them.”

The legal finding and unchanged policy  are consistent with the intentions of the WordPress developer community and what has been promoted for the four years I’ve been involved.

Talking about licensing really is the suck. Matt’s article became necessary lately as some commercial theme developers have been very aggressive to WordPress community members, who have shared theme code as allowed by WordPress’s viral GPL v2 license.

It frustrates me when I read commercial theme developers complaining about people “stealing” their themes after the thousands of hours they have worked. They make no mention of the hundreds of thousands of hours others have worked on WordPress (counting on the  GPL protecting their freedoms ).

The incredibly exciting news is seeing the various commercially developed and supported themes embrace the GPL in the last 9 months. Theme collections like ThemeShaper (Thematic FrameWork), StudioPress (previously Revolution 2),  and WooThemes are all 100% GPL — those are just the ones I’m familar with, be sure to check out the theme offerings of the other commercially supported GPL themes.

This is a response to an article written by Daniel Jalkut, titled Getting Pretty Lonely.

I think there is one critical point that we all should agree on — developers like to be compensated for their work, even those of Open Source and Free Software.

Some assume that GNU GPL makes it almost impossible or at least very hard to earn fair compensation for time invested in developing the software, while “Liberal” licences allow the freedom to determine (and guarantee) the compensation through controlling the distribution.

The reason for this is the current implementation of the competition-driven capitalism which has made the concepts of donation and freedom to compensate complete bizarre in the context of how businesses work these days.

Just imagine the developers of GCC receiving compensation every month through voluntary donations from Apple and other commercial entities that use and benefit from it. All this would require is a “GCC Developers’ Association” which would take care of distributing the money to all the developers in proportion to their contribution. The total amount of hours spent developing the software everyone month is pretty easy to estimate.

OS X would become O(pen)S X and Windows would become Open Windows. Both Apple and Microsoft could still charge $150 for their “genius bar” / support services, and at the same time gain the whole world of developers scratching their own itches and improving the software.

It is so much easier to reason paying a real person for their expertise in solving computer problem than to a corporation that aims to get maximum profits for the lowest investment.

Software licensed under GPL excludes the problem of scarce resources, because the incentive to improve the software comes from the practical needs of its users. In case of GPL the work done is done forever for everyone — solutions once found are always there to be built upon.

Now you can download bbPress 1.0 Final, the latest release of the excellent forum software by the creators of WordPress. bbPress is the ideal way to integrate  a forum with your WordPress blog.

bbPress is a simple forum software, easy to use, easy to administrate, and is very fast and clean. It has some powerful features and is highly customizable and WordPress bloggers will find the same WP goodiness and feel when they use bbPress.

We used bbPress for our forums earlier and here are the top 10 reasons to install bbPress. Some key highlights are pretty SEO optimized permalinks, lots of plugins and themes, open source, lots of feeds, Akismet spam control, integrated Gravatars, and lots more.

Download bbPress now and start a new forum for your site in minutes. Remember bbPress requires PHP 4.3 or greater and MySQL 4.0 or greater.

Copyright 2009. Quick Online Tips. All rights reserved.

Related Posts

1. Top 10 Reasons to Install Free bbPress Forums
2. Free bbPress Forums with Slug Based Permalinks
3. Download WordPress 2.8 Final

Recently, the Dev4Press and Weblog Tools Collection blogs made posts about integrating plugin changelogs into the Plugins dashboard. This functionality was something I was already doing in the SEO Ultimate plugin, so I thought I’d share my technique for doing this. (My method is different because it’s simpler and it integrates directly into WordPress’s update message.)

Here’s what an inline changelog looks like when implemented:

As you can see, a small notice like this helps users know at-a-glance what’s new in your plugin update.

Here’s the code you can incorporate into your plugin:

<?php
function my_plugin_update_info() {
	if ( $info = wp_remote_fopen("http://www.example.com/my-plugin-updates.txt") )
		echo '<br />' . strip_tags( $info, "<br><a><b><i><span>" );
}
add_action('in_plugin_update_message-'.plugin_basename(__FILE__), 'my_plugin_update_info');
?>

Of course, to keep plugin users happy, be sure that your inline changelogs are informative and unobtrusive. Happy coding!

(Plugin users, if you’d like to see this feature implemented in your favorite plugins, you could try sending the plugin author a link to this post! You could also check out the new Changelogger plugin.)

• WordPress vs. WordPress MU: A Comparison
• Announcing the “SEO Ultimate” Plugin
• The WordPress Plugin XHTML Hall of Shame
• Is Your WordPress Theme Plugin-Friendly?
• WordPress Plugin Competition 2.5

Ever since version 2.7 WordPress offers the option to adjust the number of comments on each page. From SEO's perspective, this is not very smart, as there were many articles and discussions about this topic in the past. If you turn off the comment pagination, the empty HTML fragment is still in the source code of the page.

Unfortunately, the classes that respond with CSS are the same as those from the normal page and post pagination.
If you have a theme in which the outer container of pagination has a frame or a background color, then you can see the empty container. Here are 2 screenshots with and without activated comment pagination to illustrate what I mean:

Another annoyance would be if .pagination has a margin-bottom, which would also have a negative effect on the layout. What can you do about it?

WordPress stores the setting of the comment pagination in the database table options under page_comments. Value 1 means on, value 0 means off. By doing so you can hide the pagination in comments.php if it is not turned on:

<?php if ((int) get_option('page_comments') === 1): ?>
	<div class="navigation">
		<div class="alignleft"><?php previous_comments_link() ?></div>
		<div class="alignright"><?php next_comments_link() ?></div>
	</div>
<?php endif; ?>

The query checks whether the comment pagination is set to (1) and displays the navigation. If it is set to (0) it will not display the navigation. On the other hand, if it is turned off, WordPress doesn't need to execute the two functions previous_comments_link() and next_comments_link().

So the guys who run WestHost and provide me with my awesome WordPress hosting, are a sister company of the guys that run VPS.net, and they recently gave me a VPS to play around with a bit. I kinda liked how easy it was to get a VPS up and running with a TurnKey Linux / WordPress image on it, the only issue was it was version 2.5 and needed updating.

Though they told me that would be changed pretty soon (meaning the image will support a higher WP version), I made a quick video on how to do all this:

I have to say it was a pretty nice experience, if you're looking for a VPS, this is pretty much top notch stuff (being a nice combo between a VPS and cloud based hosting) and it isn't expensive.

This is a post from Joost de Valk's Yoast - Tweaking Websites. A good blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Use WestHost, and you'll never have issues again!

Playing around with VPS.net

Normally when I set up plugin-level SEO on a WordPress blog, I’ll need 5-8 plugins to provide all the desired SEO functionality. Wouldn’t it be cool if there was one plugin that incorporated all that functionality and more into one easy-to-use suite?

That’s the goal of SEO Ultimate, which is a free plugin I’m developing on behalf of SEO Design Solutions.

Right now the plugin is in its early stages (currently at version 0.6). There are many more features yet to come; as more functionality is added, I expect SEO Ultimate to become the all-in-one WordPress SEO solution of choice for more people as time goes on.

Features

Current functionality includes the standard All in One SEO Pack features:

• Title rewriting
• Noindex checkboxes
• Meta editing
• Canonical tags
• Post meta box

SEO Ultimate also has these additional capabilities:

• 404 monitoring
• Linkbox insertion
• Settings import/export functions

Upcoming features include robots.txt editing, 301 logging, XHTML validation status monitoring, and much more. (If you install the plugin now, you can get these features delivered to you on a regular basis via WordPress’s semi-automatic plugin updater!)

I’ve also incorporated these extra features into SEO Ultimate:

• Inline changelogs
• Readme changelog
• Footer branding
• WordPress 2.7 menu integration
• Integration with WordPress’s Help system
• Inline phpDoc documentation

Auto-Installer

Also, be sure to check out this cool auto-installer system I invented. Just type in your blog’s URL, click “Launch Installer,” then click “Install Now,” and voila, SEO Ultimate will be installed on your blog! You can then enable it by clicking the Activate link.

Try it out:

You can also download the zip file. SEO Ultimate requires WordPress 2.7 or above.

Let me know what you think!

• Tip for Plugin Developers: Inline Changelogs
• The WordPress Plugin XHTML Hall of Shame
• The Ultimate PageRank Sculpting Guide for WordPress SEO
• Top 3 Underrated WordPress Plugins
• Is Your WordPress Theme Plugin-Friendly?

So, we've finally got an official word on this, the one sentence summary by Matt reads:

PHP in WordPress themes must be GPL, artwork and CSS may be but are not required.

Ok, so that's the final truth, because the Software Freedom Law Center (who are of course absolutely NOT partial in this, even though they're called the "Software Freedom Law Center") said so. Nice. Really nice actually as all I've done and released for WordPress, ever, has always been GPL, and I chose to work with Brian because his themes were GPL and the others were not (at the time).

You'd think I'd be happy, and I am, sort of. But I've got an itch that needs scratching. With this final statement, there's also a new page on WordPress.org for Commercially supported GPL WordPress theme makers, and StudioPress is among those of course.

So, all the theme makers who decide to go fully GPL (their artwork and CSS included), can get listed on that page. Well, good for them. You'd think, that by now, Matt and Automattic would have been smart enough to know who their friends and who their foes are. I'm not saying these theme makers aren't their friends. But there are these people out there, who have been building things that have been GPL all the time, who do NOT get that recognition.

Of course, we plugin authors get to host our own plugins on wordpress.org, and we can get links back to our site etc. But where's the page for commercially supported GPL WordPress PLUGINS Matt? Don't you think it's time you started treating the plugin authors the same way as the theme authors? Or do we have to start a theme war for that first?

And yes I do have an interest in this, and yes I am planning on going the "commercially supported GPL" route with some of my plugins, just because keeping them all free doesn't make any sense any more. Free does other things, just as Chris Anderson says, it has helped tremendously in getting my name out, but "free" doesn't make me rich, far from it even. I can be quite honest in that so far, in working with Brian on StudioPress... Well let's just say the effort to gain ratio is a LOT better.

The fact that people are able to build business models around a project, is the reason that projects grow. The premium theme market, started by Brian but also greatly pushed by my buddies at WooThemes and others, has increased development on themes tremendously: it has done the entire WordPress community a lot of good. (BTW, read Daniel Jalkut's post on the GPL vs liberal licenses, it's a very good read and offers some nice food for thought).

So my plea, to you, Matt, is to help people build up viable business models around WordPress Themes AND Plugins. For several reasons, including the fact that I'm loving to be able to make a living with it, but also because I think it will do the community a lot of good. And ow yeah, I'd love a haiku on WordPress.org about me too!

This is a post from Joost de Valk's Yoast - Tweaking Websites. A good blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Use WestHost, and you'll never have issues again!

On the GPL, Themes, Plugins & Free.

The WordPress Plugin Competition is the best moment of the year, plugin wise. This year’s edition is still running till the end of the month of July and as of writing, there are about 10 plugins (with some really interesting stuff).

Still, new plugins are released every day. Why aren’t these authors joining the competition?

Participating in the competition is

Instructive: you *will* learn something. Guaranteed. Or refunded. Basically, joining the competition is asking for feedback, so judges will tell you what they liked, disliked, loved and hated. I will be an official judge in this competition and I will definitely tell you what looked cool and what sucked in my opinion (for the record, read my review of last year’s edition here and there)
All the feedback you’ll get won’t be golden rules for sure, they’ll be personal points of views, but there has to be something to be learnt from it.

Exposing: definitely, participating will give you good exposure. You will end up being listed in various places that will blog about the Competition, including on very high traffic blogs. More exposure means more users for your plugin, obviously.

Motivating: as the competition deadline will approach, you will get more comments from readers, and hopefully more ideas for your plugin. Plugin authors themselves cross-pollinate each other.

Rewarding: you’ll get exposure, feedback, and eventually you might be a winner of some prize or cold cash. While this should probably not be the main reason of your participating, well, that’s the icing on the cake, right? :)

Participating in the competition is not

For the pros only: please don’t be too shy and just think “I’m not good enough, this is my first plugin, competition is not for me”. So, you’re a beginner, and so what? Nobody is going to laugh at you, you will not be mocked or anything, and everybody was a n00b at some point. This is a unique opportunity to have your plugin and your code reviewed by rather experienced coders and WordPress users.

Time consuming: it’s not like participating will require you to dedicate more time to your plugin or to support requests. Once your plugin is released, you’re just one tiny blog post and a mail away from being officially a competitor. Really, a short announcement is all it takes. The competition rules are no extra burden.

What you should do now

If you’re a plugin author, well, JOIN! Don’t release a plugin in the next few weeks without getting it listed in the competition.

If you know people who do or will release plugins, tell them about the Competition and explain why they should join. There’s just no valid reason not to.

Blog, tweet, reblog and retweet about the competition. I’m sure there are more reasons to participate than the ones I’ve listed here, so post about them.

If you’re an internet business and are more or less related to WordPress (premium themes or plugins, hosting service, ad platform…) or just anyone cool, consider sponsoring the Competition and tell your customers and readers about it. That’s cheap exposure and positive karma for you (for this matter, please get in touch with Mark from Weblogtoolscollection.com)

Share This

(cc) Ozh for planetOzh, 2009. | Permalink | No comment | Add to del.icio.us | splogmenotplz
Read more posts tagged with: Competition, Plugins, WordPress

Related posts

• Prepare For WordPress Plugin Competition 2009 (2)
• 2008 Plugin Competition Review, Part One (12)
• 2008 Plugin Competition Review, Part 2 of 2 (12)
• Your Wordpress Feed, on Steroid (3)
• WordPress, Duplicate Content, and Wrong SEO Plugins (22)

Feed enhanced by Better Feed from Ozh

I’ve got tonnes of feedback about Ajax Edit Comments and several of these are requests for new icons that the plugin uses. I’m thinking along the lines of having different sets of icons and so this email goes out to everyone asking for recommendations on what icons I should use for the plugin.

If you’re interested in knowing what the icons are required, check the images folder of the plugin. I’m planning at least two sets of icons for the plugin, so please give me as many suggestions as possible so that I can select accordingly.

Remember that the icons need to be GPL or royalty free. I cannot use paid icons for the plugin.

Visit: Techtites - Your Daily dose of all things tech!

Matt Mullenweg, the founder and lead developer of the WordPress blogging platform, emailed the Software Freedom Center recently asking about the legality of WordPress themes being licensed under copyright not compatible with the GPL, and they’ve now responded, which Matt has published on the WordPress Development Blog.

The conclusion? The PHP files in WordPress themes must inherit the GPL, but CSS and Images do not. From the email:

The PHP elements, taken together, are clearly derivative of WordPress code.

Obviously, since many premium theme developers, including iThemes, have adopted the GPL completely for their themes, including CSS and Images, this news doesn’t make a big difference for us.

But because neither side can claim they were 100% correct, the declaration is bittersweet to those on both sides of the issue.

Those claiming that themes must be completely covered by the GPL can no longer claim that:

… the images and CSS are not [subject to the requirements of the GPL]. Third-party developers of such themes may apply restrictive copyrights to these elements if they wish.

But those claiming that they can license their themes — in their entirety — under a restrictive license seem to have been in the wrong as well. Or were they?

In the last paragraph of the email, it seems there is, at the very least, a potential loophole.

Finally, we note that it might be possible to design a valid WordPress theme that avoids the factors that subject it to WordPress’s copyright, but such a theme would have to forgo almost all the WordPress functionality that makes the software useful.

If it’s possible, though not ideal, for a WordPress theme to run independent of WordPress itself, then one must assume (at least from the wording of that paragraph) that the PHP code isn’t necessarily required to be subject to the requirements of the GPL.

Obviously, this is the first time anyone has been able to speak about the issue with authority, so this is helpful. But I’m afraid this story isn’t over yet.

I, obviously, support licensing themes (free or paid) under the GPL. But despite this latest news, I’m still very reluctant to say that the legality of the issue has been completely cleared up. There are still too many questions, and not nearly enough answers. One thing is for sure, theme authors have been adopting the GPL all over the place lately. And WordPress just launched their commercial GPL theme directory today. Perhaps the legality of all this GPL talk doesn’t even matter any more.

What do you think?

Related posts:

1. PageRank, Technorati, and Free WordPress Themes
2. iThemes, WordPress, and the GPL
3. Premium WordPress Themes?
4. IE Double Margin Bug
5. Community, Self-Respect, and Free WordPress Themes

Changing the more link in a WordPress theme is easy. Just open your theme files and change it. But, if you’re writing a plugin to change this or want to preserve your theme’s code (e.g., child themes), you need a way to easily edit this.

I’ve seen some themes add their own more link filter hook, but this is unnecessary because WordPress 2.8 introduced the_content_more_link filter hook. Maybe this post will help those theme authors cut back on an extra filter hook when it’s not needed.

This will allow us to easily overwrite the default.

What is the more link?

When writing a WordPress post, you can cut the text off at any point by adding in this code:

<!--more-->

If you’re using a theme that shows the standard full post on the home/blog page of your site, this will cut the article short at the point you added the code. It will also add a link to the single-post view where the reader can continue reading the post.

Using the_content_more_link filter hook

What we want to do is change our theme’s more link text, but we need to do this the appropriate way, and the appropriate way means not hacking up your theme author’s code.

Let’s assume our theme’s more link outputs “(more…)” when we add the <!--more--> link within the post editor. Maybe we don’t like that message too much. We’d like to change it to read “Continue reading →” instead.

Open your theme’s (or child theme’s) functions.php file and paste this code in:

<?php

add_filter( 'the_content_more_link', 'my_more_link', 10, 2 );

function my_more_link( $more_link, $more_link_text ) {
	return str_replace( $more_link_text, 'Continue reading &rarr;', $more_link );
}

?>

That’s all there is to it. Enjoy your custom more link text.

So the WordPress development meeting took place today and boy was the atmosphere conducive to discussion. Lots of things discussed while new ideas were generated. Unfortunately, you get a bunch of developers into a chat room and when you announce an idea or feature, the talk immediately turns into implementation which results in an unruly court that needs to be settled down to get back on track. But, the meeting went on and the following are the bullets points that were discussed regarding WordPress 2.9. Jane is currently working on putting the feature list together to be voted upon in a poll that will be published on the WordPress development blog to get a sense of where the end users priority lies.

post thumbnails, mark: The ability to use a custom field key to assign a thumbnail image to a post excerpt.

media albums, mark – The addition of photo albums to display images. I believe this to be different from galleries.

bulk media import API

make adding embeds easier (like viper plugin) – The inclusion of popular shortcodes to support major video sites like YouTube etc.

enable most media settings as defaults that can be overridden on a per image/file or per-use basis.

cropping, resizing, and rotation (in 90 degree increments) for image uploads, filtering – This would be the extend of basic photo enhancement. As a few others said, we really don’t want to see Photoshop in the WordPress write panel for images.

Custom Image Sizes. Instead of hardcoded thumb, med, large (manually configuring maximum image sizes for small, thumbnail etc)

lightboxing images: It’s been decided not to add Lightbox as a core feature just yet.

post types: For WordPress 3.0

page exclude plus reorder for blog nav: nikolayb – The ability to easily remove a page from showing in the navigation menu while also providing UI to sort the order of the menu.

media metadata – The addition of tags and categories to sort media.

uploader feature: ability to choose from most recently used/most often used/marked as favorite files

more default shortcodes. check top ten from wp.com. slideshare and any place that advertises wp.com shortcodes

importers (specifics TBD)

and UI header brushup and uploader UI – I imagine this has to do with the header poll that was announced after 2.7 was released.

That’s about it. Not sure what next weeks topic will be about but if you want to suggest one, you can by visiting the WordPress development updates blog. If you would like to participate in the chat next week, install IRC or an IRC compatible client and connect to the following IRC server.

chat.freenode.net or any random server on the Freenode network and then join this channel at 5PM Eastern time on Wednesdays. #wordpress-dev.

Related posts:

1. WordPress 2.8.1 Beta By End Of The Week
2. WordPress Needs To Revise Post Revisions
3. Wanna WordPress Wiki

I've just agreed with my buddy Daron Babin of WebmasterRadio.FM to be the host for a weekly WordPress podcast, no names or time slots decided yet but I'm so excited about the news that I wanted to share it with you all!

All your suggestions for names, topics and guests are welcome in the comments!

This is a post from Joost de Valk's Yoast - Tweaking Websites. A good blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Use WestHost, and you'll never have issues again!

Yet Another WordPress Podcast

Before making the domain move the other day, I made a mistake by deleting something I shouldn’t have from the database. It was the comment_karma field located within the wp_comments table. A long time ago, I remember installing a plugin called Comment Karma which enabled visitors to rate a comment up or down thus promoting the best user rated comments to the top.

I thought that by installing this plugin a long time ago, that it had created this entry in my database. Thinking another plugin left its stuff behind in my database, I removed it only to find out that removing it broke my commenting system to the point where the incrementer broke. To make matters worst, I didn’t do a database backup since I thought I was removing something plugin related. However, thanks to Michael Torbert, he helped me put the comment_karma field back in its location and once I did that, everything worked again.

So, when I dived into the WordPress-Dev IRC channel to see what this field is used for, someone said it was not used by anything in core and Michael told me he couldn’t find anywhere that field was being used. But, if it was not being used in core, why would it cause the commenting system to break when it’s removed?

The overall lesson here, don’t do ANYTHING to your database unless you backup first. Complacency is your enemy.

No related posts.

Over the past few days, I’ve been helping out someone with their blog as it’s become compromised by some nasty injection code. This code is in his php files, in his content, and his database. I have no idea how it happened except that his plugin and theme folders had a permission level of 777. On top of that, I discovered some malicious themes within the themes folder containing the base64 encrypted code which I believe to be the hidden spam links.

I told him to do a fresh install the first time around which is what he did via Fantastico only to have the problem resurface. Again, the themes and plugin folders had a permission level of 777 and I found out this was because of a plugin he had installed called One Click Updater.

Currently this plugin only uses direct file access to update and install plugins/themes, so you’ll need to make the “/wp-content/plugins/” and “/wp-content/themes/” folders writable by PHP for this to work.

Either he didn’t know he could do the same thing in WordPress since version 2.7 or core plugin upgrades didn’t work. In any case, I believe the permission level to be a source of the problem. As it turned out, his database was clean but certain files located within rogue themes were injecting the encrypted code into all of his content which was only viewable by checking the source code of the site. In the end, I finally exported his site via the WXR export feature, gave him a fresh install of WordPress, imported the WXR file and told him to stay 5 miles away from the One Click Update plugin or any plugin that needs permissions for folders to be 777. Once his fresh site was online, all traces of the spam links were gone meaning his database was clean, his WXR file was clean, and he was a happy camper.

Now you might be wondering, why didn’t this guy do all of this himself? Well, he is in a unique situation where the only thing he owns is an N95 phone powered by S60. He maintains and writes content for his blog all through this phone. It’s his only connection to the digital world. So, uploading and doing things that come easy on a desktop PC is not so when all you have is a handheld phone. I give this guy a lot of credit.

To bring this back full circle, I encourage you to read Chris Coyier’s experience where he explains how his notable site CSS-Tricks ended up with hidden spam links within the content of the site and how he was able to get rid of them.

I guess we should be checking the source code of our own sites more often?

Related posts:

1. This Is Not Spam

Yesterday, while working on a project for Springer Uitgeverij, I was amazed to find out there is no simple RSS Shortcode plugin, that simply allows you to do this:

[rss feed="http://yoast.com/feed/" num="10" excerpt="false"/]

And then that would show the feed you'd specified. Well, now there is: the RSS Shortcode plugin. It looks like this, when functioning (with excerpts set to false):

• Playing around with VPS.net
• On the GPL, Themes, Plugins & Free.
• Yet Another WordPress Podcast
• New Plugin: RSS Shortcode
• CSS Image Replacement, what's up Matt?

This is a post from Joost de Valk's Yoast - Tweaking Websites. A good blog needs good hosting, you don't want your blog to be slow, or, even worse, down, do you? Use WestHost, and you'll never have issues again!

New Plugin: RSS Shortcode

I have uploaded yet another plugin on WordPress Extend. This one is another ancient plugin that allows you to display your chat widget from meebo me. meebo me lets you chat with your site visitors using your Meebo account.

Visitors on your blog can hit a simple button and chat with you when you are logged into meebo. This is an easy and free way to interact with your visitors.

While meebo me works with every website, this plugin makes integration with WordPress extremely simple.

Read more and download meebo me for WordPress

Check out this interview by Chris Yates with Dave at WordCamp Dallas:

We were pretty dang angry this week for some reason. Dave’s hating on the Virtual WordCamp, Kym’s hating on Jane Fonda, and we’re all hating on the Air Force. But we still love you! ;)

Episode 58

WordPress 2.8.1 Beta 2 released

Virtual WordCamp (WTF???)

BuddyPress 1.02 released

WordPress Plugin Competition 2009 rolls along

Celebrity Pressers: Jane Fonda, Jane Monheit, The US Air Force

Tip of the Week: Make sure you set your timezone in your WordPress

Kym’s pick: Nature WordPress Theme

Dave’s pick: Redirection plugin

Over the next few weeks, I want to take reader-submitted questions about WordPress and answer them here on the blog. Have a question about themes? Plugins? Simple or complicated — it doesn’t matter!

If I pick your question, I’ll answer it (in as much detail as necessary) here on the blog, and link to you as the source of the question.

Hopefully this will be a BIG help to everyone out there, and make for some really good conversation! Leave your questions in the comments.

Related posts:

1. Is My Theme 2.7 Compatible?
2. 7 Must-Have Plugins
3. WordPress 2.3 Theme Backward Compatibility
4. Ultimate Guide to WordPress SEO – Google Sitemaps
5. Comment Link in single.php