Skip to content

10 Things You Should Know About WordPress 2.1

Back in December of 2005, I was filling in for Darren Rowse at ProBlogger and I wrote an entry that was very highly read and commented on. The topic was 10 Things You Should Know About WordPress 2.0. The occasion was the release of the much-waited for release of the current major release of WordPress (We’re up to 2.0.7 but the “dot releases” have all been security/bugfix releases).

Tomorrow (January 22, 2007), WordPress 2.1 will be released and it signifies the first major release since the 2.0 branch was launched. As is typical of major releases, they do not only address security/bugfixes but they release new functionality.

So in the spirit of the original article, I give you ten things you should know about WordPress 2.1.

First though, it’s notable to point at the progress the entire WordPress community has made in the last year since 2.0 was released. Many things, such as themes, have been improved upon. For instance, theme authors can take advantage (and now do!) of screenshot.png, a screenshot image that can be included in a theme folder that provides a visual representation of what the theme is. This ability was implemented in 2.0 but since most themes were designed for WordPress 1.5 at the time, most themes did not have this feature implemented.

In addition, the addition of WordPress widgets as an add-on has provided theme authors and bloggers a phenomenal way to simply drag and drop sidebar elements. This takes the mystique out of placing modules in a sidebar when the vast majority of the WordPress users really don’t know how (or want to) mess with the HTML that makes up a sidebar.

Testing has been given serious effort with the release of hosted blogs. You just thought you were getting a free no fuss, no muss blog built on WordPress but what you little guinea pigs may not have known was that it has been the testing bed of most of the WordPress development code. It gives developers a real-time, real-life window into what works and what doesn’t and allows for extensive non-technical testing. Both WordPress 1.5 and 2.0 were plagued with bugs that were not thoroughly vetted out prior to release. While does not guarantee a bug-free release, the chances and scope of bugs are significantly reduced.

So what is new in WordPress 2.1?

Auto-save of Drafts – WordPress 2.1 adds an autosave function that is automatically implemented when writing new drafts. This functionality uses AJAX and operates without new pageloads. The title of the post must be filled out in order for autosaving to occur.

Better Image Upload Handling – If you do any image uploading under the 2.0 branch, you’ve probably been a little frustrated by the confusing menu that becomes available for those images. It was a bit of “back to basics” to implement radio-button style visual prompts assisting in the handling of these images. You can even Edit image attributes after the image is uploaded.picture-3.png

Deprecation of




, etc – Deprecation is a mild word. Typically in software development, deprecation means that it is no longer a recommend approach but for backwards compatibility, the function or variable still exists. In this case, elimination would be a more appropriate term. This is going to affect a lot of people because there are still many plugins out there using these variables when generating queries within plugins. Instead, the method for querying wordpress table sis to use the


global. For instance,


should be termed




should now be


. And so on. Plugins using the old format will cause SQL errors that might be displayed on a blog or simply break a blog altogether. I had a post recently on the WordPress Development blog which describes these changes.

Update: According to Ryan Boren from WordPress, these variables have been “ressurrected” andplaced in deprecated.php. This is critical as it means that most plugins that may have broke before, will be fine now.

Plugin Compatibility – As mentioned above, many plugins will no longer work in 2.1 due to deprecation of database table variables. However, whenever there is a new version of WordPress, the other possible “plugin breaks” extend farther. Fortunately, the WordPress community has been hard at work testing plugins with 2.1 determining compatibility. You can find a list of backwards-compatible plugins at the Codex.

