Major re-organization of handlers. PLEASE NOTE: This drastically affected the Views module API and until modules are updated to match, they will stop working. Efforts have been made to ensure that this won't cause your site to crash, but that's partly up to the individual module as well.

#278013: Failure to check for relationship with base table causes error when adding many to one filters and fields on a relationship.

#279899 by mooffie and nonsie: Move views_preprocess_node() to views.module so it always appears; add display name to node template suggestions. Needs documentation.

Create a "soft" fail condition for arguments, which means that if an argument is part of a % placeholder in a URL, failing validation is not actually a failure IF there is some other action to take when validation fails.

Exposed filter memory was being trashed by a rewriting validate; also, exposed filters that decided not to participate weren't properly storing that status in session. This fixes both things.

Modify $view to only use handlers for the field items, since it cares a lot more about the handlers than it cares about the actual storage of the field items. This could have implications for modules, particularly date and calendar.

#264282: Check for errors before doing foreach on an item that might not be an array when breaking 1,2,3

Some refactoring of how handlers are handled, particularly with their default options. This is an unfortunately widespread change and will affect modules utilizing the API.

Missing body caused table level override on field level text items; i.e, "Node revision" overriding "Body"

Initial taxonomy implementation. There's still a ways to go -- I totally punted on depth -- and we need a few more argument handlers.

Add an "empty text" option to the prerender_list handler (which affects user roles and profile freeform list)