We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36711
    • 68 Posts
    hi

    I am using MODX Revo vers 2.1.3-pl and have been having problems with 500 internal error page at both backend and front end sides pretty often
    now, the only solution which looks to be solving this issue, was disabling all cache items in system settings
    this is not the first time I'm raising this issue and got several valuable feedbacks from other developers from which one was that of the hosting might be running out of free space and this would be one which causes this error
    however our hosting provider let us know that this problem is out of question since there is no any limit on disk space

    our problem is, that by disabling the cache, the websites loads much slower than previously

    so, I would appreciate if someone would guide us or let us know his opinion what might cause the 500 internal error when cache is enabled

    thanx in advance
      sherlockseo
      • 22303 MODX Staff
      • 10,725 Posts
      Generally this is going to be caused by a Plugin or Snippet that had code which is dependent on something that is perhaps not available when run from a cached copy. It could also be a problem with the hosting environment, but you'll have to provide details for us to be able to pinpoint the specific problem.
        • 36711
        • 68 Posts
        thanx opengeek
        you are most probably right, this is what we also think
        now, I'm just thinking about which way would be more efficient to test all snippets, meaning to filter out the one which might have the code dependent on something not available from a cached copy

        any suggestion?
          sherlockseo
          • 22303 MODX Staff
          • 10,725 Posts
          Try disabling tags in the content until you get a non-blank response. An easy way to do this is to put a space in between the two brackets, e.g.
          [ [foo? &bar=`1`] ]
          .

          FWIW, in MODX 2.1.4/2.2.0 you can use a - token after the opening tags to have a tag ignored — this is the new comment tag syntax.
          [[-foo? &bar=`1`]]
            • 36711
            • 68 Posts
            sorry opengeek for my late response sad

            thanx, I find your reply very valuable
              sherlockseo