wp_option table ws_menu_editor auotload = yes

  • This is the biggest wp_options entry and autoload =yes.

    This is usually our biggest entry with autoload =yes.

    Accrodign to a post from 2 years prior this is because “it loads on everypages (admin)”. True.

    But that it not th ecase for non logged-in which is the main use of non-transactional website.

    Any ideas of the impact setting it to autoload = no instead ?

Viewing 1 replies (of 1 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    I have not measured the difference between autoload “yes” and “no”. It would probably vary depending on DB performance anyway. It would mean an additional SQL query on every admin page.

    If you’re very concerned about the size of this wp_options entry, you could try enabling configuration compression. To do that, go to the “Settings” tab, scroll down to “Debugging”, and enable this box: “Compress menu configuration data that’s stored in the database”. Then go back to the menu editor and click “Save Changes” there (no need to actually make any changes, just save the existing configuration again).

Viewing 1 replies (of 1 total)
  • The topic ‘wp_option table ws_menu_editor auotload = yes’ is closed to new replies.