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

    This fix also affects feedburner validation of rss feeds (ditto generated) !
      ----------------------------------------------------------
      http://www.linkedin.com/in/lucapost/
      http://www.twitter.com/lukwe/
      ----------------------------------------------------------
      • 28100
      • 66 Posts
      Yay!! I’ve been hunting for hours to find the reason why I was getting this error.
      All fixed now - thanks! smiley
        • 715
        • 15 Posts
        Good thing I stumbled upon this post. Getting rid of the error definitely speeds up the php engine and the pages seem to be served a lot faster.
          • 34162
          • 1 Posts
          I am having this same problem... see my post at http://modxcms.com/forums/index.php/topic,25607.0.html

          I don’t even know how to go about looking for a missing semi-colon in all the php code.

          What is interested in my case is that I get this issue even when I request a blank page (with no template) from modx... so that would seem to rule out a problem with any snippets...

          Brad
            • 10449
            • 956 Posts
            search highlight is a plugin, not a snippet. Go to RESOURCES > MANAGE RESOURCES > PLUGINS > Search Highlighting

            Either disable it completely, delete it or add the missing ;

            iirc, it was the 2nd last line:

            $output = str_replace(’<!--search_terms-->’,$highlightText,$output);

            Maybe check the repository if there’s a new version out: http://modxcms.com/repository.html
              • 34162
              • 1 Posts
              Thanks ganeshXL...

              I looked through my snippets, but didn’t think to check the plugins...

              The problem was another plugin I had installed to deal with ie png problems. I deleted the plugin and problem solved!

              Yikes, though... for the last week while that plugin was installed Google couldn’t crawl my site and removed many pages from the index! At least its fixed now.

              What still perplexs me is why the internal 500 error was invisible? Why did only search engines encounter it and not regular human browsers? I just wonder in case it happens again I don’t know how I"ll tell apart from the server log file...
              • Quote from: Bebradsm at May 14, 2008, 10:04 PM

                What still perplexs me is why the internal 500 error was invisible? Why did only search engines encounter it and not regular human browsers? I just wonder in case it happens again I don’t know how I"ll tell apart from the server log file...
                Everyone received a 500 error, but the content was still being delivered, so unless you looked at the response headers with say the Web Developer Extension for Firefox, you wouldn’t have noticed. The bots however see the 500 response code and stop looking.
                  • 10449
                  • 956 Posts
                  It’s a good idea to check Google Webmaster Tools periodically... They report 404 and 302 errors according to your sitemap xml - I reckon 500 errors will be reported there as well.

                  https://www.google.com/webmasters/tools/

                    • 4749
                    • 623 Posts
                    SearchHighlightPlugin - who woulda thunk? Solved, my problem too!
                      The MODx has you...
                      Utah Web Design
                      • 5529
                      • 70 Posts
                      I’m so glad this was here!

                      I had the same problem and deleting that plugin solved it! wink


                      Quote from: zballl at Feb 19, 2008, 08:31 PM

                      Thanks!
                      Disabling the plugin solves it.
                      I’m not using a local server, it is in production and opened to outside world...
                      I checked the header with Fiddler2 and with web developper toolbar FF plugin, who confirmed both the 500 error (also present in my apache logs).

                      Thanks again for you quick and precious help.