We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Noise in the logs...

    • 9207 ☆ A M B ☆
    • 2,475 Posts
    Everett Reply #1, 15 years, 6 months ago
    Seeing a lot of stuff in the logs... there’s a huge dump that starts with this:

    [2011-03-25 21:59:38] (ERROR @ /var/www/vhosts/oursite.com/httpdocs/core/model/modx/modmanagerresponse.class.php : 391) PHP warning: file_exists() [<a href='function.file-exists'>function.file-exists</a>]: open_basedir restriction in effect. File(/var/www/vhosts/oursite.com/httpdocs/manager/assets/modext/<script type="text/javascript">
//<![CDATA[


    Any ideas what might have caused that? Seeing open_basedir makes me thing it’s related to permissions...

    MODx 2.0.8-traditional
    PHP 5.2.6
    Redhat Linux (not sure of the version)
    Linux (?)
      Hosting stuff: http://fireproofsocks.com/
      Coding stuff: http://craftsmancoding.com/
      Blog stuff: http://tipsfor.us/
      • 14635
      • 5 Posts
      jonb Reply #2, 15 years, 3 months ago
      Did you get anywhere with this? Im seeing the same.

      Thanks,
      Jon.

        • 25663 MODX Staff
        • 12,272 Posts
        Ryan Thrash Reply #3, 15 years, 3 months ago
        Everett, is this still happening with 2.1.1?
          Ryan Thrash, MODX Co-Founder
          Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
          • 9207 ☆ A M B ☆
          • 2,475 Posts
          Everett Reply #4, 15 years, 3 months ago
          tt has to do with PHP’s open_basedir restrictions -- that’s a safer setting, but I’ve had to disable it on my host. I’ve had problems with all my PHP sites (not just MODx) on my host because I haven’t configured that directive correctly, it seems... so no, I haven’t really figured out the larger problem there, but I did figure out a solution.

          However, it does relate to some similar feature requests re more thorough checking of the file permissions after installation -- moving files around, changing user settings, etc. have all messed up my MODx installs on various occasions and nothing but a "re-install" of the same version has fixed it, which is pretty redonkulous since the only thing I need from the installation/setup is the permissions check. I think file permissions should be checked during manager login or a menu item should be tied to those tests. Too many things get wonky when the permissions are fudged... sometimes it’s really subtle and insidious when a file or directory isn’t writeable, for example.
            Hosting stuff: http://fireproofsocks.com/
            Coding stuff: http://craftsmancoding.com/
            Blog stuff: http://tipsfor.us/