@Rarst I still have one blog < 3.0 - we don't need no auto-updates.

> The problem I am facing is the post meta can be called by a unique key that is pcom in my case

I wonder if our site is an attack vector for some hacks. People ignore validation and sanitization that much...

Sites running unsanitized CRUD requests are de facto just cloud storages for bot nets.

Is there anyway I can intercept the term being updated through quit edit before it's updated?

Strange issue... I changed the term "description" field from a normal textarea to a wp_editor() ... So that I could format descriptions... So it saves just fine when editing a specific term. However, say you wanted to update a term name or slug quickly using the quick edit... When it saves the term, it strips all the HTML from the description.

Ding ding ding.. Found the culprit. pre_term_description filter... has wp_filter_kses hooked.

In-case anyone cares..... Here's what I did

add_filter( 'wp_kses_allowed_html', array( $this, 'set_allowed_html' ), 10, 2 );

`public function set_allowed_html( $allowed_html, $context ) {

	if ( $context != 'pre_term_description' ) {
		return $allowed_html;
	}

	return wp_kses_allowed_html( 'post' );

}`

So term descriptions now allow the same HTML as a blog post for example.