We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 82
    • 17 Posts
    I just started receiving this today. Does this error mean that the server is not allow access to this file?
    « MODx Parse Error »
    
    MODx encountered the following error while attempting to parse the requested resource:
    « PHP Parse Error »
     
    PHP error debug
      Error:	Unknown(): URL file-access is disabled in the server configuration	 
      Error type/ Nr.:	Warning - 2	 
      File:	/hermes/web06/b1808/moo.ndmile/weddings/manager/includes/document.parser.class.inc.php(766) : eval()'d code	 
      Line:	2


      • 28042 ☆ A M B ☆
      • 24,524 Posts
      It means that you cannot access a file with a URL but must use a filesystem path. A snippet or plugin is using an ambiguous path to an include file, most likely. Check line 2 of the offending snippet or plugin and make sure it’s using a proper path. Perhaps simply adding ./ to the beginning of the path string will suffice.
        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
        • 82
        • 17 Posts
        Thanks for the reply Scott. I am not sure this is the issue. This started happening literally out of nowhere. I only access this portion of my site (the manager side at least) once every 3-4 days and this problem started 3 days after my last change (which was adding a page by duplicating an old one and changing the necessary values). I have not touched any of my snippets or plugins in a few months. To be honest, I am only using 2-3 custom snippets and 0 custom plug-ins. I only use the ModX portion of the site to display clients wedding videos so it did not need a lot of customization. And as I said, this started out of the blue.

        Any suggestions?
          • 82
          • 17 Posts
          I bet you are right. I informed them about the problem and now it is working like normal. So it was not ModX’s fault nor mine! Yippee!