Posted 3 years ago #
A number of error messages are issued using the die method.
This is very unfortunate for many reasons. In particular for translators because the corresponding page does not seem to be given a particular encoding and the translated message may appear garbled.
For example in the wp-login.php file, why not display these messages as nicely as the other ones in the wp_login function of pluggable-functions.php?
Thanks! :-)
Posted 3 years ago #
I agree with chtito. Form error handling in wordpress needs an overhaul. Are there any plans to implement hooks for error handling so that I can customize the way I deal with errors via the API, or am I going to have to hack out wp-comments-post.php and the other offending files, only to be forced to constantly diff and merge whenever there's a WP update?
This IS a support question.
Posted 3 years ago #
It's certainly a valid question, but one best answered by the developers, who don't spend a lot of time on the forums.
Have a look at the mailing lists here:
http://lists.automattic.com/mailman/listinfo/
I think wp-hackers is the appropriate one for development questions, and wp-polyglots for translators.
And for anyone with concerns about the forums, have a look at wp-forums
Posted 3 years ago #
Ah, LesBessant, thank you! Sometimes the most obvious ideas elude us. I've been on wp-hackers for nearly two years.
As it turns out, there was a brief discussion about this very thing on the wp-hackers list in October 05. I've inquired as to the state of affairs, and will report back as necessary.
Posted 2 years ago #
Reporting back, nine months later:
The wp-hackers list pointed me to this bug report:
http://trac.wordpress.org/ticket/1786
which appears to have been resolved by using wp_die() instead of die() in the wp-comments-post.php file. I suppose wp_die() must be hookable.
These changes made it into the wordpress trunk on July 5th, but somehow didn't make it into the 2.0.5 release on October 27th. It looks like they still haven't made it into the 2.0 branch, and thus probably won't make it into the 2.0.6 tag, which was apparently due 5 days ago.
Looking further into this, the wp_die() function is slated for the 2.1 release, which does not yet have a date on the official roadmap.
This topic has been closed to new replies.
