mkormendy

I am having this issue as well.

That appears to have allowed the plugin to work, however I am still seeing the error in the logs.

Did you end up figuring this out?

How?

That’s not how a thread is resolved. This is not resolved whatsoever.
Opening a new thread is redundant, and confusing to new users.

I figured out that there were multiple requests being sent, but the first initial request is successful. That being said, I will close this ticket and can move forward with what I was developing. It appears that authentication/capabilities aren’t needed when using rest_do_request().

As for the documentation, I would still like to help, I’m offering my hand, please contact me at mike at somethinginteractive dot com.

In my case, and a couple others, I think documentation would have fast-forwarded my development, as it took me more time than necessary just to read the plugin code and conjure up a bunch of tests until I got things right.

Let’s chat offline about how I can help.

Do you need some help with maintaining parts of this plugin BTW? The developer documentation is woefully under-informative, I think that if we had better documentation, you would have less support-debt on your plate.

I don’t think you read the whole support question in its entirety.

I’m using rest_do_request() method with the WP_REST_Request API. I shouldn’t need a user.

• This reply was modified 4 years, 6 months ago by mkormendy.

And the progress after 3 months is?

I would look into using Gravity View. It’s free now on github. Look for the article on WP Tavern.

Of course I re-installed W3 Total Cache, still broken, rolling back to the previous version has stopped the errors for now until you guys fix your plugin.

I have confirmed this is working.

Nevermind, I’ve found the code to remove the notice.

My cron scheduler runs on a very slow basis due to my setup. I however would like a way to turn off the notice and not have it automatically determined by your algorithms.

I would like to know this too.