Version 1.9.0 breaks my site

  • glennsvlas

    (@glennsvlas)


    1 month ago

    Hi,

    When I installed the 1.9.0 version my site breaks. I received the following email from my hosting provider as it relates to this:

    Error Details

    =============

    An error of type E_ERROR was caused in line 148 of the file /www/mysvlas_793/public/wp-content/plugins/all-in-one-intranet/core/mu-shim/core_aioi_mu_shim.php. Error message: Uncaught Error: Call to undefined function getmypid() in /www/mysvlas_793/public/wp-content/plugins/all-in-one-intranet/core/mu-shim/core_aioi_mu_shim.php:148

    Stack trace:

    #0 /www/mysvlas_793/public/wp-content/plugins/all-in-one-intranet/core/mu-shim/core_aioi_mu_shim.php(70): core_aioi_mu_shim::install('/www/mysvlas_79...', '/www/mysvlas_79...')

    #1 /www/mysvlas_793/public/wp-includes/class-wp-hook.php(341): core_aioi_mu_shim::ensure('')

    #2 /www/mysvlas_793/public/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array)

    #3 /www/mysvlas_793/public/wp-includes/plugin.php(522): WP_Hook->do_action(Array)

    #4 /www/mysvlas_793/public/wp-settings.php(593): do_action('plugins_loaded')

    #5 /www/mysvlas_793/public/wp-config.php(112): require_once('/www/mysvlas_79...')

    #6 /www/mysvlas_793/public/wp-load.php(50): require_once('/www/mysvlas_79...')

    #7 /www/mysvlas_793/public/wp-admin/admin-ajax.php(22): require_once('/www/mysvlas_79...')

    #8 {main}

      thrown

    Can you assist? I’ve reverted back to version 1.8.1

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

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Jackson Mwange

    (@mwangejack)

    1 month ago

    Hi @glennsvlas,

    Thanks for reporting this.

    The error is caused by getmypid() being disabled on your server; this is a PHP function in our latest update that some hosting environments block for security reasons, which prevents the plugin from completing its setup routine.

    If you’d like, the most straightforward fix is to contact your host and ask them to remove getmypid from the disable_functions list in your PHP configuration. It’s a safe, read-only function that simply returns the current process ID, so most hosts are happy to enable it on request.

    Having said that, I have also shared this with our team and we are working on a fix that will be released soon.

    We appreciate your patience on this, and please let us know if you have further questions.

    Thread Starter glennsvlas

    (@glennsvlas)

    4 weeks, 1 day ago

    Thanks for your prompt reply.

    For now, I’ll stand-by for your updated release.

    Thank you again!

    Thread Starter glennsvlas

    (@glennsvlas)

    4 days, 22 hours ago

    Hi,

    My hosting provider will not disable the function you mention under any circumstances.

    Also they are showing that version 1.8.1 has a vulnernerability. I’m inquiring about the severity of that vulnerability.

    When is your new release of your plugin, that will fix my problem, be available?

    Thanks,

    Glenn

    Thread Starter glennsvlas

    (@glennsvlas)

    4 days, 22 hours ago

    Information about your vulnerability can be found here:

    https://wpscan.com/plugin/all-in-one-intranet

    Thread Starter glennsvlas

    (@glennsvlas)

    1 day, 23 hours ago

    Could you please read my last two entries and get back to me?

    Thanks,

    Plugin Support Jackson Mwange

    (@mwangejack)

    1 day, 14 hours ago

    Hi @glennsvlas,

    I apologize for the delay in getting back to you, and thanks for your continued patience!

    To answer your question directly: 1.9.0 did fix the security vulnerability you flagged, but it introduced other compatibility issues, including the getmypid() error you originally reported. That’s why reverting to 1.8.1 got your site running again, but it also means you’re back on a version with the known vulnerability.

    We’re aware of that trade-off, and the release we’re working on is meant to resolve both sides of it, the compatibility issues from 1.9.0 and the original vulnerability, so you can update without running into either problem. It’s close to ready, but still needs to go through testing, so I don’t have a firm date yet.

    I’ll follow up as soon as I have a release date. Thanks for hanging in there while we get this right.

    Plugin Author Slava Abakumov

    (@slaffik)

    14 hours, 23 minutes ago

    Hey @glennsvlas

    I’ve just released 1.9.1 that should address your issue. Please update and let us know whether it works for you!

Viewing 7 replies - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.