• My host (WPEngine) has disabled the php function ‘disk_free_space’. It appears that this is an issue (for me, at least) with WP 6.3, and its new ‘pluging/theme rollback feature’. This feature tests to make sure there’s enough disk space before attempting a manual plugin or theme update.

    But, since my host has disabled this function, I now get the Site Health message, “Could not determine available disk space for updates.”

    While this message *is* correct, and does *not* prevent me from updating plugins or themes, it’s annoying to have this constant message.

    My understanding is that a number of shared hosting providers – like WPE – disable this function, so I would think others might have this issue.

    Has anyone else experienced this?

Viewing 7 replies - 1 through 7 (of 7 total)
  • What’s annoying about it?

    There’s no error going on here.

    Thread Starter Steve D.

    (@sdowney2002)

    I think of any issues raised by Site Health as items needing to be fixed. There is no fix for this – it’s just a status report. I’m thinking maybe this particular type of response (‘we can’t determine free disk space) doesn’t belong in Site Health, perhaps?

    Mostly, I’ve posted to see if anyone else is having this issue. My hosting provider is at a loss, so I’m wondering if it’s maybe something with MY configuration. (I’ve done all the typically checks to clear the issue, without success.)

    imo, there is nothing to fix here tho –>

    I think of any issues raised by Site Health as items needing to be fixed

    It’s a false positive, bc the Health plugin is unable to check.

    There’s loads of plugins WPEngine denies for various mostly good reasons,

    https://wpengine.com/support/disallowed-plugins/

    WPEngine are the experts in their field of hosting. The Site Health plugin is an overall *guide* to your installation, and is contributed and maintained to WordPress.org by the community.

    My 2 cents is ignore it, and move on.

    Thread Starter Steve D.

    (@sdowney2002)

    It seems to be a poor design choice to show what is basically and *informational* message (‘cannot determine free disk space’) in Site Health. In my mind (and I bet many others), messages in Site Health represent problems to be fixed. We’re now being told to ignore a message.

    I don’t think it’s a ‘false positive’. The message itself is correct. My issue is simply that the message should not be presented in Site Health.

    That’s just bad UX.

    I am also hosted by WPE and my site has been getting the same Site Health message “Could not determine available disk space for updates.” Now, I am now getting the message after updating to 6.3.1 “Available space is critically low, less than 20MB available. Proceed with caution, updates may fail.” Contacted WPE and they had no clue why my site is saying that as I have ample disk space. This is annoying and frustrating. I agree with Steve D. Anyone else have this issue?

    Thread Starter Steve D.

    (@sdowney2002)

    @drsuperior Yep, looks like they introduced a new error in 6.3.1 here: https://core.trac.wordpress.org/ticket/59116#no0. I can replicate your issue when I update to 6.3.1 and when I revert the code change in ticket #59116, the issue goes away. I’ve submitted a ticket to WP.
    https://core.trac.wordpress.org/ticket/59251#ticket

    Good to hear Steve D. – hopefully they will fix it.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘‘disk_free_space’ php function disabled by host’ is closed to new replies.