-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to do more configuration in admin #7
Comments
We have index name. Right now, non-protected meta fields are indexed. I think that is sufficient. Although an extra filter couldn't hurt. |
Sorry - was porting over some ideas from the old repo. Are you auto-indexing all meta fields? We dealt with that at the hack day to ensure that we only include explicitly declared meta fields. Aaron Holbrook On Jun 10, 2014, at 3:15 PM, Taylor Lovett notifications@github.com wrote:
|
We are indexing non-protected meta fields. See is_protected_meta() function also register_meta(). We actually need to check for an authorization callback before checking whether the meta is protected. We went through all this with WP API last week. In short, a filter is not necessary WP has functionality built-in to determine whether meta is public or not. |
Things like index name, meta fields to index, etc
The text was updated successfully, but these errors were encountered: