Removing old Structure Nav History to keep DB size down

Justin Alei's Avatar

Justin Alei

05 Jun, 2017 05:47 PM

Hi guys,
I forgot to add the $config['structure_nav_history'] = 'n'; setting after an upgrade and the database has gotten massive because of the history feature. I've since added the config setting turning this off, but could you just confirm that truncating the exp_structure_nav_history table is safe/correct way to remove all the Structure Nav History entries without affecting the 'live' or 'current' pages? I couldn't see anything in the docs, on here or Stack Exchange.

Thanks,
Justin

  1. Support Staff 1 Posted by Support on 05 Jun, 2017 06:37 PM

    Support's Avatar

    Yes, truncating the exp_structure_nav_history table is correct. We don't recommend the structure_nav_history setting to disable it as that leaves you without a safety net in the event something happens to your Structure tree.

    We are working on adding a self-pruning feature to the next version of Structure to help keep the size of the nav_history table in check.

  2. Support closed this discussion on 05 Jun, 2017 06:37 PM.

  3. Justin Alei re-opened this discussion on 05 Jun, 2017 06:44 PM

  4. 2 Posted by Justin Alei on 05 Jun, 2017 06:44 PM

    Justin Alei's Avatar

    Great, thanks for confirming! Yes, a self-pruning function would be useful for sure.

  5. Support closed this discussion on 05 Jun, 2017 06:46 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac