Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Russell Jamieson

    (@powerblogservice)

    Hi Paul,

    Genesis needs not only to be installed; it needs to be active too.

    I have not checked the plugin out on a multi-site installation.

    I will set one up, run some tests and get a fix out over the weekend.

    FYI: The way it detects Genesis on plugin activation is as follows

    public function is_genesis_present() {
    		return substr(basename( TEMPLATEPATH ), 0,7) == 'genesis' ; //is genesis the current parent theme
    }
    Plugin Author Russell Jamieson

    (@powerblogservice)

    When I wrote “active” above, I meant that either the Genesis framework or a Genesis child theme needs to be current theme.

    Thread Starter paulluxford

    (@paulluxford)

    Hi Russell,

    Thank you for your reply. Sorry I forgot to mention that I have Genesis installed and I have a child theme active.

    I look forward to using your plugin on my multisite.

    Really appreciate your help 🙂

    Paul

    Plugin Author Russell Jamieson

    (@powerblogservice)

    Hi Paul,

    I ran some tests of Dambuster on a multisite installation.

    I found that:

    1) When the theme on the main site was TwentyFifteen I was able to reproduce the problem as you described it

    2) However when I set the current theme on the Network main site to Genesis I was able to “Network Activate” Genesis Dambuster successfully

    My recommendation is that you “Network Enable” the plugin to make it available, and then allow each site to choose whether or not to activate the plugin, and how to configure it.

    Does that make sense?

    Hey Russel,

    Just a thought – since the plugin is intended only for Genesis but there could be a lot of non-Genesis thems installed in a multisite network (as we have in ours), could you surround the plugin with a function check for existence of Genesis?

    That way the plugin could be network activated and available to all sites on the network, and it would automatically be active ONLY when a genesis theme is activated, but without generating errors on non-Genesis themes. Users often change themes, i.e. Twenty Fifteen, then back to a Genesis theme, and so on.

    Thanks!

    Plugin Author Russell Jamieson

    (@powerblogservice)

    @dan & Jennifer

    No problems. I will add this in the next release which will be in the next week

    Plugin Author Russell Jamieson

    (@powerblogservice)

    The plugin runs fine of a WordPress multisite.

    In fact all testing now takes on a WordPress multsite installation with a separate site for each supported Genesis child theme

    Hi, I have a multisite install, and i’ve the beaver theme activated.
    When i try to activate the plugin on site or network-wide basis, i get an ‘acces denied’ warning.

    Do i also need to install and activate the genesis framework?
    I assumed this was already build in the beaver theme.

    • This reply was modified 9 years, 5 months ago by winoman.
Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Multisite Compatibility’ is closed to new replies.