Change History (9)

Looks like testing material to me. Something a theme author can verify it's stuff prior to release in quality control. Better to educate a theme-author then the user who might just does not get what this all is about (too technical).

The workflow suggested is making the user the tester when it's already too late: Theme distributed and the error thrown means a full roundtrip from user -> themer -> user.

There are just so many users with themes which are lacking one of the two hooks.
Then they blame my plugin, when the JavaScript is not working...
Which is no surprise, as it is never included without the hooks, as it is included using wp_enqueue_script().

I think hakre has a good point: at that point it's too late. This feedback expects too much of the end user. When confronted with such an error message, he has to then decide what it means, whether it's worth doing anything about, and if so, what to do.

Also, I have a hard time believing this is a widespread problem, which I remember coming across a few times in 2005 and 2006, but not much since. Haven't we won the war by now?