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

    I got an http 500 error - internal server error on my web context.

    PHP-Version 5.3.3
    MODX 2.2.5 (i know, time to update to 2.2.6 smiley

    I'm operating a multilingual site with contexts web/en/it/nl and the babel extra. As seen on http://designfromwithin.com/blog-webdesign-development/2012/01/12/modx-multilingual-setting-up-babel-and-have-a-website-with-multible-languages/ this setup worked for months now.

    url structure is like
    domain.com
    domain.com/en/
    domain.com/it/
    domain.com/nl/

    The strange thing: suddenly the web-context throws that error, en/it/nl-contexts just work fine.
    I didn't do really exciting stuff, only thing I can remember (what may have caused the problem, but really not sure): i tried to make a custom hook for FormIT like in the tutorial on the rtfm http://rtfm.modx.com/display/ADDON/FormIt.Examples.Custom+Hook.

    so I pasted this code right into my snippet:
    $modx->log(xPDO::LOG_LEVEL_ERROR,'Testing my custom hook.');
    return true;  //<-- if you omit this or return false, your form won't validate
    


    No changes made to the .htaccess, our hosting provider told me there were no errors in the apache log file.

    Only Error in the modx log is

    [2013-01-08 15:43:19] (ERROR @ /index.php) `[[+id]]` is not a valid integer and may not be passed to makeUrl()
    


    I don't think this caused the web context to stop working, as this error is there since 3 weeks (I've deferred fixing this problem).

    Hope u wizards can help me at least getting a meaningful error log for fixing that problem.

    I apologize for my bad english
      • 33968
      • 863 Posts
      Anything in your php error log?
        • 35814
        • 7 Posts
        Not quite sure where I can find it?

        After updating to 2.2.6 w/o problems the error seems to be gone, but now I get a white page.

        Another look at the modx error log showed me

        [2013-01-08 17:48:53] (ERROR @ /index.php) Could not get table class for class: modAccessContext


        This error got logged short after I switched the site_status to 0 in the system settings (before I uploaded the files for the update).

        Thx for your time Lucas smiley
          • 33968
          • 863 Posts
          Hmmm if you just upgraded, make sure you completely clear out the cache then try again. Is the error on all contexts or just web?
            • 35814
            • 7 Posts
            Quote from: okyanet at Jan 08, 2013, 11:15 AM
            Hmmm if you just upgraded, make sure you completely clear out the cache then try again. Is the error on all contexts or just web?

            oh my... I got it by myself. I could slap myself right away for not seeing the missing ";" at the end of the line in my lexicon file (I knew I was updating those strings, checked that file already for typos)

            This caused the whole context to get screwed up.

            Better check those things more accurate.

            Thanks for your time spent on my problem Lucas smiley
              • 33968
              • 863 Posts
              Haha, no problem - I usually realise the mistake within an hour of posting it to the forum anyway smiley