We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 9207 ☆ A M B ☆
    • 2,475 Posts
    You can delete all of that -- this is best done via the manager, but if you have a full backup, you can be more adventurous and try it from the back-end (e.g. DELETE FROM xxxx WHERE 1);

      • 28042 ☆ A M B ☆
      • 24,524 Posts
      Better to use the TRUNCATE TABLE tablename for completely emptying a table. Deleting the items has to be done one by one (each row gets evaluated, and since 1 is true it gets deleted), and the auto-index value continues to be incremented (if you had 5,876 items and delete them all, the next one will still be 5,877). TRUNCATE TABLE (I think) actually drops the table, then re-creates it. Now all table metadata and other overhead is gone, your next entry will be auto-incremented to 1, and the whole process will be much faster and put much less of a load on the database.
        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
        • 9207 ☆ A M B ☆
        • 2,475 Posts
        Ooo... old thread. You can safely delete EVERYTHING from the modx_event_log and modx_manager_log tables -- it's just logging info, which may be valuable for auditing/debugging, but is not necessary for any functionality.

        Use MySQL's "TRUNCATE" command, e.g. type the following on a MySQL prompt:

        TRUNCATE modx_event_log;
        TRUNCATE modx_manager_log;