Mohammad Jangda

Looks good 👍

We could also intelligently default to specific sanitize callbacks depending on the field type (e.g. rich text should use `wp_filter_post_kses`)

Thinking we need to introduce some sort of `sanitize_function` option as well in cases where you don't want to have to handle the custom callback with all the params, i.e....

Yep: ``` $sanitize_function = apply_filters( 'cmm_sanitize_function', 'function', ... ); if ( is_array( $value ) { $value = array_map( $sanitize_function, $value ); } else { $value = call_user_func( $sanitize_function, $value );...

:P On Thu, Jan 31, 2013 at 7:19 PM, Rinat K [email protected] wrote: > I'm just bringing that to your attention, so it won't fall through cracks > as it...

Closing as wontfix for now. We can revisit if/when we pick up additional work to the Vary Cache API.

I think a good workaround would be an imitation Files Service that lives in dev-env. I would suggest we close this as it may not be the place to track...

> But I think long term this is just more technical debt and we should instead remove all this special handling and have it be just like core does. This....

I think the issue is that there's no need to send PURGE requests to these URLs. However, given the age, I think we can just close this.

We should probably add `dir_opendir` which just calls `return false` since we don't really support directory operations (like iterating).