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

    I’m getting a warning that the output.class.inc.php file doesn’t exist when I try to load the website. If however I change the module path of the quickedit module in the Manage Modules section from "assets/modules/quick_edit" to "/assets/modules/quick_edit" (note just added a / in front) , the website loads, but then the quickedit front-end editor doesn’t work. And I haven’t done this installation different than the other numerous I’ve done, where this problem doesn’t occur.

    Can someone please help me troubleshoot this issue? I’ve read in the forums and it looks like it suggests I make the folder writeable or something. I’ve tried this, but didn’t make any difference.

    MODx version - 0.9.6.1p2
    IIS / PHP5

    Thanks
    Ettiene
      • 9162
      • 39 Posts
      Please guys can someone assist me? If I’m not posting enough info or doing something stupid that causes people to ignore this post, then I apologise and would love for someone to tell me what info is still missing. smiley

      Thanks
      Ettiene
        • 7231
        • 4,205 Posts
        Do you have the <base> tag set in your template?
          [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]
          • 9162
          • 39 Posts
          I’ve got this:

          <base href="[(base_url)]" />


          Is it correct?
            • 7231
            • 4,205 Posts
            That looks correct, although some people recommend using: <base href="[(base_url)]"></base> due to some ie6 bug. But that is irrelevant. Could it be somehow related to your htaccess settings?

            Could your base path be set incorrectly? This is in site configuration in the manager. I have read that sometimes it may need to be set manually.

            If possible post the error that is output, maybe there is a clue in the message.
              [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]
              • 9162
              • 39 Posts
              Hi there,

              i’m on IIS, and FURL’s aren’t enabled at the moment. Therefore I’m not using .htaccess or httpd.ini files at the moment. I could enable it if you want.

              Also, I can’t find anywhere in the Site configuration in the Manager where one can modify or set the base path. Maybe I’m blind smiley

              Anyways, here is the parse error output:

              « MODx Parse Error »
              MODx encountered the following error while attempting to parse the requested resource:
              « PHP Parse Error »
               
              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: 	C:\Domains\jacobsbaaidev.co.za\wwwroot\manager\includes\document.parser.class.inc.php(745) : eval()'d code	 
                Line: 	70	 
               
              Parser timing
                MySQL: 	0.0183 s	(3 Requests)
                PHP: 	0.0259 s	 
                Total: 	0.0442 s
                • 7231
                • 4,205 Posts
                IIS is not my area, but the message in the manager states that there could be issues with the paths with IIS servers. To check the paths go to the manager and go to Tools >> Configuration and select the "Interface & Features" tab about half way down there is the "Resource path:" setting and right bellow it there is the "Resource URL".

                This is the warning that is posted with the resource path:
                Enter the physical path to the resource directory. This setting is usually automatically generated. If you’re using IIS, however, MODx may not be able to work the path out on its own, causing the Resource Browser to show an error. In that case, you can enter the path to the images directory here (the path as you’d see it in Windows Explorer). NOTE: The resource directory must contain the subfolders images, files, flash and media in order for the resource browser to function correctly.

                I am on a mac and have never hosted on IIS so I may not be much help rolleyes
                  [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]
                  • 9162
                  • 39 Posts
                  Hi there,

                  Thanks for the reply. The weird thing is that I’ve got about 10 other sites that’s hosted on IIS (same shared server too) too, same settings and all, and they work fine. Anyways the resource path and URL values are as follows:

                  Resource path: C:/Domains/jacobsbaaidev.co.za/wwwroot/assets/
                  Resource URL: assets/

                  That looks ok to you?
                    • 25867
                    • 1 Posts
                    I got a same problem but I find that that happen only on Opera browser. IE, FF works OK!
                    Please - do some think with this bug!
                      • 22303 MODX Staff
                      • 10,725 Posts
                      Quote from: ettiene at Sep 05, 2008, 05:36 PM

                      I’ve got this:

                      <base href="[(base_url)]" />


                      Is it correct?
                      That is not correct, [(site_url)] not [(base_url)] -- very important!