You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a PULL request that addresses this issue, and will link it shortly.
(This ticket is to supply the background information).
I was seeing errors on my site generated from /wp-cron , related to wp-help.
The error was actually occurring in a different plugin (wp-optimise), however the cause of the error is able to be isolated to wp-help. This is illustrated in lines 6 & 7 in the trace below.
The error is thrown during CWS_WP_Help_Plugin::api_slurp() , when updating posts (i.e. slurped from another URL).
Currently, when CWS_WP_Help_Plugin::api_slurp() is called, it never registers the wp-help post type.
Reasons why I think the post type should be registered as part of api_slurp:
It's a one-line code fix to solve.
For someone encountering the error, it's not necessarily easy to diagnose.
Given we're in the context of WP hooks...etc. it is perfectly reasonable for other plugins to expect that this post type be registered, prior to wp_update_post() being called.
I have a PULL request that addresses this issue, and will link it shortly.
(This ticket is to supply the background information).
I was seeing errors on my site generated from /wp-cron , related to wp-help.
The error was actually occurring in a different plugin (wp-optimise), however the cause of the error is able to be isolated to wp-help. This is illustrated in lines 6 & 7 in the trace below.
The error is thrown during CWS_WP_Help_Plugin::api_slurp() , when updating posts (i.e. slurped from another URL).
Currently, when CWS_WP_Help_Plugin::api_slurp() is called, it never registers the wp-help post type.
Reasons why I think the post type should be registered as part of api_slurp:
TRACE is as follows:
The text was updated successfully, but these errors were encountered: