We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 12110
    • 122 Posts
    Hello,

    huh we have a MODx 0.9.6.1.p version running. Everything has been fine for two weeks, but since today there’s a strange error message in the server logs when I try to access the manager login, the browser only showing a blank page (all folder and file rights are set correctly):
    PHP Warning: include_once(quotes_stripper.inc.php) [<a href='function.include-once'>function.include-once</a>]: failed to open stream: No such file or directory in /srv/www/vhosts/rosenheim2010.de/httpdocs/modx/manager/index.php on line 90 


    Followed by a lot of other error messages, mainly includes and classes failure.

    The site itself can be accessed, even friendly URLs are still working.
    I tried an upgrade install, everything was green, accessible and working, but the problem remains the same ...
    (If anybody from Germany is reading this: it’s on a 1&1 Linux Root Server).

    PHP Version is 5.2.3., magic_quotes_gpc Off, magic_quotes_runtime Off, register_globals Off

    Any help is greatly appreciated! Thanks!!!
      • 7231
      • 4,205 Posts
      Don’t have a solution but if you add the index.php to the url for the manager you can get the manager login page. I would guess that this may be a FURL issue.
        [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

        Something is happening here, but you don&#39;t know what it is.
        Do you, Mr. Jones? - [bob dylan]
        • 12110
        • 122 Posts
        I had tried that, thanks. Unfortunately it doesn’t work too ...

        In Firefox there’s still a blank page, in IE7 the Login form appears, then after logging in ... a blank page. But I’m logged in then ... and see Quickedit on the pages.

        Just tested some of my other MODx sites, they are working perfectly. But this one is strange ...
          • 12110
          • 122 Posts
          Hello,

          after some phone calls it was clear that the problem came from the provider - they had applied changes to a vConfig file on a their rented Linux server. Don’t know exactly as the technician wasn’t available, but they changed back and now the manager is running fine again.

          Thanks for the hint about the charset - the templates need to be adapted to utf-8, thats’s right.

          Thanks for your help! (By the way: Is the [solved] in the title the correct way to mark this?)
            • 28042 ☆ A M B ☆
            • 24,524 Posts
            You can also use [(modx_charset)] in your template, that way it’s consistent no matter what you do with your configuration.
              Studying MODX in the desert - http://sottwell.com
              Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
              Join the Slack Community - http://modx.org
              • 12110
              • 122 Posts
              Thanks! Wasn’t aware of this doc variable before.