We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 30100
    • 58 Posts
    Yesterday when I was intergrating NewsEditor 1.0 and NewsPublisher 1.4 to my site I suddeny got this errormessage:

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 67564 bytes) in /home/tirithen/public_html/visbok/manager/processors/cache_sync.class.processor.php on line 35


    My site works fine except that as soon as I try to enter or change something in the database I get this error on the manager side, on the front end side when I try to publish or edit an "article" I get a blank page. The problem first appeared when I was setting a link in all my main documents to NewsEditor to allow a logged in user to change the page.

    I connected to the MySQL server with phpMyAdmin to see that my database was still there, the largest table I could find was one of the logs, about 1200 posts and I emptied that table.

    Yes I did get a message right before it stopped working something about the document cannot be its own parent or something alike and the errormessage looks like a eternity loop that drains the allowed memory but how do I find the error? I cannot do anything with my site as for now. :’(

    My system is MODx-version 0.9.6.1p2 on Apache/2.2.4 (Ubuntu) PHP/5.2.3-1ubuntu6.3 (mod_php5)
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      Sounds like somehow you’ve got a document whose parent ID is its own ID. This is not supposed to be able to happen, but if it did it would certainly cause such a loop. Go to your phpMyAdmin for the content table, and in the Query tab replace the "WHERE 1" part with "WHERE `parent` = `id`".
      SELECT * FROM `modx_site_content` WHERE `parent` = `id`
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 30100
        • 58 Posts
        Yes that’s it! Thanks a lot, still don’t know how I managed to get it like that though. But now it works fine again. :-D
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          Looks like somebody needs to take a close look at those snippets to find out under what conditions the parent ID is saved even though it’s the same as the document’s ID. It sounds like it generated the error, but saved the value anyway.
            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org