bsmolyanov

Yes, exactly, the Make and API Call. The “Body” parameter was not filled-in and this caused the error. However, previously this was not an issue. Now, I inserted {} in the body and the error is gone. Method is POST.

Hi, David,

Since several days the error says:

• [400] Invalid JSON in request body: Syntax error (error code: rest_invalid_json)

However, nothing in the way the value (post ID) passed to Make.com has been changed on my side (in WordPress).
Moreover, in the Make module itself there is nothing in the body. The post ID is passed as part of a custom REST API end point, like “posts/postID/delete-terms” where the postID if the variable from Make and ‘delete-terms’ is the custom end point, registered in WordPress via PHP code.
Therefore I am not able to see what json is being sent/received.

• This reply was modified 8 months, 3 weeks ago by bsmolyanov.

Thanks a lot, @m4xw3ll ! I look forward to it.

Meanwhile, I came up with one more suggestion (feature request) – ability to use the OpenAI’s Batch API for the Knowledge Base embeddings, as it provides 50% cost reduction.

Imagine one needs to feed many thousands of posts into the Knowledge Base vector database. Such a task is not urgent, so the process can be delayed by up to 24 hours per batch, and the best part – the cost savings will be tremendous.

I trust you will consider such a feature as well.

Thanks and keep up the great work!

I will start a new thread based on the new topic.

Thank you!

Managed to solve this by replacing LogInitiators::WEB_USER with LogInitiators::WP_USER.

Hi @eskapism

For the record – the culprit was the plugin GP Social Share. It seems not currently supported, although I like it a lot.

Thanks for your support!

Thanks a lot, @eskapism !

Unfortunately, something seems to be wrong. I place the code in functions.php and then I get the following PHP errors. Also it prevents the other loggers from displaying their messages as well.

There are the errors I am getting:

Got error 'PHP message: PHP Fatal error:  Allowed memory size of 2147483648 bytes exhausted (tried to allocate 557056 bytes) in /home/....../wp-includes/class-wpdb.php on line 2459'

and

Got error 'PHP message: WordPress database error Commands out of sync; you can't run this command now for query UPDATE wp_options SET option_value = '1695284706' WHERE option_name = 'action_scheduler_lock_async-request-runner' made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_OptionLock->set, update_option, QM_DB->queryPHP message: WordPress database error Commands out of sync; you can't run this command now for query SELECT COUNT(DISTINCT claim_id) FROM wp_actionscheduler_actions WHERE claim_id != 0 AND status IN ( 'pending', 'in-progress') made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_AsyncRequest_QueueRunner->maybe_dispatch, ActionScheduler_AsyncRequest_QueueRunner->allow, ActionScheduler_Abstract_QueueRunner->has_maximum_concurrent_batches, ActionScheduler_DBStore->get_claim_count, QM_DB->queryPHP message: WordPress database error Commands out of sync; you can't run this command now for query SELECT a.action_id FROM wp_actionscheduler_actions a WHERE 1=1 AND a.status IN ('pending') AND a.scheduled_date_gmt <= '2023-09-21 08:24:06' LIMIT 0, 5 made by shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_AsyncRequest_QueueRunner->maybe_dispatch, ActionScheduler_AsyncRequest_QueueRunner->allow, ActionScheduler_Store->has_pending_actions_due, ActionScheduler_DBStore->query_actions, QM_DB->query'

I would really appreciate your input to make this custom logger work.

Thanks!

• This reply was modified 2 years, 9 months ago by bsmolyanov.