WordPress.org

Ready to get started?Download WordPress

Forums

WORDPRESS 2.3.3 IS AVAILABLE!!!! (79 posts)

  1. youngmicroserf
    Member
    Posted 6 years ago #

    Oh and btw, I'm getting the same thing in an installation of the nightly built ('Your WordPress 2.4-bleeding is out of date. Please update.') on my localhost.

  2. whooami
    Member
    Posted 6 years ago #

    i wanted to see what the source said on the site, youngmicroserf

    I looked at the php source responsible for the upgrade message, and thats using the global, $wp_version, which is assigned inside wp-includes/version.php

  3. outrageousthoughts
    Member
    Posted 6 years ago #

    After the upgrade, I noticed I was having problems with email notifications when comments are posted. Basically, there are no emails being sent. Whereas prior to the upgrade, email notifications for posted comments were working fine.

    I performed a diff between the versions of the files wp-include/pluggable.php and found that the only different is that the new version excluded the following line:

    $phpmailer->Sender = apply_filters( 'wp_mail_from', $from_email );

    I understand that others have had problems when this line was included in previous versions, but my problem is quite the opposite. So, if you may be suffering from lack of emails when people post comments, you may wish to include this line back in (or just revert your copy of wp-include/pluggable.php).

    [sig moderated]

  4. dhanchey
    Member
    Posted 6 years ago #

    I don't know where to put this so I'm going to throw it up here. I am very new to WP and attempted the upgrade to 2.3.3 by myself. I followed the extended instructions carefully yet had multiple errors. Some of them were caused because my files did not upload to the server correctly (does anyone have experience with this problem with satellite internet?, but I noticed two things that had they been included in the directions, would have helped immensely:
    1. The config.php file had two lines that were different so I entered the correct information and uploaded a new one for 2.3.3.
    2. change your theme to "default" BEFORE you upgrade. Then, upload the new default theme. The directions tell you not to delete your Content folder, but if I had used the new default theme from the get-go, the troubleshooting process would have gone much smoother. (I was using the old one and got many errors.)

  5. skeezicks
    Member
    Posted 6 years ago #

    It's probably moot at this point, but I recall reading about problems at Bluehost when uploading files... Depending on what one uses to do the uploading, existing files WILL NOT be overridden and apparently no warning is given.

    I never saw that problem because I use dedicated ftp applets, so I wouldn't be surprised if this has something to do with the "new and improved" file manager used in Bluehost's cPanel...

    Just my 2 cents...

  6. Samuel Wood (Otto)
    Tech Ninja
    Posted 6 years ago #

    This is why deletion (after backing up, of course) is recommended.

    See: http://codex.wordpress.org/Upgrading_WordPress_Extended#Step_7:_Delete_the_old_WordPress_files

  7. qdsouza
    Member
    Posted 6 years ago #

    I'm rolling back to 2.3.3 this minor release some how messed up all the Ajax on the Admin Side of my site. Can't add categories, links, can't even delete posts where everything is messed up.

  8. artscenter
    Member
    Posted 6 years ago #

    Thanks to "whooami" for the info about which files changed from 2.3.2 to 2.3.3, and for making them available as a .zip on his own site.

    BUT this info should have been included in the developer's blog that announced the release. It would be nice to also have an "official" .zip (and a .tar.gz) of the five files. That way we could be assured that the info was correct, that the .zip included the correct files, and that they had not been tampered with.

    It looks like "whooami" has done a lot of great work helping people get WordPress working, but there's nothing to prevent a malicious person from posting a bogus .zip file that includes malware of some sort. Without an "official" .zip file, we each have to decide on our own whether or not to trust "whooami"'s version.

    (I'm not trying to cast any doubt on his work, but as far as I can tell, he isn't officially part of the WordPress development team, or even a moderator. If his information was wrong, I assume somebody official would have seen it and removed his post. But his website could have been hacked at any time, for example, and who would know?)

    Me, I'm paranoid: I downloaded the full 2.3.3 installation .zip, expanded it, and took the files from there. That way I knew that they were the correct versions. It probably took me an extra minute or two. (I assumed "whooami" is right about the five files, but figured it was unlikely that updating them would mess up the blog. I backed up everything before doing anything, of course, just in case.)

    I do NOT mean this post to cast any doubt on "whooami" or his posts; I just think it would be better to get this information and the files from an official source. And again, thanks to "whooami" for getting this info to us.

  9. zuHause
    Member
    Posted 6 years ago #

    Hi there! I found some mysterious user, that lately registered to my blog. The given username looked quiet random so I googled the russian email address: inefarege@bk.ru google
    The user seems to register to all available blogs and guest books by script. He often leaves the more or less stupid line "Hello! Nice site ;) Bye.". I think this is the preparation for a mass abuse of blogs and guest books!

  10. whooami
    Member
    Posted 6 years ago #

    (I'm not trying to cast any doubt on his work, but as far as I can tell, he isn't officially part of the WordPress development team, or even a moderator. If his information was wrong, I assume somebody official would have seen it and removed his post. But his website could have been hacked at any time, for example, and who would know?)

    I am a she.

    And I would know.

    You take the same risk with every plugin you install, by the way.

    And for the record, having files hosted on this site makes them no less safe. In fact, this site has had files modified in the past; my site, in sharp contrast, has never been exploited.

    last time I checked, this wasnt fort knox.

    [

    See this if you need clarification:

    http://wordpress.org/development/2007/03/upgrade-212/

    ]

    That said, you raise good points, and I dont take offense -- I just think you put a little too much stock in one domain over another without cause.

  11. Samuel Wood (Otto)
    Tech Ninja
    Posted 6 years ago #

    BUT this info should have been included in the developer's blog that announced the release. It would be nice to also have an "official" .zip (and a .tar.gz) of the five files. That way we could be assured that the info was correct, that the .zip included the correct files, and that they had not been tampered with.

    The WP devs have been reluctant to provide "changed" releases directly for a few different reasons. Primarily because when people modify the core code, they cannot guarantee that the change-only files will continue to work properly. And really, this 5-file difference is an extreme example, normally upgrades contain dozens and dozens of changed files. It wouldn't really save any time or space to upload only the changes in those cases.

    If you really want to upgrade using changes only, then you should be doing SVN upgrades. Read more about this here:
    http://codex.wordpress.org/Installing/Updating_WordPress_with_Subversion

  12. Motel Moka
    Member
    Posted 6 years ago #

    Just updated on Monday. I wanted to know if there's a way to modify the "write post" display in which instead of getting the html edit mode I can get to switch it to the ordinary text mode? Seeing all the codes keeps confusing me when I'm trying to write a post and I use images pretty often and I obviously can't modify them manually in html edit mode which takes too much time out of my hands.

  13. Floridadan
    Member
    Posted 6 years ago #

    I updated my blog with just the xmlrpc.php file and I've found that old users can register and post comments without being approved first. That is extremely annoying when you delete/ban a user who comes back and registers again and posts like nothing happened. So I rolled back to the old xmlrpc.php file until someone can clear up why this is happening.

  14. Samuel Wood (Otto)
    Tech Ninja
    Posted 6 years ago #

    The xmlrpc.php file has nothing to do with either registration or posting of comments. It would not affect either of those because it is not used at all for those. It's not even loaded into memory in those cases.

    The xmlrpc.php file is only used when called directly, and it only allows for remote editing and publishing of Posts (not comments). It is also used for pingbacks (which don't contain any comment or post content).

  15. Floridadan
    Member
    Posted 6 years ago #

    There's a bug in the new xmlrpc.php file that allows users who have been deleted to register again and bypass the rule that allows comments once the first comment has been approved.

  16. Jeremy Clark
    Moderator
    Posted 6 years ago #

    As far as I know wordpress doesn't keep track of a user once they have been deleted so an old user would be able to sign up again. As otto said xmlrpc is only used by desktop blogging software such as windows live writer. It has nothing to do with user registration.

    Edit: Just checked on this and I'm correct wordpress keeps no track of the user once they've been deleted. So old users could come back and re-register without any trouble therefore no bug.

  17. Floridadan
    Member
    Posted 6 years ago #

    Thanks Otto and Jeremy. I thought deleting annoying users was effective but they are simply re-registering. Once they have been approved they remain approved even if you delete their username. There seems to be no effective way to rid my blog of pesky users.

  18. Jeremy Clark
    Moderator
    Posted 6 years ago #

    One quick way to stop them from commenting is to add their user name email address and the ip address they comment from to the comment blacklist.

  19. Floridadan
    Member
    Posted 6 years ago #

    Yes, but won't that catch other innocent users if their username contains a similar word or phrase as the blacklisted username? How do you unapprove a user that's been approved. There's an option to unapprove a comment but that only works for the single comment.

Topic Closed

This topic has been closed to new replies.

About this Topic