WordPress.org

Ready to get started?Download WordPress

Forums

WordPress 2.2.1 (57 posts)

  1. whooami
    Member
    Posted 7 years ago #

    http://wordpress.org/development/2007/06/wordpress-221/

    READ!!!!

    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

  2. Dustyakubra
    Member
    Posted 7 years ago #

    Huzzah! I've been waiting for those atom fixes for a while as it means my blog wasn't being syndicated to livejournal.

  3. whooami
    Member
    Posted 7 years ago #

    im sticky!!! yay!! :) cool!

  4. MichaelH
    Member
    Posted 7 years ago #

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

    Thanks.

  5. jetze-itproducties
    Member
    Posted 7 years ago #

    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.

    Greetz

  6. ingaoz
    Member
    Posted 7 years ago #

    I did all as written in instructions to upgrade my blog to latest version.
    After I uploaded all files and go to
    /wp-admin/upgrade.php

    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

  7. lexhair
    Member
    Posted 7 years ago #

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

  8. empoor
    Member
    Posted 7 years ago #

    Is it just me or can't I upgrade?

    "Parse error: parse error, unexpected $, expecting ']' in /data/members/paid/n/e/nehold.com/htdocs/www/wp-includes/theme.php on line 242"

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

  9. sportech
    Member
    Posted 7 years ago #

    ingaoz,

    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: http://www.sportech.info/

  10. Academiphiliac
    Member
    Posted 7 years ago #

    I have the same problem as ingaoz.

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

  12. skiordie
    Member
    Posted 7 years ago #

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

    Hmmm...

  13. whooami
    Member
    Posted 7 years ago #

    A sidenote to all of this upgrading nonsense..

    this :

    http://codex.wordpress.org/Upgrading_WordPress#How_to_Upgrade_in_Five_Steps

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

    and this:

    http://codex.wordpress.org/Upgrading_WordPress#Detailed_Instructions

    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 :o If I update the codex it's going to be 30 pages long when I'm done.

  14. skiordie
    Member
    Posted 7 years ago #

    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?

  15. crishnakh
    Member
    Posted 7 years ago #

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

  16. skiordie
    Member
    Posted 7 years ago #

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

  17. designoahu
    Member
    Posted 7 years ago #

    I received the message that there is no upgrade available after replacing the files with the 2.2.1 version, however at the bottom of the dashboard it does say that I am running version 2.2.1, go figure.

  18. designoahu, I just experienced the same thing. Uploaded all of the files, no upgrade is necessary, and in my admin panel it says 2.2.1 on the bottom. How do we know for sure that the upgrade actually took place?

  19. MichaelH
    Member
    Posted 7 years ago #

    @designoahu and jeffro,
    Database upgrade isn't required going from 2.2 to 2.2.1 just the upload of the files (which is where the version info comes from). So running the upgrade.php, doesn't hurt, but doesn't really do anything.

  20. designoahu
    Member
    Posted 7 years ago #

    I see. Thank you for clearing that up MichaelH!

  21. wdg
    Member
    Posted 7 years ago #

    I've been a member for 6 months. I'm not experienced, but just feeling my way.

    I upgraded from 2.0.x to 2.2.1. In my sidebar where the blogroll should be, it says:

    WordPress database error: [Unknown column 'link_count' in 'where clause'] SELECT * FROM wp_categories WHERE cat_ID > 0 AND link_count > 0 ORDER BY cat_name ASC

    How can I make that go away and my blogroll appear? I saved my database before I upgraded. Do I have to revert back to 2.0.x?

  22. MichaelH
    Member
    Posted 7 years ago #

    wdg--no, just revise your sidebar.php to use the template tag, wp_list_bookmarks(), or change your theme to one that is compatible with 2.2.

  23. themystical
    Member
    Posted 7 years ago #

    I don't know but I'm having bad luck with this 2.2.x batch, haven't tried to do any upgrades but so far all fresh instals led to troubles, dashboard messed up, not able to delete post, edit them, the blog content showing in the dashboard as it was the theme, that was really weird. Also forbidden access errors, some could be fixed by editing the .htaccess other not, widgets problems and... I'm stiking with 2.1.3, willing to upgrade but too busy(scared) to fix eventual problems. Meh :-\

  24. danahuff
    Member
    Posted 7 years ago #

    Michael, thanks so much for explaining the mysterious upgrade. We are all so used to the steps involved in upgrading that deviation threw us for a loop. It might be a good idea if some note of the difference between upgrading from 2.2 to 2.2.1 and other upgrades was mentioned on the Development Blog.

  25. cpoteet
    Member
    Posted 7 years ago #

    My ExecPHP widgets don't work in 2.2.1

  26. crishnakh
    Member
    Posted 7 years ago #

    For make appear br in comments, deactivate plugin LMB smilies comments.

  27. BlogK
    Member
    Posted 7 years ago #

    I have issues with this quick upgrade cycle. Seems there is not a decent level of testing. 2.2 has widget feature build in but templates don't seem to recognize it well. My template uses test for sidebar widget widget
    <?php if ( function_exists('dynamic_sidebar') && dynamic_sidebar() ) : else : ?>

    Now with 2.2.1 won't display sidebar unless on home page.
    Is there a different call to make?

    Why is this issue not mentioned on download page? How much testing is done before release?

    Why not seperate the urgent security fixes from the feature set improvement. These update are getting to be a real pain. I am not in a rush for new features. I want the existing code to work with what I already have and not go thru a debugging cycle every few weeks.

  28. petersig
    Member
    Posted 7 years ago #

    I am getting a very similar sidebar error to those reported by sportech and wdg, above--but I'm running 2.0.4, and terrified of updating:

    This is the base code in the sidebar:

    <?php if (is_home()) { ?>
    				<?php
    	$link_cats = $wpdb->get_results("SELECT cat_id, 
    
    cat_name FROM $wpdb->categories WHERE link_count!='0'");
    			foreach ($link_cats as $link_cat) {
    	?>

    The error report is:

    WordPress database error: [Unknown column 'link_count' in 'where clause']
    SELECT cat_id, cat_name FROM wp_categories WHERE link_count!='0'

    Warning: Invalid argument supplied for foreach() in /home/formytum/public_html/wp-content/themes/Antique-Modern/sidebar.php on line 10

    The fix is supposed to be, according to Michael H:

    revise your sidebar.php to use the template tag, wp_list_bookmarks(), or change your theme to one that is compatible with 2.2.

    While I can trace sidebar code, and know something of the function of each section, I can't either debug this code or figure out how to use the template tag, as Michael H. instructed.

    My site, with the error message still holding forth, is
    (I always have to explain) a health-education site for IBS, called For My Tummy, http://www.formytummy.com.

    TIA

  29. MichaelH
    Member
    Posted 7 years ago #

    petersig--actually my advice isn't correct there--if you are running version 2.0.4, then the 2.0.4 database table wp_categories does not have a column called link_count. Only with 2.1 did link_count get added to the wp_categories table.

    It would see you are using a theme that is designed to run with 2.1 or 2.2 but your database is still a 2.0.x database.

    @wdg--the update may not have completed successfully, at least the database portion so you might want to run install.php again.

  30. christian-s
    Member
    Posted 7 years ago #

    @whooami
    thanks for pointing out that the
    wp-content\themes\classic
    wp-content\themes\default
    should be deleted when doing the upgrade.

    I got this error when trying to follow the upgrade instructions
    "Parse error: syntax error, unexpected '}' in /home/vicsande/public_html/blog/wp-content/themes/default/functions.php on line 418"
    as I did not delete those dir because the guideline explicitly said NOT to delete those directories.

    Now my site is working again after I uploaded the new versions of the two themes. thanks!

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags