We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 16009
    • 23 Posts
    I put a simple index.html file in public_html, and www.krueckeberg.org renders immediately. I just don’t get what is going on. It is not the browser because the same long rendering time occurs with IE6 and Opera 8.51.
      • 696
      • 46 Posts
      Your problem as stated before is with the JavaScript Files... they are being called through port 81 for some reson unknown to man, but all your internal links are looking on port 81, and so it takes almost forever trying to find each file untill it times out...



      Broken links, ordered by link:

      http://jigsaw.w3.org/css-validator/check/referer
      error code: 400 (no object data), linked from page(s):
      http://www.krueckeberg.org/modx/

      http://krueckeberg.org:81/modx/index.php?id=1
      error code: 12002 (timeout), linked from page(s):
      http://www.krueckeberg.org/modx/

      http://krueckeberg.org:81/modx/index.php?id=11
      error code: 12002 (timeout), linked from page(s):
      http://www.krueckeberg.org/modx/

      http://krueckeberg.org:81/modx/manager/media/script/scriptaculous/prototype.js
      error code: 12002 (timeout), linked from page(s):
      http://www.krueckeberg.org/modx/

      http://krueckeberg.org:81/modx/manager/media/script/scriptaculous/scriptaculous.js
      error code: 12002 (timeout), linked from page(s):
      http://www.krueckeberg.org/modx/

      5 broken link(s) reported

      The Js files when being refrenced using the correct port work instantly... http://krueckeberg.org/modx/manager/media/script/scriptaculous/scriptaculous.js
        • 16009
        • 23 Posts
        After informing my ISP that "I believe that the JavaScript Files are being called through port 81 for some reason, and so it takes almost forever trying to find each file untill it times out", the IPS said:

        "You’re experiencing problems because of the way we have to redirect to the internal PHP5 server. You need to make sure your code is not automatically building redirects based on the tcp port the original request was received. This will cause it to try to redirect the end-user (your browser) to port 81, which will not work. You need to hardcode port 80 into your code so that any redirects send you to the public apache listener."

        Does this response make sense. I’m just a average Joe. How would I go about hardcoding port 80 into the code? Is that even practicable?
          • 1764
          • 680 Posts
          okay, is it me or is this just weird? Why would your site be over part 81 and what do redirects have to do with JS includes?

          To answer your question there really isn’t a very simple way to hard code port 80 into the redirects and I doubt that it would help much anyway since I can’t think of any redirects that should be going on when accessing the homepage.

          Have you tried this? Create a new template with nothing but [*content*] in the body, use the template in one of the pages on your site and then try to acess it. Do you still get get the delay?

          I certainly could be wrong but I just can’t think of any reason to hard code ports into the redirects.
            • 32963
            • 1,732 Posts
            Ok I think I see what’s happening here.

            I think you can try hard coding the base_path and base_url values inside the config.inc.php file.

            You can hard code these settings inside your manager/includes/config.inc.php file just below line 14 or below the line that contains "$site_sessionname= ".

            example:
            $base_url = "http://domain.com/modx";
            $base_path = "c:/webroot/modx";
            $site_url = "http://domain.com/modx";




              xWisdom
              www.xwisdomhtml.com
              The fear of the Lord is the beginning of wisdom:
              MODx Co-Founder - Create and do more with less.
              • 16009
              • 23 Posts
              Thanks, I’ll give that a try.
                • 16009
                • 23 Posts
                I think I’ll have to change ISP to really ’fix’ this weird problem. I added

                $base_url = "http://www.krueckeberg.com/modx";
                $base_path = "/home/kkruecke/public_html/modx";
                $site_url = "http://www.krueckeberg.com/modx";

                these lines below
                $site_sessionname = "SN439f125479909";
                and still got "time out" problem.
                  • 32241
                  • 1,495 Posts
                  Sorry if I’m not quite following this.

                  But why don’t you try to add port 80 to the url?

                  For example, http://www.krueckeberg.com:80/modx

                  Let see whether it works or not.

                    Wendy Novianto
                    [font=Verdana]PT DJAMOER Technology Media
                    [font=Verdana]Xituz Media