• Resolved renoirb

    (@renoirb)


    If you see your web server sending messages similar to:

    Failed to determine HOME directory after trying "sh: 1: cd: can't cd to ~" (exit code 2)

    Or some error message saying it failed to execute such as:

    PHP Warning: exec() has been disabled for security reasons

    Using such hacks is good when you want to facilitate team work while developing. But when you deploy your site for general public usage… YOU SHOULD ALWAYS make sure you actually address the warnings. Not just mute them.

    What is the problem then?

    The reason is that the development helpers of a library used by this plugin tries to figure out configurations. When you are deploying, you do not need the code to always try to figure out things we do not need.

    Fortunately, they added a way to completely disable it. In consequence, we do not get the error message.

    The root of the problem is in the included library AWSSDKforPHP

    wp-content/plugins/dreamobjects/AWSSDKforPHP/sdk.class.php

    Solution:

    Add this line in your wp-config.php file:

    # Due to dreamobjects plugin errors
        define('AWS_DISABLE_CONFIG_AUTO_DISCOVERY', true);

    http://wordpress.org/plugins/dreamobjects/

Viewing 1 replies (of 1 total)
  • Plugin Author Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    I’m going to slip that into the plugin for you guys… You’re right, there’s no need for it.

    (FYI, it’s set to check – if you already defined it, it won’t define it, but if you haven’t, it will, so if someone needs to override, that should work)

Viewing 1 replies (of 1 total)
  • The topic ‘Log is complaining "Failed to determine HOME directory"’ is closed to new replies.