Native WordPress Migration Functionality – I unequivocally can say that when I released the WordPress-to-Wordpress migrator, I had no idea that it would bring me as much traffic or that the tool would recieve such warm welcome. So, it’s with mixed emotions that I say goodbye to the vast amount of traffic I recieved. The WordPress migration tool was released to essentially mirror functionality that is in WordPress 2.1 (and thus So while the 2.0 branch will remain available through 2010 (it is available in Debian Linux now) , the new 2.1 branch introduces the functionality that I provided to 2.0 customers with my tool.

MySQL Version – It should be noted that although most hosting providers have upgraded their MySQL version to 4.0+, many are still lingering at MySQL 3.23. WordPress 2.1 eliminates support for this older version of MySQL. An easy way to determine what version you are running is to drop this in a file called


and drop inside your web root:

< ?php
// Replace with your database connection info
echo mysql_get_server_info();

New Visual Editor Interface – A big problem (to many) in the WordPress 2.0 branch was the Rich Text Editor (RTE) powered by TinyMCE. I believe the RTE was a good idea but was before it’s time. Thankfully, the developers have heeded the concerns brought to bear on the RTE in WordPress 2.0 and have significantly improved it. Notably, there is now a tabbed interface in the Write screen that will allow bloggers to switch between the two views seamlessly.


Merging of Links and Categories – This is another one of those things that tend to be more of a backend database thing, but there are notable semantics to be pointed out. In previous versions of WordPress, links and categories were handled as two separate entities. Links were seen as a thing used solely to power a blogroll and Categories were seen as a way to solely compartmentalize posts. In WordPress 2.1, the development philosophy shifted in such a way to recognize that these things actually tend to serve nearly similar purposes. While those philosophies can be discussed in other posts, the important thing to recognize is that the Categories table is now prepopulated with a Blogroll category and all links are assigned, by default, to the blogroll category. Folks who are upgrading will have this association made as part of the upgrade process.

Privacy Features – Probloggers will not find this feature particularly useful, nor will most bloggers who desire exposure. However, in WordPress 2.1, there are privacy features which allow you to block your site from search engines and directories. This is useful, however, if you were to want to keep a blog for family or friends or a purely personal blog intended for your own self.

Nonces – This is not really new in WordPress 2.1 but it is new since the original WordPress release. In fact, nonces were introducted in WordPress 2.0.3 and they are significant security items. It applies not only to WordPress but plugins so plugin authors take note of nonces. Mark Jaquith [fixed typo. Sorry Mark!] has more on nonces and how to use them. He details the specific implementation in a way my grandmother (who is dead) could understand. In a nutshell, nonces are unique “passwords” embedded in the comment moderation emails, among other things that prevent YOU from damaging YOUR blog. Each request is assigned a nonce which only lets ONE person do ONE thing within your wp-admin (i.e. approve a comment or delete a post). This replaces the “Are you sure?” dialog.


  1. Great article on what I should know about WordPress 2.1. Over the past year I’ve become more and more acquainted with WordPress through my own personal blog as well as beginning to use the structure as a free CMS option for many of my clients. Thanks for all of this insight!

  2. Good information, I’ve been using 2.1 beta for a while and so far no problem wiht many older plug-ins.


  3. Indeed, good write up.

    Edit: link removed.

  4. FYI, you’ve misspelled Mark Jaquith’s last name, inserting an “i” where there should be none.

  5. I think I use a few plugins that are going to break with the deprecation of $tableposts and $tablecomments, but hopefully the fix is as easy as it looks.

  6. […] put together a worthwhile post for WordPress users wanting to upgrade to WP 2.1. It’s called 10 Things You should Know About WordPress 2.1 which outlines some of the new stuff that it has including auto-saving drafts, new image upload […]

  7. Tim Tim

    And after all this development, there is STILL no Postgres support, denying one of the best pieces of blogging software even more active users who would prefer PostgreSQL instead of MySQL for whatever reasons.

    That’s sad.

  8. Looking forward to the upgrade!

  9. Great article Aaron… I’m running RC1, but I’ll be sure to upgrade when the time comes…

    And what’s this about your tool? You saucy thing, you…

  10. Nice overview Aaron.

    Auto-Save drafts – YES! a real life saver.

    Good to see them working on image uploading as that was the one thing that really, really frustrated me way too many times.

    “many plugins will no longer work in 2.1” – that I don’t like and I think may cause vast headaches for many bloggers.

    A quick look at the list of compatible plugins and my own plugins I use and I think 60% of my plugins are now useless.

  11. I’m sure plugin authors will upgrade their plugins once they realize that they are incompatible with 2.1

  12. It’s my most endearing quality… Speaks volumes about the rest of my character really…

    I just realised the Easy Admin Access is now broken thanks to the post page changing from post.php to post-new.php

    I’ll get on that… It’s proved to be quite popular, so I’d better make sure it’s working properly!

    Congrats on the Digg by the way… You’ve grown up so fast! *sniff*

  13. Can Can

    What about static homepage property ? i created a page and called it as home so it apperared at side block as home cool but it also says home in title and h1 tag on the page :( .Its my first time so probably messed something so is there a way or hack for able to name page as home but not title and h1

  14. Good news and post, thanks for the update.

  15. […] WordPress 2.1 is on its way. Aaron Brazell has posted a nice write-up of new features and things to watch out for (like plugin incompatibility).. […]

  16. Hmm .. people still use that horrible tinyMCE? I hope the default is set to “NO THANKS” ..

    And speaking of thanks.. THANKS for linking to the page that shows the latest versions of plugins that WILL work .. it’s a good start for me personally!

    Later Dude/

  17. PS.. will you be updating Time Capsule? I’ve gotten used to that!

  18. I may have to. I didn’t know anyone actually used it. :-)

    Shoot, you may have to email me the plugin again. I’m not sure where I stashed it.

  19. […] 10 Things You should Know about WordPress 2.1. Some great stuff coming very very soon. I’d suggest a glance at this article before you upgrade, just to avoid surprises (some of them pleasant!). […]

  20. MajorD MajorD

    Great to hear this wonderful project is moving forward – wish they would implement a better spam guard.

  21. Auto-save! This one feature would have been really useful a few weeks back, and now that it’s here!
    Thanks for the overview. This should be a great update for the WordPress community. Hopefully none of my custom plugins will require too much re-work.

  22. Jason: You may actually be upgrading right now because your site is a completely white page. But if you’re not upgrading, I hope now you’re aware that your site is a completely white page. :)

  23. Good stuff. I can’t wait to see it.

  24. […] The next major release of WordPress is version 2.1 and it should be available for download a little later today.  The new release includes better support for images and an auto-save feature for draft posts.  There may be some plugin compatability issues initially and you can find out which plugins are compatible here.  For more information on what is new in WordPress 2.1, take a look at this post on Technosailor. […]

  25. […] o mesmo caminho, especialmente os que usam vários plug-ins, é extremamente recomendável ler este post sobre as novidades da nova versão e como elas podem afetar seu […]

  26. […] Get ready for another update! WordPress 2.1 is set for release tomorrow. For a nice overview of what to expect in the new version, check out Technosailor’s post 10 things you should know about WordPress 2.1. […]

  27. […] WordPress 2.10 slippes. Det er enda ikke kommet noen melding pÃ¥ hjemmesiden til WordPress, men her finner du en veldig fin gjennomgang pÃ¥ hva som blir nytt og anderledes i den nye […]

  28. 10 Things You should Know About WordPress 2.1…

    Wer sich mit einem Umstieg auf die kommende Version WordPress 2.1 beschäftigt, für den fasst Technosailor die 10 wichtigsten Fakten zusammen, die Ihr dazu wissen solltet….

  29. $table* were recently resurrected and placed in deprecated.php.

  30. koz koz

    Hello Unfonrtunately, I did not know your wordpress-t-o-wordpress migrator before I hosted my wordpress elsewhere (and did not want to try the migration of the database due to previous problems I encountered with this).

    My new blog as a 20 days existence (the other one : 1 year 1/2). Do you knwo if it will possible to use this new functionality without loosing my January’s date (entries & comments) ?

    If this is not the place to ask that question, well… sorry… and I’ll ask it elesewhere.

    And thank you for yourt article !

  31. […] goes over my head BUT it is an area I am trying to know more about so I read it with interest. 10 Things You should Know About WordPress 2.1 #PrestoGifto{margin:0 auto;}#PrestoGifto td{vertical-align:top;text-align:center;}#PrestoGifto […]

  32. […] on January 22, 2007. It’s interesting to notice that if not for Technosailor’s 10 Things You should Know About WordPress 2.1 I wouldn’t be able to find out new WordPress features. Even WordPress blog links to […]

  33. Great article Aaron! I was going to do up an article similar to this, but, since I’ve been so busy lately, I just didn’t get to it yet.

    I know it will be too late now, with WordPress 2.1 being released sometime today. But, I might still do up an article which will be a follow-up to your’s.

    Thanks again for the great article! ;) :)

  34. These are the top 10 new features? Pretty disappointing.

    Categories are so out of date. Where is native and well integrated tagging support? What’s with Atom 1.0 support? What’s so special about this picture upload? Most people I know use flickr for their blog pictures anyway. What about proper geo support? What about an auto-update feature? With a security update every ew weeks the whole upgrade procedure is really annoying.

    Sorry, I fail to understand all the noise…

  35. […] sablon nem fog rendesen működni, “ki tudja, mit művel” az adatbázissal, stb. Nos, Aaron Brazzel 10 új dolgot foglalt össze, amely nagyjából jellemzi az új […]

  36. […] Brazell has written a beautiful and informative post about the 10 (perhaps most important) things that you should know about the latest version of WordPress – Word…. Here are the points which are explained on the original post […]

  37. […] Za sve blogere koji funkcioniÅ¡u na WordPressu, interesantan članak Aaron Brazella na engleskom o 10 stvari koje bi trebali da znate o WordPress 2.1. […]

  38. I’m with Tim. It will be really nice when WordPress offers support for Postgres users. Course I will still use WordPress as it is a great piece of software, but I greatly prefer postgres to mysql.

    I think habari may give wordpress a run for their money especially because the software is database independent (MySQL, PostgreSQL, SQLite).

  39. […] WORDPRESS说22号要放出2.1版本~~~期待~~!老早就言称2.1里面有部分核心代码做了改动,部分插件可能无法正常运行。官方有个列表:A  list of plugin compatibile with WordPress version 2.1 ï¼›Deliciouså’ŒDigg里今天关于wordpress的最热门话题也是2.1å•Š2.1,高曝的一篇文章:10 Things You should Know About WordPress 2.1。 […]

  40. Surely now we can All google for test.php, and steal peoples details???

  41. I definitely would be delighted to get my hand dirty on this new version of WordPress. Hopefully it does meet up to expectations.

  42. I’ve just found your blog through

    I will use it for my next WordPress blogs, but for now I will hold on since I am afraid that plug-ins don’t work.

    It happen one time when I changed my template. I’ve lost my pages and sitemeter…

  43. Thanks for your explanations. I appreciate them.

    And BTW: I didn´t know about your wp-to-wp tools before this posting. ;)



  44. […] It appears that WordPress 2.1, upon which our hosting is based, will be released in the next few days, perhaps as soon as tomorrow. 2.1 is the first major release since 2.0 was released almost a year ago and promises several new features: […]

  45. Ryan: Thanks. Wonder how I missed that. I’ve updated the post to indicate that most plugins will not now break because the $table* variables have been, at least temporarily, re-enabled.

  46. Cool article, thanks for the info. I am probably going to hold off for a little while before switching to 2.1 (I’m on 2.0.7 now), to make sure there are no major problems.

  47. brandy brandy

    might be worth noting the big bbPress update too. :)

  48. […] Aaron Brazell has a post written about the 10 Things You Should Know About WordPress 2.1 before it releases tomorrow. He writes about the new additions found in the latest release which […]

  49. […] Some of us are aware that WordPress 2.1 has been released. Technosailor from b5media gives us 10 Things You Should Know About WordPress 2.1. […]

  50. […] января), чего нам стоит от нее ожидать? Ð’ сети появился довольно большой пост на эту тему, но переводить его полностью я не вижу смысла, поэтому […]

  51. Thanks for the clear write up and explanation of the new features in WordPress 2.1

    I was previously going to hold off moving to 2.1 but now I hear that plugins using depricated code will still work I can migrate any that need tweaking at my own pace meaning upgrading should be much easier, and that I can make the most of the benefits of upgrading straight away.

  52. 10 вещей, которые вы должны знать о WordPress 2.1…

    Сегодня должна быть выпущена новая версия WordPress 2.1. Aaron Brazell написал интересную заметку , чего следует ожидать пользователям Wodrress в новой в…

  53. That makes everything clear. Thanks for the well written post!

  54. […] 10 Things You should Know About WordPress 2.1A breakdown of the key new features in the latest version of the blog platform, WordPress.  Version 2.1 will be released sometime today on […]

  55. […] ja, en lees ook dit eventjes. Hoeft u mij niet lastig te vallen met de vraag wat er nu allemaal veranderd is. Door Michael […]

  56. […] ver más detalles sobre estos cambios en el Codex de WordPress o en el artículo 10 Things You should Know About WordPress 2.1; y los más ya ansiosos pueden bajar una versión release candidate de WordPress […]

  57. […] Technosailor pubblica un elenco delle cose da sapere sull’ultima versione di WordPress. L’articolo non è sotto licenza Creative Commons, quindi non voglio tradurlo, ma ne faccio un veloce riassunto. […]

  58. […] WordPress 的问题。不升的理由没有了,于是今天忍不住我把 Blog 升了。(更新:According to Ryan Boren from WordPress, these variables have been “ressurrected” and placed […]

  59. Great article, I’m definitely going to upgrade tomorrow.

  60. […] released. Only a week after the last point release, this version brings not only bug fixes, but new features including improved image uploading, a new WYSIWYG editor, automatic saving of drafts, and more. […]

  61. […] 2.1 – codenamed Ella. Can’t wait to take Ella for a test drive. This is a pretty significant upgrade with lots of new […]

  62. […] 10 Things You should Know About WordPress 2.1 Aaron Brazell gives it the once over for all us WP fans. Know what I’m looking forward too? Auto-save, the improved image handling, and editing. Interesting tidbit? “Nonces”! (tags: 2.1 technosailor update wordpress) […]

  63. […] 10 Things You should Know About WordPress 2.1 » Technology, Blogging and New Media (tags: wordpress) […]

  64. […] for free. A New Sith, or Revenge of the Hope: Reconsidering Star Wars IV in the light of I-III 10 Things You should Know About WordPress 2.1. Many of you run WordPress, so I thought you might find this helpful. Some oops and other silly […]

  65. […] a link to the official WordPress 2.1 page, and Aaron Brazell’s post, The 10 Things You Should Know About WordPress 2.1. Tags: blogging, WordPress Filed under: blogging   |   Tags: blogging, […]

  66. WordPress 2.1…


    一如預告所言,今天 WordPress 推出了 2.1,有很多重要的新功能,例如自動暫存、新編輯器、更有效率的資料庫存取動作… 之類的;大家之前很擔心的 plugin 相容性問題,…..

  67. […] Read more about what has been added or view the comments at the digg post Share this news:These icons link to social bookmarking sites where readers can share and discover new web pages. […]

  68. […] 10 Things You should Know About WordPress 2.1 » Technology, Blogging and New Media So what is new in WordPress 2.1? (tags: WordPress) […]

  69. Keanen Keanen

    Anyone tried to upgrade with postie installed?

  70. […] Gezien het succes van zijn artikel op over 10 die je moet weten over WorPress 2.0 heeft Aaron Brazell 21 januari een mooi artikel geplaatst over de 10 dingen die je moet weten over WordPress 2.1. […]

  71. Just when I was in the middle of integrating Flash 9 and WordPress 2.0.7, you do this to me! Noo!!!

    Hurry up and release it you dogs! – jk jk – =)

  72. WooHoo! 2.1 is released!

    Now then .. when will 2.1.1 be available?

    just kidding :)

    But .. I did just upgrade my Pap site directly from 1.5.2 to 2.1 version. My biggest problems that I had, was the pre/post compatibility issues of my template, and plugins. A lot of code for plugins in my templates had to be removed. My Random Excerpt plugin brought forth a death black screen, but there were plugins I activated that were “not on the approved list” that do work (so far that is – knock on wood)

  73. […] dovrebbero provare ad aggiornare una versione di test del proprio blog e leggere questo piccolo memorandum. PUBBLICITÀ PUBBLICITÀ postato da Fullo il martedì 23 gennaio 2007 […]

  74. Great article. I’ll try this upgrade on my other installed WP.

  75. […] plugins, how to test etc. Plugins Updated For WordPress 2.1 by Gamerz WordPress 2.1 Plugin Testing 10 Things You should Know About WordPress 2.1 a big thanks to Josh Bancroft of for finding this […]

  76. […] ссылок по теме, рекомендую статью Аарона Бразелля 10 Things You should Know About WordPress 2.1 и запись в официальном […]

  77. […] to upgrade your version of wordpress, some cool new features, as I previously highlighted. Here is 10 Things You should Know About WordPress 2.1. Tags:wordpressShare […]

  78. Question. I’ve been digging through the mySql.

    wp_posts has a column called post_category. But there is a table dedicated for categorisation (wp_post2cat). So what is that field used for? Backward compatability? Seems silly… they’re all 0 (default)

  79. […] 10 Things You should Know About WordPress 2.1 Before the newest release of WordPress comes out you might want to be prepared for what to expect. Plugins will break, archives will be massacred oh the pain! (tags: wordpress webdev) […]

  80. Excellent write-up. I often get the question of “why do you need to upgrade?” and “If it’s not broken, don’t fix it”.

    You just gave me some ammo to fight of pesky questions about upgrades of WP.

    I found that the ditching of support for old MySql 3 was a MAJOr issue as some of the folks I deal with still run that old bugger ;)

  81. Baby: There is talk of setting the min MySQL to 4.1 in 2.2 ;)

  82. I would really like to see WordPress 2.1 running on my server. But I think I will wait some weeks before updating. Many plugins I use still don’t support WP 2.1.

  83. […] 했다. 일단은 까페24에 mysql 버전업에 대해서 문의해둔 상태다. ì—­ì‹œ WP2.1을 깔기 전에 알아야 í•  10가지를 빠뜨린 탓 […]

  84. I also want to see WordPress on my website but I only have one concern i.e. what if there is a serious & critical security bug discovered (e.g. MySpace Spam King issue) and I don’t upgrade my installation. Somebody will hack my blog. And I have experienced it few years back while experimenting with PHPNuke which was the then great CMS alternative!

  85. I had a problem after upgrading wordpress 2.0.7 server to 2.1 on a FC6 server this morning. The editor is ‘code’ only and no tabs shown at all to switch between the two modes. I have a
    screenshot here for anybody interested to help me troubleshoot. Any pointer is appreciated.

    • MikeQue MikeQue

      Thanks! We have been going nuts thinking something was wrong with the PHP or had misinstalled.

      This is definitely a usability bug, that this is set to default inWP2.1 and is buried so deep in the UI.

      • What usability bug are you referring to, MikeQue? Your comment does not make apparent sense because it might be out of context…

  86. You probably have the option set on your profile page to not use the Visual Text Editor.

  87. I thought of that too, so I checked all the options under the Admin’s dashboard, esp. options/writing. Can you be more specific on where this ‘profile page’ is?

  88. […] new features and over 550 bug fixes which you can read at your leisure using the above link. Technosailor has provided a nice overview of the new 2.1 release if you don’t fancy reading through all […]

  89. shame on me. I missed it. Thanks, Aaron. I skipped the whole option/users tab, thinking it is for user account management.
    Anyhow, I was using Visual Text Editor before the upgrade. So, the upgrade somehow took it away. Hate to think it could be caused by a reset to default because I’d think most people would want Visual Editor. Otherwise why use a CMS at first place :)

  90. […] Get ready for another update! WordPress 2.1 is set for release tomorrow. For a nice overview of what to expect in the new version, check out Technosailor’s post 10 things you should know about WordPress 2.1. […]

  91. I just upgraded to WP 2.1 and I was pleasantly surprised that none of my 2.0.7 plugins broke that I couldn’t find updates to WP 2.1 versions. Even with the little bit that I’ve checked out in 2.1 I’m even happier than New Orleans Saints fans are this week.

    Thanks for bringing me into the WP family. I can;t believe it took me so long to use this killer software/

  92. […] 10 Things You should Know About WordPress 2.1 » Technology, Blogging and New Media (tags: wordpress blog software tutorial) […]

  93. WordPress am laufenden Band?…

    Eine WordPress-Version jagte in den vergangenen Tagen die andere. Und während einige Anwender froh über ihr letztes Update sind, wartet die nächste Generation WordPress bereits auf seinen Einsatz. Frag sich nur, wieviel Update braucht d…

  94. […] Ils ont aussi un forum dédié à ce nouveau-né. Un article intéressant aussi (en anglais) sur le blog de Aaron Brazell, développeur chez […]

  95. me me

    the new version still not support. “real” source code editing.
    eg. you can not embed a youtube video.

    • Sure you can. Make sure you’re in standard mode and not using the RTE.

  96. […] 10 Things You should Know About WordPress 2.1 » Technology, Blogging and New Media (tags: wordpress blogging CMS Download OpenSource plugins reference) […]

  97. […] Links: WordPress 2.1 Ella 10 Things You Should Know About WordPress 2.1 Download WordPress 2.1 WordPress 2 (Visual QuickStart Guide) WordPress Complete: set up, customize, […]

  98. […] now due to these database optimisations, it seems to from my end anyway. Aaron Brazell has written “10 Things You Should Know About WordPress 2.1″ with even more details on the changes that come with WordPress […]

  99. […] another techy note, I’m still mulling over the WordPress 2.1 (Ella) upgrade because I have yet to check that all of my plugins are compatible.  Eventually I will stop being […]

  100. […] last night. I probably should have done a bit more research, as the upgrade involved quite a few fundamental changes to the back end, including template tags and other gotchas. So, I’ve spent most of last night […]

  101. […] After several recent security fixes, WordPress 2.1 is going to be released to the public tomorrow. Technosailor has a great overview of the updates made in the new version – 10 things you should know about WordPress 2.1. […]

  102. Thanks for a useful post – I will be upgrading the indigo t-shirt blog this weekend but am still worried about plugins not working.

  103. […] 10 Things You should Know About WordPress 2.1 by Aaron Brazell… Aaron gives some good insight into what to expect from the latest upgrade from WordPress, but I think he (they) missed some of the finer points. […]

  104. […] is a pretty exhaustive summary over at Technosailor, but be prepared to be underwhelmed, because all in all, this was not the day […]

  105. […] Proprio per questo molti bloggers prima di fare l’aggiornamento dovrebbero provare ad aggiornare una versione di test del proprio blog e leggere questo piccolo memorandum. […]

  106. […] 10 Things You should Know About WordPress 2.1 » Technology, Blogging and New Media is a good summary of key changes. Merging of Links and Categories […] While those philosophies can be discussed in other posts, the important thing to recognize is that the Categories table is now prepopulated with a Blogroll category and all links are assigned, by default, to the blogroll category. […]

  107. […] biggest annoyances with wp: the “Save and Continue Editing” button now works and the bizarre image insertion interface from the old WordPress is much […]

  108. […] 10 Things You Should Know About WordPress 2.1 Some WordPress 2.1 Gotchas […]

  109. […] has posted 10 Things You should Know About WordPress 2.1.Found via […]

  110. […] today, I pushed a button to upgrade All Spin Zone to the newest major release of WordPress, version 2.1. For those of you who use WordPress as your own blog platform, I’m pleased to report that the […]

  111. […] anybody confused by WordPress’ clever new autosave system, apparently it only works if the title is filled in. Makes sense – I couldn’t work out why it was so […]

  112. […] new version comes feature packed with several new additions. Technosailor gives you some detail while the WordPress Blog release post just lists them out for quick […]

  113. […] WordPress 2.1 has been released. Here is the Plugin Compatibility List, and 10 things you should know about WP 2.1. […]

  114. WordPress 2.1…

    It’s been a bit over two weeks since the release of the long awaited WordPress 2.1, codenamed Ella, and although I had upgraded one of my blogs the very next day when it became available, it’s only now that I finally have some time to post …

  115. […] 2: Well, it looks like the category merge is a new feature after all and it had another effect: it changed the id of the categories, so I had to rewrite my sidebar for […]

  116. adam s. adam s.

    The advanced toolbars and buttons in the TinyMCE editor of WordPress 2.1 can be changed and customized as you like. See the article at for details.

  117. Hi,
    Nice Top Ten List and frankly this is useful. Thank you for taking time to blog this :)

  118. Aaron, you could probably do some more updating on this list as more features have been released. Might even start prepping your next article that includes the new Tags feature in WordPress.

    Great write-ups though, looking forward to more of them.

  119. Anyhow, I was using Visual Text Editor before the upgrade.

  120. @Grosshandel: Yea I was using Visual Text Editor, too.

  121. And after all this development, there is STILL no Postgres support, denying one of the best pieces of blogging software even more active users who would prefer PostgreSQL instead of MySQL for whatever reasons.

  122. Although i’m using wordpress 2.3 now, this is still great information. Its fascinating how fast things like features and / or bugs can change in the short period of time, that a new version is developed. Thanks, Aaron!

Comments are closed.