On Wed, Oct 10, 2012 at 6:52 AM, Daniel Kinzler daniel@brightbyte.de wrote:
Since the ContentHandler stuff has been merged into the core, several much-used functions and hooks have been deprecated. I have tried to find and replace all calls in core, but a lot of extensions are still using the old stuff. They will still work for all text-based content, but will generate a ton of warnings, and will fail tests (and make core tests fail).
I'm very worried about converting all of the extensions to use new APIs now. If it turns out we need to revert ContentHandler, this will make the revert that much more difficult.
I'd rather we remove deprecation warnings for the newly deprecated APIs.
Rob