CompleteRSS 1.0 Released

CompleteRSS 1.0 was released yesterday, it’s been upped to a full-release, no longer alpha. Nothing major has changed as far as functionality or purpose is concerned, but it’s a highly recommended upgrade because it addresses a couple of high-profile (really annoying) bugs that can occur if you have a post with the word “feed” in the permalink.

Moreover, there have been several fixes to enhance compatibility with non-standard permalink structures, older versions of PHP, and feeds via proxies. It’s a fully-stable release, and now it’s more important than ever, since WordPress 2.1 has gone public.

WordPress 2.1 never displays content past the <!–more–> marker in an RSS/Atom feed, unlike WordPress 2.0.x & co. If you’re a dedicated blogger and you love your readers, do them a favor and serve full-content RSS feeds: they’ll appreciate it, and you’ll get more feed subscribers :)

Continue reading

MySQLi for WordPress 2.1.x

MySQLi is a “new”1 and improved version of the original MySQL extension for PHP. While there is no especially convincing reason to switch from the original MySQL functions to MySQLi, both MySQL and PHP recommend that developers do so.

WordPress is aimed for the masses and WordPress 2.0 still supports even MySQL 3.x – so most likely we won’t be seeing a switch to a MySQLi-powered WordPress anytime soon. However, for those that care about such things, we’ve created a MySQLi conversion file for WordPress.

Continue reading


  1. It’s been available for years, just no one uses it. 

Why I Joined Habari, and What It’s All About

People have been bombarding my email asking me questions about Habari, and most importantly, why I joined it. I wasn’t planning on blogging about any of this until I officially became a committer in the Habari project, but after reading this post, I feel the need to share my reasons.

I’ve been a loyal contributor the WordPress project and a ardent (for lack of a more aggressive word) WP-Hacker for what seems like forever – even though it isn’t. WordPress is my first-love when it comes to blogging, you may have noticed. But yeah, I working on Habari too.

I didn’t leave WordPress. Not because Matt is the devil-incarnate nor because I’m put off that he wouldn’t hire me (not even interested), but because Habari is a challenge. It’s something I’ve always wanted to work on.

Continue reading

WordPress 2.0.7 Fixes the FeedBurner Bug

For the first (and hopefully last) time ever, we’re glad to hear that WordPress has a major security vulnerability. Why? As a result of a security vulnerability that affects WordPress 2.0.6 and below on certain server configurations, the WordPress Developers Team has released a new version of WordPress that incorporates both a security patch for the detailed vulnerability, and a fix for the FeedBurner Bug that we reported for 2.0.6. You can download WordPress 2.0.7 or see the list of affected/changed files here on the WP Development Blog.

Originally, the WordPress team had refused to patch the WordPress 2.0.6 FeedBurner Bug on the premise that it was too soon to release another version of WordPress for a “minor” bug – which we disagreed with. However, you can now download WordPress 2.0.7 and hopefully this time there aren’t any surprise bugs that need immediate patching. We highly recommend everyone goes and downloads WordPress 2.0.7 immediately in order to avoid anyone compromising their blog/site via the security hole in WordPress 2.0.6.

Correction: WordPress is released and maintained independant from Automattic

Ultimate Tag Warrior and WordPress 2.1

For anyone trying out WordPress and interested in keeping their tags alive: don’t. Ultimate Tag Warrior is completely broken with WordPress 2.1 and you can lose all your tags by upgrading to WordPress 2.1. In the more recent SVN revisions of WordPress 2.1, any time a comment is added, deleted, or unapproved, you lose all the tags for that particular post. It’s a damn shame, because UTW is an excellent plugin, and WordPress 2.1 is a big improvement over 2.0.

Bunny’s Technorati Tags is a more basic tagging solution, but it’s verified working on WordPress 2.1. If you can figure out how to switch from UTW to Bunny’s TT you can easily switch back when Christine releases a new version of UTW that’s compatible with WP 2.1 via her import from custom-field feature. Just be very careful, make database backups, and use Google when you get stuck.

Continue reading

A Clarification on WordPress

Day before yesterday, we posted an article about how WordPress was king of the blogging world, and how close to impossible it would be for it to lose its position. Amongst the comments, trackbacks, emails, and pingbacks directed our way, we find it necessary to clear up some points. For sake of communication and clarity, we’re using bullets to explain:

