[wp-hackers] Requesting advice regarding comments form errors, accessibility and patch for http://core.trac.wordpress.org/ticket/4332

Andrew Nacin wp at andrewnacin.com
Mon Feb 22 13:06:40 UTC 2010

This has also been discussed in a few other tickets in some form. There's no
good way to handle this uniformly across all themes (such is the nature of
the beast). There was one suggestion to add an API of sorts for a theme to
be able to receive errors back, another to just add a simple hook that can
then be fed a wp_redirect() and die() before WP issues one. Since in 3.0 we
now have a comment form template tag, we could incorporate such handling
into there as well.

I'm sure many would love to see this tackled in a future release, but it
needs to be tackled head-on. It might be good to find the various related
tickets, tag the duplicates, and maybe we can paint a clear picture of the
problem and use cases, and what can be done to make it better.

On Mon, Feb 22, 2010 at 7:48 AM, Bjorn Wijers <burobjorn at gmail.com> wrote:

> Hi,
> I'm wondering if somebody (preferably a core committer) could shed some
> light on this patch http://core.trac.wordpress.org/ticket/4332.
> As far as I understand from Ryan there are some issues with comment
> paging and inline replies? What should be done to fix this?
> I would like to fix this so we can show errors directly in context with
> the form fields instead of showing a new page. By doing this, Wordpress
> would adhere to this section[1] of the Dutch Government accessibility
> guidelines (Webrichtlijnen) out-of-the-box. This makes it even more
> interesting to use Wordpress for Dutch Government websites :)
> [1]
> http://www.webrichtlijnen.nl/english/manual/development/production/contingency-design/guidelines/#r-pd-22-5
> ps: Javascript is not a solution since it is a client-side solution upon
> we cannot rely.
> Thanks in advance!

More information about the wp-hackers mailing list