Support » Everything else WordPress » WordPress 2.2.1

  • whooami




    Unfortunately, 2.2.1 is not just a bug fix release. Some security issues came to light during 2.2.1 development, making 2.2.1 a required upgrade. 2.2.1 addresses the following vulnerabilities:

    * Remote shell injection in PHPMailer
    * Remote SQL injection in XML-RPC Discovered by Alexander Concha.
    * Unescaped attribute in default theme

Viewing 15 replies - 1 through 15 (of 56 total)
  • Huzzah! I’ve been waiting for those atom fixes for a while as it means my blog wasn’t being syndicated to livejournal.




    im sticky!!! yay!! 🙂 cool!

    Could someone confirm that this List of Files Revised for 2.2.1 is correct.


    I host several WordPress sites for some friends and clients of mine. Is it possible to get ‘a heads up’ some days before an update is released? This is specially usefull when the update includes security fixes, so i can make some arrangements and apply them as soon as possible. BTW i’m not member of any mailing list, so maybe there is one that does that already.


    I did all as written in instructions to upgrade my blog to latest version.
    After I uploaded all files and go to

    I am getting this message:
    No Upgrade Required

    Your WordPress database is already up-to-date!

    Is this ok or I did something wrong? :-S

    Greetz…you can follow the version update progress on the WordPress Trac Roadmap.

    Is it just me or can’t I upgrade?

    “Parse error: parse error, unexpected $, expecting ‘]’ in /data/members/paid/n/e/ on line 242”

    Edit: after a long fight, fixed it.. But says I don’t need to upgrade.. Okay..


    I’m getting the same message and I’m getting an error in my sidebar that reads…

    WordPress database error: [Unknown column ‘name’ in ‘order clause’]
    SELECT * FROM wp_categories WHERE cat_ID > 0 AND link_count > 0 ORDER BY name ASC

    Anyone know how to fix this please?

    Site can be seen here:

    I have the same problem as ingaoz.

    If you want advance notice of releases, the best thing to do is subscribe to the WP-testers mailing list.

    After the upgrade from 2.2 -> 2.2.1, password protection of post, page is not working.





    A sidenote to all of this upgrading nonsense..

    this :

    simply isn’t clear enough about upgrading the default theme.

    and this:

    says NOT to delete anything inside wp-content/ which would include the default theme,of course.

    The end result to this ambiguity in those instructions is that people don’t upgrade the default theme, which has changed considerably in the last few iterations.

    That’s been evidenced over and over again already by the sheer number of ppl still running the default theme and having issues with deprecated tags inside it.

    Perhaps NOW, that a security issue has been addressed within the defualt theme, someone might edit those instructions properly?

    For those that might suggest that “eye” update the codex, don’t even go there 😮 If I update the codex it’s going to be 30 pages long when I’m done.

    About the password protection function not working after the 2.2.1 upgrade, when I go to my blog as guest, the password protected post just comes up without requiring any password.

    Is this a bug or what?

    In comments I have no </br> in the new version. Is this a bug? Or problems of any of my plugins

    password protection function works after clearing my cache…but works in a funny way. will start a post describing this behavior…

Viewing 15 replies - 1 through 15 (of 56 total)
  • The topic ‘WordPress 2.2.1’ is closed to new replies.