How are you dealing with 100+ sub-dom sites’ configs?

  • All sites are meant to be just sections of the same sight, but even just the menu system is fighting back.

    I want to maintain one menu, and all are updated, as the all should use the same, so no updating 100+ menus every time.

    Same with themes, but each site seems to have its own theme resources & config, and not cfg’d to use a ‘master’. Updated in both cases to orig/primary/master should automatically be seen in all, right?

    Can’t find how to do this, and playing with settings for 2 days trying isn’t helping.

    Ideas?

    1. Down to adding custom css in one theme, not a child.
    2. Max mega menu used.
    3. No idea how to tell my ‘theme engine’ I edit through…

Viewing 1 replies (of 1 total)
  • Moderator bcworkz

    (@bcworkz)

    The concept of a master menu is not implemented because the sites are intended to appear as completely separate, unrelated sites, much like wordpress.com sites.

    Changes to the main site’s theme only carries through to sub-sites when the change is made to the code base, such as templates. Changes to menus and settings are not related to the actual code base, so have no effect on sub-sites.

    I’ve no experience with Max Mega menu plugin, the following discussion applies to the default menu system. How my suggestions would be applied to Max Mega are best answered by the Max Mega developers.

    The menu items technically are not even part of the theme, they are custom post types unique to each site. In order to implement a “master” menu, you could develop a custom nav menu function to replace the usual wp_nav_menu() or whatever your theme uses. It would basically work the same way, except it would query menu item posts from the main site’s posts table instead of the usual sub-site table.

    You’d probably want to hide the admin menu page from site admins since any changes there would have no effect. Same goes for the customizer menu pane.

    Something similar could be done with other options, replace instances of get_option() with a function that gets options from the main site’s options table.

Viewing 1 replies (of 1 total)
  • The topic ‘How are you dealing with 100+ sub-dom sites’ configs?’ is closed to new replies.