The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Upgrade php 4.4.4 => 4.4.7 and allow_url_fopen no longer works

Discussion in 'General Discussion' started by krisdv, Jul 16, 2007.

  1. krisdv

    krisdv Well-Known Member

    Joined:
    Jun 18, 2003
    Messages:
    175
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Belgium
    Although allow_url_fopen in php.ini is "On"

    Does anyone know why and in which version this behaviour has changed?
     
  2. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    In PHP 4.0.4 through 4.3.4 you could set this in any php.ini. However after that version it could only be set by the system-level php.ini.

    Full documentation available at:

    http://us.php.net/filesystem
     
  3. krisdv

    krisdv Well-Known Member

    Joined:
    Jun 18, 2003
    Messages:
    175
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Belgium
    It is strange one of the users only noticed the difference after the upgrade from 4.4.4 to 4.4.7
     
  4. Spiral

    Spiral BANNED

    Joined:
    Jun 24, 2005
    Messages:
    2,023
    Likes Received:
    7
    Trophy Points:
    0
    I would have to see the exact call being made by the client
    and the rest of the PHP.INI file and if they have any
    .htaccess setup, etc.

    There are a lot of factors that effect whether or not a remote
    URL file opening call would be successful or not that each
    goes way beyond "allow_url_fopen" in the PHP.INI file.

    I suspect you forgot to compile an important related extension
    like cURL for example or possibly set an incompatible setting
    such as safe mode being on for example. Both of those are
    just single examples of things that could mess up opening
    remote files.

    Then there is the factor of what the client is doing exactly ...

    If the client is trying to include a file remotely, that is different
    from using fopen to access a remote file, etc. It is also
    controlled by a totally different configuration flag now too.
     
Loading...

Share This Page