Closed Geczy closed 12 years ago
The core problem is that the Wordpress code base is full of minor errors, whilst the whole point of this library is to be ultra strict about errors. They don't go hand in hand.
An ideal solution would be to detect if it's wordpress, and then be less strict about error reporting, but that's easy to say.
You can also use 'withoutErrors', and pass a callback into there. That's useful if your loading wordpress for a specific section, such as to grab out some blog posts for a non-Wordpress page.
Oh I see! So your class actually just quits if there's any error or notice at all, right?
Yes.
The idea is that for those times when you just want to try the code, by having a very aggressive and "look at me" attitude with errors, you'll be more focused churn away at the errors one at a time. It also means the minor ones are just as important.
Essentially, you are forced to fix every bug it finds, there and then.
I like this. Thanks for clearing that up, I was used to xdebug's ways of continuing to execute the rest of the script, yet showing the errors at the top.
Perhaps a new issue for a feature request to "continue = on" rather than quit? Unless this exists already?
Closing as this is intentional behavior
Turning on
php_error.wordpress = On
fixes this issue...Not ideal, though