• Resolved kmwhcn1980

    (@kmwhcn1980)


    Thank you so much for creating this plugin. I noticed that my site check is having two errors associated with this plugin.

    The errors are:

    1. Background updates are not working as expected – It seems that the plugin is disabling wp_version_check()

    2. The Rest API did not behave correctly. – The REST API did not process the context query parameter correctly.

    I have disabled all plugins and reactivated them one by one, and it appears that CIDRAM may be causing this.

    Is there a way to resolve these errors? Thank you again for your excellent work with this plugin.

    • This topic was modified 3 years, 3 months ago by kmwhcn1980.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Maikuolan

    (@maikuolan)

    Hi kmwhcn1980,

    Firstly, thanks for creating this topic and for sharing this problem with me.

    Offhandedly, I’m not entirely sure why that’s happening. CIDRAM doesn’t *explicitly* disable wp_version_check() anywhere (in fact, the only part of the CIDRAM plugin which directly interacts with WordPress code is its main bootstrap file, cidram.php, which just contains some basic necessities for ensuring proper compatibility between WordPress and CIDRAM; everything else in the plugin is very self-contained). But for now, without having looked further into it just yet, what I *suspect* is happening, is that when WordPress attempts to execute wp_version_check(), or attempts to execute the REST API, somewhere along the communication chain (e.g., the WordPress server attempting to respond to the initial request), CIDRAM is executing, that part of the execution chain (e.g., and most likely, the IP address of the origin of the particular request at hand) is triggering one of CIDRAM’s internal signatures, and is consequently being blocked by CIDRAM, thus causing the wp_version_check() call or REST API call to fail.

    I wanted to reply here now, mostly to confirm that I have now seen this topic. I’ll look into this problem now, attempt to verify/confirm my suspicions, find a decent solution (most likely, because this sounds like it’s either a bug, a false positive, or both, it’ll involve pushing/tagging a new version/release, and needing to update), and reply back a little later to share what I discover, debug/details/etc.

    Plugin Author Maikuolan

    (@maikuolan)

    Hi kmwhcn1980,

    I’ve made some changes just now, which implement some new bypasses, which I’m hoping should resolve the problem, and pushed out a new version accordingly (2.6.1).

    When you’ve got a spare moment, mind updating to the new version, then testing to confirm whether the problem still persists (CIDRAM causing wp_version_check() and the REST API to not work properly), and replying back here to let me know the results? The changes made should help, but I’m not sure whether I need to take the changes further.

    Cheers.

    Thread Starter kmwhcn1980

    (@kmwhcn1980)

    Hi Maikuolan,

    Thank you for your efforts! With only CIDRAM activated, I am still receiving an error that REST API did not behave correctly — The REST API did not process the context query parameter correctly.

    That said, with both CIDRAM and the health check plugin activated, I am still getting the background check error – A plugin has prevented updates by disabling wp_version_check().

    I also tried a site health check With only the health check plugin activated. With this configuration, I am receiving a minor prompt informing me that I should remove inactive plugins. Both rest API and background checks seem to be working.

    Please let me know if you need any further information. Again, I appreciate your assistance.

    Kyle

    Thread Starter kmwhcn1980

    (@kmwhcn1980)

    Hi Maikuolan,

    I removed the health check plugin and the only issue that remains is with the Rest API, as stated above.

    Cheers,

    Kyle

    Plugin Author Maikuolan

    (@maikuolan)

    Hi Kyle,

    Sorry for the delayed reply. Very busy past few days with training assessments, and haven’t yet had much time to look into this further. I’ll need to investigate this a bit more over the next few days, I think. I’ll reply back here again as soon as I progress a little further with it.

    Cheers,
    Caleb.

    Thread Starter kmwhcn1980

    (@kmwhcn1980)

    Hi Caleb,

    It’s ok, thank you for your efforts. I realize that developers have lives and priorities outside their plugins. No apology is needed. If you need anything on my end, please let me know.

    Cheers,

    Kyle

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Site Health Issues’ is closed to new replies.