Nate Zander

Thanks for your help.

@nickrigby your solution did not work for me, v0.1 of the plugin

@aaylersghost that worked great!

I changed line 42 to:

$vars = apply_filters( 'rest_query_vars', $wp->public_query_vars );

Yes, I did modify the plugin directly. Since I installed it manually, there is no risk of it accidentally being overwritten.

Is it safe to assume this will be the permanent ‘opt-in’ fix to enable this functionality in the API?

Interesting, thanks @nickrigby. I will test it out and report back.

Is anyone out there filtering by meta_key/meta_value? The plugin does NOT seem to resolve that type of filter query, but trying to confirm if it’s just me.

re: https://github.com/WP-API/WP-API/issues/1599#issuecomment-143412680

I am also experiencing this.

I did find this plugin, but it doesn’t seem to help with filtering by custom fields (even after I registered the meta). I am rolling back to WP 3.6 for now.

https://github.com/WP-API/rest-filter

It looks like that line of code was unnecessary to get my other ajax to work. Plugin working fine now, thank you.

Sorry, yes I use admin-ajax.php as required by wordpress. I use the above line of code to catch the POSTed action variable to route to the proper php function.

Unchecking ‘send usage data back’ seemed to clear it up for me.

We are also experiencing this.

We use the PHP embed code. Is there a parameter I can pass to remove this pixel?

yarpp_related(array(
  'exclude' => array(480, 486), 
  'post_type' => array('post', 'recipes'),
));

No I am using new WP REST, thanks.

I am also very interested in this. Has anyone had success yet?

Thank you computerinfo21, that hack worked perfectly.

This plugin is exactly what I need to add post style flexibility to my child theme. But I don’t like hacking plugins in case they get updated…has anyone found a similar plugin that is being maintained?

Thanks!

I am also experiencing this bug.

I am also experiencing this error, and unfortunately it’s breaking the rest of the javascript on my page. In this case, it’s only affecting my logged in contributors. In this case, the edit screen is open inside a modal window (created by fancybox)

Disabling NextGEN Gallery resolved the issue.

I will submit the bug report as you suggested above.

I also encountered this error. I am running PHP 5.4.38

Thanks Kyle! I will give it a try and update my rating.