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

    Thanks for the detailed information. I appreciate it.

    Ok, I did downgrade eform from 1.4.3 to 1.4.2 and have had no errors since (in the past 24+ hours). Could it be the eform 1.4.3 (form submission) was causing the errors?

    I will monitor it over the weekend and post the update. Hope I don’t see those errors any more smiley

    Thanks for all the help guys!

    -Raavi
      • 33372
      • 1,611 Posts
      I haven’t seen anything in particular about eForm that would cause this, but I think you should post your experience to the eForm board because if this is a problem with the new version they’ll want to know about it.

      Glad it’s fixed for you now.
        "Things are not what they appear to be; nor are they otherwise." - Buddha

        "Well, gee, Buddha - that wasn't very helpful..." - ZAP

        Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
        • 24278
        • 165 Posts
        Sorry guys, looks like eform is not causing the errors. I have another 3500 errors in the morning. I’m so confused.
          • 24278
          • 165 Posts
          One query.
          I am running " FirstChildRedirect", can the functionality of this snippet cause the "Too many forward attempts." error when overloaded with many requests.
          -Raavi
            • 33372
            • 1,611 Posts
            If this snippet is broken or misconfigured I could imagine that happening. I don’t think it could be "overloaded" with requests, however. This snippet only forwards once, so unless you have nested folders with multiple calls of this snippet it should never loop.

            By default, the FirstChildRedirect snippet forwards to the site start page if no documents are found in the folder (so check that your site start page is set to an existing published document that doesn’t also run this snippet). Also check your caching setup for your snippet call (I believe it should be run uncached). And of course you should verify that you have the correct settings in the menuindex fields of your documents, since that’s how this snippet chooses which document to forward to.

            If you can, try removing this snippet for a while as a test to see if it is the cause or not. This resource has been deprecated, but I’m not sure why that is. Maybe OpenGeek can fill us in on that...

              "Things are not what they appear to be; nor are they otherwise." - Buddha

              "Well, gee, Buddha - that wasn't very helpful..." - ZAP

              Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
              • 24278
              • 165 Posts
              Ok ZAP, will try disabling the snippet.

              I am just running one instance of the FirstChildRedirect snippet and am pointing to an existing document. And YES the start page is available and published.

              Is there any other information I can provide, that will help in addressing this issue.

              -Raavi
                • 25663 MODX Staff
                • 12,272 Posts
                Raavi, please PM me a manager login and I’ll see if anything immediately jumps out.
                  Ryan Thrash, MODX Co-Founder
                  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me