Community Forums
Connect with us on LinkedIn
+ Reply to Thread
Results 1 to 4 of 4
  1. #1
    Member
    Join Date
    Jun 2003
    Location
    Belgium
    Posts
    174

    Default Upgrade php 4.4.4 => 4.4.7 and allow_url_fopen no longer works

    Although allow_url_fopen in php.ini is "On"

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

  2. #2
    Technical Product Specialist cPanelDavidG's Avatar
    Join Date
    Nov 2006
    Location
    Houston, TX
    Posts
    11,189
    cPanel/Enkompass Access Level

    Root Administrator

    Default

    Quote Originally Posted by krisdv View Post
    Although allow_url_fopen in php.ini is "On"

    Does anyone know why and in which version this behaviour has changed?
    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. #3
    Member
    Join Date
    Jun 2003
    Location
    Belgium
    Posts
    174

    Default

    It is strange one of the users only noticed the difference after the upgrade from 4.4.4 to 4.4.7

  4. #4
    BANNED
    Join Date
    Jun 2005
    Location
    Wild Wild West
    Posts
    2,025

    Default

    Quote Originally Posted by krisdv View Post
    It is strange one of the users only noticed the difference after the upgrade from 4.4.4 to 4.4.7
    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.

Similar Threads & Tags
Similar threads

  1. custom php.ini no longer works with PHP 5.2.8
    By Website Rob in forum cPanel and WHM Discussions
    Replies: 0
    Last Post: 01-07-2009, 06:30 PM
  2. PHP.ini file, confusion? My site no longer works right?
    By artisticimpulse in forum cPanel and WHM Discussions
    Replies: 25
    Last Post: 07-29-2007, 03:28 AM
  3. PHP Version 4.4.2, register_globals ON php.ini no longer works!
    By sh4ka in forum cPanel and WHM Discussions
    Replies: 1
    Last Post: 06-02-2006, 04:06 PM
  4. gcc - no longer works?
    By aquagerbil in forum cPanel and WHM Discussions
    Replies: 2
    Last Post: 11-30-2005, 12:57 PM
  5. Where is the proper php.ini? I want to turn allow_url_fopen off!
    By N9ne in forum cPanel and WHM Discussions
    Replies: 7
    Last Post: 10-23-2003, 01:39 PM
Linkedin       Facebook       Twitter       RSS       Flickr       YouTube