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

    I have read several threads where people have had issues with infinite save loops when templates and resources. In my case the loop occures when resources are attempted to be saved. The resource does get saved when the page is refreshed (after the loop has gone for a while), but this is not something I can deal with anymore... I have seen solutions on other threads like making sure the modx timezone is set to the same timezone as the php.ini file, setting modx_cache_disabled = true in config.inc.php, running the setup, but none of these are working for me. I have no clue what changed overnight to cause this problem. I am getting the error
    uncaught exception: [object Object]
    when I look at the console in firebug (firefox plugin) and the error
    Failed to load resource: the server responded with a status of 500 (Internal Server Error) - DOMAIN/connectors/resource/index.php
    Uncaught #<Object> - ext-all.js:7

    I am also getting several instances of the following error in my modx error log
    [2013-09-03 11:25:48] (ERROR @ /connectors/element/propertyset.php) Error caching lexicon topic lexicon/en/core/default
    [2013-09-03 14:00:49] (ERROR @ /connectors/system/log.php) Could not load class: unknown from mysql.unknown



    I am running MODX Revolution 2.2.2-pl and it has been working perfectly for almost a year now. I have no clue what has changed, but I would really like to get it resolved! I am open to any suggestions!
      • 42035
      • 90 Posts
      Hi jsteffan1

      One of the solution for this which i know is
      First check all the template variables value in the resource which has validation of blank value.
      You will see the red line below the text of template variable which is blank.

      Second one check all the code in template which is applied to that resource make sure there is any code like this Javascript:void(0); or any Javascript call there. If yes than put this code in any chunk or snippet than try to save resource.

      Some words like "casino" are restricted in content of resource in tinymce editor. So make sure there would be no words like this in the Tinymce editor of content in Resource.
        Arkalp.com
        • 37210
        • 131 Posts
        Hi jsteffan,

        You can try what Vinod said..but if you're saying that things changed overnight, it's most likely a server issue.

        Give your server provider a call and see if anything has been changed.

        Sar
          • 39990
          • 45 Posts
          Thank you for the responses Vinod and insightdesign! I think what makes this situation so weird is I don't have any template variables on this modx instillation and I have 2 other MODX websites running on this server that work perfectly. One of them even has the same templates with different styles. The web server hosting this site is a web server I have built and haven't touched the apache, php or mysql configurations for a very long time. I tried putting the database on a test server and pointing the modx instillation to that database and it worked perfectly so it is not a database problem. I think I am going to install a new modx instillation and have it look at the current database and see if that solves the problem.
            • 36533
            • 65 Posts
            I would clear your core/cache folder first if you haven't tried that yet. I recall running into this very same problem and that cleared it up for me.
              • 39990
              • 45 Posts
              Thank you nuwebstudios! I tried deleting the components of core/cache and that didn't seem to do anything... still stuck...
                • 39990
                • 45 Posts
                I was finally able to find the problem. I ran the command
                tail -f /var/log/apache2/error_log
                in my terminal and watched the PHP Notice errors as my sites on this server were browsed. I tried saving a resource and noticed that in the log file there was a fatal error with a plugin that I had removed. I re-installed the plugin and it worked perfectly!