Last checked and updated on April 16, 2026What Is New in WordPress 2.1
WordPress 2.1, codenamed Ella, is a significant release focused on a more streamlined writing experience, major under-the-hood code improvements, and enhanced security.
| Category | Key Changes |
|---|---|
| New Features | Autosave, Spell Check, New Default Theme |
| Improvements | Redesigned Interface, Faster Performance, XML-RPC API |
| Developer Changes | Updated TinyMCE, Deprecated Old Functions, New Hooks |
| Security | Improved Comment Moderation, Security Hardening |
| Bug Fixes | Over 550 Bugs Fixed |
How did the writing experience improve?
The editor got a major overhaul. Autosave was introduced to prevent content loss, and a spell check feature was added directly into the writing panel.
In practice, this meant fewer frantic copy-paste actions when a browser crashed. The entire interface was also cleaned up, making it less cluttered and more focused on the actual task of writing.
What under-the-hood changes affected developers?
The core code saw massive optimization, making pages load significantly faster. The XML-RPC API was fully enabled by default, opening the door for more external applications and mobile clients to interact with WordPress.
This matters because it was a big step towards WordPress being a true application platform, not just a blogging tool. Developers also had to contend with the removal of old, deprecated functions like the_category_head() and the_category_id().
Was there a new default theme?
Yes, WordPress 2.1 shipped with a new default theme named Kubrick. This theme was a visual refresh and was designed to be more modern and visually appealing out of the box.
It featured a cleaner design and better typography, setting a new standard for how a default WordPress theme should look and feel for users.
How was security addressed?
Security was tightened with improved comment moderation tools to help fight spam. Several other security enhancements were baked into the core to protect against common vulnerabilities.
While not a single headline feature, this ongoing hardening was crucial for maintaining the integrity of the millions of sites already running on WordPress.
FAQ
What deprecated functions were removed in WordPress 2.1?
Functions like the_category_head() and the_category_id() were finally removed. If your theme or plugins used these, they would break and needed to be updated to use newer alternatives.
Is the Autosave feature compatible with existing plugins?
It could cause conflicts with plugins that implemented their own save routines or heavily modified the post editor. Testing was essential after upgrading.
Why was the XML-RPC API enabled by default?
This move was to better support external publishing tools and mobile apps. It standardized remote publishing, making it a core feature instead of an optional one users had to find and enable.
How significant were the performance improvements?
Very. The core team focused on optimizing database queries and caching, which resulted in noticeably faster page load times, especially on sites with a lot of content.
Did the TinyMCE editor get updated?
Yes, the bundled version of TinyMCE was upgraded. This provided a more stable base for the visual editor and fixed several bugs present in the older version.