We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28120
    • 380 Posts
    Is it ok for me to truncate


    • modx_site_content_history
    • modx_event_log

    since they’re getting large ....

    Thanks

    Mark
      • 4310
      • 2,310 Posts
      I think modx_site_content_history is an extra table probably added by the content history add on.
      Truncating modx_event_log should be okay, however it’s worth checking what the entries are, maybe they indicate a problem that requires atttention.
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        You can clear the event log from the Manager, Reports -> System Events, and clear the log.
          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
          • 36404
          • 307 Posts
          hi,

          you can truncate prefix_manager_log too (can get a bit bulky during the dev time...) without any problem

          have swing
            réfléchir avant d'agir
            • 26931
            • 2,314 Posts
            this one is handy, too http://modxcms.com/forums/index.php/topic,31114.msg188861.html#msg188861

            // snippet householding
            // modx "householding" chores:
            // getting rid of old system event logs + manager logs in database
            // + optimize tables (stuff you normally do in phpMyAdmin or one-by-one in manager > reports)
            // use this snippet inside a page that is only accessed once a day, e.g. google-sitemap xml doc = poor man’s cron job smiley
            // optional parameter: days, e.g. [!householding? &days=`30`!] -> will delete log entries older than 30 days
              • 28120
              • 380 Posts
              Great - thanks for all the responses!