We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 24250
    • 18 Posts
    Hi,
    i have big problems with one MODx installation.
    I have several installations for different websites, hosted on the same server. One of them has problems with includes or the paths to include.
    PHP error debug
      Error:     include_once(assets/modules/quick_edit/output.class.inc.php) [function.include-once]: failed to open stream: No such file or directory   
      Error type/ Nr.:     Warning - 2   
      File: /var/www/web178/html/de/manager/includes/document.parser.class.inc.php(745) : eval()'d code   
      Line:     70

    i had to disable and rename the quickedit directory to get MODx working.

    Some others snippets cause similar errors, like WebLoginPE. I had to recode the snippet an put an dotslash "./" to all includepaths the errormessage tells me to, to make it work.
    I am not a good programmer or serveradmin to know why that happens expecially when all other installations (same server afaik) work well.
    MDDx version is 0.9.6.3
    PHP Version 5.2.0-8+etch13

    Any Ideas so far?
    R.J.

    [table][tr][td]System [/td][td]Linux 2.6.22-3-vserver-amd64 #1 SMP Tue Feb 12 10:01:41 UTC 2008 x86_64[/td][/tr]
    [tr][td]Build Date[/td] [td]Sep 30 2008 18:34:19[/td][/tr]
    [tr][td]Server API[/td] [td]CGI/FastCGI[/td][/tr]
    [tr][td]Virtual Directory Support[/td] [td]disabled[/td][/tr]
    [tr][td]Configuration File (php.ini) Path[/td] [td]/etc/apache2/confixx_phpini/web276/1/php.ini[/td][/tr]
    [tr][td]Scan this dir for additional .ini files[/td] [td]/etc/php5/cgi/conf.d[/td][/tr]
    [tr][td]additional .ini files parsed[/td] [td]/etc/php5/cgi/conf.d/gd.ini, /etc/php5/cgi/conf.d/imap.ini, /etc/php5/cgi/conf.d/mcrypt.ini, /etc/php5/cgi/conf.d/mysql.ini, /etc/php5/cgi/conf.d/mysqli.ini, /etc/php5/cgi/conf.d/pdo.ini, /etc/php5/cgi/conf.d/pdo_mysql.ini, /etc/php5/cgi/conf.d/xsl.ini[/td][/tr]
    [tr][td]PHP API[/td] [td]20041225[/td][/tr]
    [tr][td]PHP Extension[/td] [td]20060613[/td][/tr]
    [tr][td]Zend Extension[/td] [td]220060519[/td][/tr]
    [tr][td]Debug Build[/td] [td]no[/td][/tr]
    [tr][td]Thread Safety[/td] [td]disabled[/td][/tr]
    [tr][td]Zend Memory Manager[/td] [td]enabled[/td][/tr]
    [tr][td]IPv6 Support [/td] [td]enabled[/td][/tr]
    [/table]
      • 22303 MODX Staff
      • 10,725 Posts
      PHP 5.2.0, seriously? That version is badly broken no doubt. I’d update your environment first, then see if it’s something to do with configuration. Honestly, you need to be running 5.2.5/6 or 5.2.8 if running the 5.2.x series and you want a stable experience.

      However, this may just be related to open_basedir restrictions. See if those are enabled and how they are configured.
        • 24250
        • 18 Posts
        This is an estreme low-budget webhosting, though i have no access to upgrade anything sad
        I am wondering, because other installations (same server, same php-version) are runnung without any problems. The only difference i see ist the Configuration File (php.ini) Path.
          • 17846
          • 17 Posts
          OpenGeek, where did you hear about 5.2.0 being a bad version? I just moved to another server and they installed this version, so I’m a bit worried what the problems could be and I can’t find much information on the net. Thanks.
            • 22303 MODX Staff
            • 10,725 Posts
            Quote from: MackenzieB at Mar 09, 2009, 12:48 PM

            OpenGeek, where did you hear about 5.2.0 being a bad version? I just moved to another server and they installed this version, so I’m a bit worried what the problems could be and I can’t find much information on the net. Thanks.
            I didn’t "hear" about it anywhere per se; software just has bugs (and don’t forget security vulnerabilities) and there have been 8 releases since 5.2.0 to fix a great many of them. I just prefer as secure and bug-free an experience with my servers as I can get, that’s all. wink Excuse my abrupt response on that; I’ll try to contain myself in the future.

            I have no explanation for the QuickEdit problem on one domain unless maybe that file just got corrupted (or missed) in transfer to the site (if you FTP’d it there), or for some reason there are include_path restrictions or misconfigurations involved as I suggested.

            For WebLoginPE, I’d post something about that problem here.
              • 17846
              • 17 Posts
              Quote from: OpenGeek at Mar 09, 2009, 07:24 PM

              I didn’t "hear" about it anywhere per se; software just has bugs (and don’t forget security vulnerabilities) and there have been 8 releases since 5.2.0 to fix a great many of them.
              Why 8 new releases if there weren’t any issues... Never thought of that embarrassed

              Quote from: OpenGeek at Mar 09, 2009, 07:24 PM

              Excuse my abrupt response on that; I’ll try to contain myself in the future.
              No worries there! grin