Since I can’t make sense of the list of files revised, could you tell us whether this revision fixes the problem that developed with 2.3.1 that broke the email notification of comments for lots of people?
Here’s a link to the Codex article with tickets closed and code changes for 2.3.2:
http://codex.wordpress.org/Changelog/2.3.2
I upgraded one site, but I won’t be upgrading the rest until somebody tells me why, after upgrading, I can’t delete categories! I go to “Manage,” “Categories” and hit delete. When I refresh the page, the categories I previously deleted are back again!
The provision for custom db error is a good one.
I’d like to request for a similar custom message in case of a PHP coding error. If a novice like me makes an error while tinkering with the PHP code of a template file, the viewer of the blog at that point of time sees a long string of “Fatal error at /home/…blah…blah…on line no…”
In addition to being very annoying to a visitor, it doesn’t make any sense to him(her).
Can we have an arrangement where the meaningful PHP error message is sent to the admin, but the viewer is shown a polite custom error message.
Thanks in advance.
S.K
I picked up the message that I should update my installations, and saw the suggestion on the page http://wordpress.org/download/ suggesting using a hosting partner so that the upgrade is a one-click operation.
At WordPress’s suggestion I do exactly that, and my host is Bluehost. Their service has been pretty good, except in the area of WordPress upgrades.
My experience has been that through my host’s Fantastico installer new versions of WordPress only become available after many days or sometimes weeks.
The latest update isn’t available through Fantastico at the time of writing, which is worrying when we’re being warned to upgrade quickly!
Could someone please speak to Fantastico about this or even with my host, if that’s where the problem lies?
Thanks,
Gavin
gmatkin,
You may use a FTP client.
S.K
But kichu, that only addresses part of gmatkin’s question.
gmatkin can do it himself manually using an FTP client, but then what’s the point in WordPress recommending non-technical folk use a hosting partner “so that upgrading is a one-click operation”?
kichu, I like your suggestion re error pages due to buggy PHP code. Do you want to copy that to the Requests and Feedback forum? (It makes sense here too, but it should also be there, I think.)
Why upgrade to 2.3.2?
The “security threats” seem irrelevant to me. What’s wrong with people being able to see the _structure_ of my database? Some people might have reason to be concerned about people seeing their drafts, but I’m not. Do I need to upgrade?
(This will be my first upgrade since I made several edits to files that I think will get replaced, so I will need to spend more time than I want to planning and tinkering.)
P.S. Should there be a “comment” link on the 2.3.2 announcement page?
I will upgrade because I see that the list of changes includes:
* Performance improvements for post sanitization when raw content is required (#5325).
* Suppression of database errors unless WP_DEBUG is true (#5473).
* Changes to wp-mail.php to escape the error messages when displaying them to avoid a possible XSS attack (#5484).
* Changes to the information exposed the wp.getAuthors xmlrpc method to reduce the information exposed and add a capabilites check (#5534).
If those mean what I think they mean, it’s good for me to upgrade.
I asked my question “Why upgrade …?” because I expect lots of people will think the announcement is not relevant to them.
I upgraded and my blog is gone!
is it true mcgregorlink?
i’m thinkking to upgrade it!
I upgraded and when I log in I still get a message telling me to upgrade…
The upgrade announcement says this:
As a little bonus, 2.3.2 allows you to define a custom DB error page. Place your custom template at wp-content/db-error.php. If WP has a problem connecting to your database, this page will displayed rather than the default error message.
I see no option in the Admnin CP after upgrading to define or create such a page.
I have not given up hope. It may still be there, but hosting service is looking onto the prob, which may be on their end.