Most importantly: that wasn’t a review of WordPress. Just a discussion about how WordPress amongst others “spoils” developers!

  • WordPress isn’t necessarily the best engine, just the best platform. The difference is, it might not have the best code and features out there, but as a product together with its community, resources, and developers, it’s the platform for you to use.
  • The reason why WordPress will find it much easier to remain at the top compared to others that have taken the fall is that it’s open source, friendly, and free. That means people are more willing to help it out. Business 101: “open & flexbile” companies take much more and much longer to fail than “closed & rigid” companies do.
  • We’re not saying WordPress will remain the best product, but that even if a far better product came out (like the promising new-comer: Habari), WordPress will remain the tool of choice simply because of how widespread and prevalent it has become.
  • WordPress is not a company, it’s an open-source project. Automattic is the company. They come together, but WordPress is a separate entity, that continue developing and improving with or without Automattic. Don’t confuse the two.

Continue reading

WordPress 2.0.6 and FeedBurner Disconnects

This article provides a workaroud for WordPress 2.0.6 and chronic FeedBurner disconnects. It’s essential that you upgrade to WordPress 2.0.6 immediately in order to prevent your blog from being taken over by hackers! Upgrade, then follow these instructions to get it to play nicely with FeedBurner afterwards.

The Problem

After upgrading to WordPress 2.0.6 or WordPress 2.1 Beta, your FeedBurner feed will, at times, give you an “invalid xml” error, and “FeedMedic” will show you something like this:

Your server disconnected us before sending the full source feed content. If your blogging platform is TextPattern, this is a known bug, and a fix can be found here: http://forum.textpattern.com/viewtopic.php?id=11247

Continue reading

How WordPress Spoils Developers

When you’re done reading this article, check out our clarification for more info.

WordPress took the online world by surprise. Undoubtedly the single most influential tool in the blog-boom, WordPress has not only revolutionized the web as we (used to) know it, but also completely changed the daily ins and outs of web development forever. It’s not just about the power and perfection of the package, but also the coding standards, community benefits, and open source modeling. In short, WordPress has changed the face of web scripting for everyone.

The most obvious impact WordPress has had – on everyone – is that there really isn’t much room for another blogging platform. No matter how good of a competing product someone might make, it’s near impossible for anything to ever overtake WordPress as the tool of choice for the job – no matter what that might be. WordPress isn’t perfect, and we’re the first to admit it. It certainly isn’t the most lightweight blogging platform nor is it the ultimate CMS, but that most definitely hasn’t stopped it from conquering the market.

Continue reading

Why is $_SERVER[] Considered a “Class?”

There seems to be a minor bug/glitch in our Request_URI for Windows that we can’t figure out, so if anyone has any idea, please give us a holler, or post below if you like. Under times of high load (and sometimes without), PHP completely crashes and dies until the worker process is restarted with Using $this not in object context as the “die message” that shows up for all requests. However, our script doesn’t use a class, and makes no calls to one either.

Continue reading

Updated Comment-Entry Form

A long time ago NeoSmart Technologies used to have WYSIWYG editors all over the place, but things just didn’t work out. For one, it was rare for a post with even tiny bit of formatting applied to be rendered as valid XHTML (like the rest of the site), and for another, it was very incompatible with newer versions of certain web browsers and older versions of others – so we got rid of the system.

However, we’ve had quite a few complaints about WordPress’ default requirement for encoded HTML entities, and many posts were lost by including an unencoded “<” or other element. We’re glad to say we’ve found an alternative. We came across the Xinha WYSIWYG editor, a nice (and possibly minimal)-looking editor that has a new experimental HTML-creation engine that produces truly valid code no matter what you throw at it. That and the fact that it can easily be customized (as we’ve done here) and works on almost any browser made it the ideal choice for NeoSmart Technologies.

Anyway, it works fairly well and a spell checking module is also being added at the moment. For anyone not wanting to use the WYSIWYG editor (especially if you’re trying to write some code), you can press the icon of a document with “<>” superimposed on it – that’ll display the pure HTML and you can do what you like from there.