Warning messages in Version 1.14.10

  • Resolved ipapagi

    (@ipapagi)


    3 years, 2 months ago

    Hi after the activation of the latest Version 1.14.10 shows many warnings (multiple times):
    : popen() has been disabled for security reasons in
    /var/www/vhosts/espapevthess.sites.sch.gr/httpdocs/wp-content/plugins/boldgrid-backup/admin/class-boldgrid-backup-admin-cli.php
    on line
    133

    Warning
    : fread() expects parameter 1 to be resource, null given in
    /var/www/vhosts/espapevthess.sites.sch.gr/httpdocs/wp-content/plugins/boldgrid-backup/admin/class-boldgrid-backup-admin-cli.php
    on line
    135

    Warning
    : pclose() expects parameter 1 to be resource, null given in
    /var/www/vhosts/espapevthess.sites.sch.gr/httpdocs/wp-content/plugins/boldgrid-backup/admin/class-boldgrid-backup-admin-cli.php
    on line
    142

    Please could you help me?

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

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Jesse Owens

    (@jessecowens)

    3 years, 2 months ago

    Hi @ipapagi –

    Thanks for reaching out, and I’m sorry to hear about all the warnings you’re seeing.

    First, I’ll start with an overview of what’s causing this warning. Total Upkeep requires access to run some commands on your server, and it checks with your server configuration (php.ini) to see what execution functions are available, including ‘popen’, ‘proc_open’, ‘exec’, ‘shell_exec’, ‘passthru’, and ‘system.’

    It’s totally normal for your hosting company to disable one or more of these, which is why Total Upkeep asks the server for your PHP INI information to see which ones are disabled.

    What seems to be happening in your case is that your server’s php.ini does not list popen as a disabled function, yet when Total Upkeep tries to use popen, we get the message :popen() has been disabled for security reasons.

    One possibility to check would be to run this command if you have SSH access:
    php -r "ini_get( 'disable_functions' );"

    That command should give you a list of disabled functions, including popen. If it’s not, then you should check with your Systems Admin or hosting provider to either enable popen, or make sure that the php.ini file reflects which functions are disabled.

    Thread Starter ipapagi

    (@ipapagi)

    3 years, 2 months ago

    Hi @jessecowens

    Unfortunately, I don’t have a ssh access. But I put the following lines in a php file and I load it from a browser:
    <?php
    $retval = ini_get( ‘disable_functions’ );
    print_r($retval);
    ?>
    and the result is:
    opcache_get_status,mail, apache_child_terminate, apache_setenv, define_syslog_variables, escapeshellarg, escapeshellcmd, exec, fp, fput, highlight_file, ini_alter, ini_get_all, ini_restore, inject_code, openlog, passthru, php_uname, phpAds_remoteInfo, phpAds_XmlRpc, phpAds_xmlrpcDecode, phpAds_xmlrpcEncode, popen, posix_getpwuid, posix_kill, posix_mkfifo, posix_setpgid, posix_setsid, posix_setuid, posix_setuid, posix_uname, proc_close, proc_get_status, proc_nice, proc_open, proc_terminate, shell_exec, syslog, system, xmlrpc_entity_decode

    popen is among the above commands but not the fread and pclose.

    Please could you advise me how to proceed?

    Plugin Contributor Jesse Owens

    (@jessecowens)

    3 years, 2 months ago

    Hi @ipapagi –

    Thanks so much for taking the initiative to create that testing file! Based on this information, I was able to recreate the bug and I’ve filed a bug report for our developers.

    The root cause of the problem is that normally, the disabled_functions list doesn’t have spaces in it, and we didn’t account for that in our logic. In your example, you can see that there is no space in between opcache_get_status,mail but all the rest of your disabled functions have spaces in between them.

    We expect to have an update to the plugin released by Monday, 15 February to fix this for you. In the meantime, you could consider disabling WP_DEBUG_DISPLAY so that the errors don’t show up in your dashboard.

    Thread Starter ipapagi

    (@ipapagi)

    3 years, 2 months ago

    Hi @jessecowens

    Thank you for your support.

    I’m waiting for your fix!

    Best regards!

    Plugin Contributor Jesse Owens

    (@jessecowens)

    3 years, 2 months ago

    Hi @ipapagi –

    Sorry for the delay! Total Upkeep 1.14.11 has just been released to address this bug for you.

    Please let us know if you have any more issues, we’re happy to help.

    Plugin Author Brad Markle

    (@bwmarkle)

    3 years, 2 months ago

    Hi @ipapagi, we just released Total Upkeep version 1.14.11. Are you able to upgrade, test, and let us know if the warnings have stopped showing?

    Thread Starter ipapagi

    (@ipapagi)

    3 years, 2 months ago

    Hi @jessecowens & @bwmarkle

    Thanks for the correction. I have just upgraded the Total Upkeep to the latest version and the warnings have been disappeared!

    Keep up your great job!

    Regards!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Warning messages in Version 1.14.10’ is closed to new replies.

Tags