• digitalhead

    (@digitalhead)


    I just upgraded WordPress to 3.1 and lost my tweak that allowed installation from within the site. I installed Third Party Host Fix to solve it. It works, but I keep seeing this error:

    Warning: putenv() has been disabled for security reasons in ~/digitalhead.co.cc/htdocs/wp-content/plugins/third-party-host-fix/thirdpartyhostfixer.php on line 27

    It seems to still work, but the error is still there. It also came up with this directly after the install:

    The plugin generated 234 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

    Is there a fix or will there be an update for 3.1?

    https://www.ads-software.com/extend/plugins/third-party-host-fix/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author drenboy

    (@drenboy)

    Hi digitalhead,

    Looks like your webhost placed putenv into their disable_functions list.
    If the plugin works fine still, I’d recommend either:

    1. Check if your webhost can remove the putenv restriction or

    2. Simply disable the plugin when you’re not using it to install themes, other plugins.

    Hope this helps.

    Thread Starter digitalhead

    (@digitalhead)

    Thanks for the reply Drenboy. The plugin wasn’t working, so I disabled it until getting a response.

    I’m using a free hosting plan and anything that is disabled is a restriction of that hosting, so the host wouldn’t be willing to turn it on.

    I’ve been using a different method to be able to install and upgrade from within the installation. I found this on the webhost’s forums and it seems to work pretty well. I just put this code at the end of the wp-config.php file:

    if(is_admin()) {
    add_filter('filesystem_method', create_function('$a', 'return "direct";' ));
    define( 'FS_CHMOD_DIR', 0751 );
    }

    Apparently, the original form of this code also used putenv and that line was removed because it caused problems as well.

    To be honest, I’m not familiar enough with the code to know what the stuff in this snippet means, but it was well approved by the host’s admins. Otherwise, I wouldn’t have trusted putting it into my site.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Error at top of page after installing Third Party Host Fix in 3.1’ is closed to new replies.