Viewing 7 replies - 1 through 7 (of 7 total)
  • Yes it works on a Multi-site install. However, some of the features will only work on the main install (not the sub-sites).

    Thread Starter londonnet

    (@londonnet)

    Thanks for the reply
    Do you install the plugin and network activate or activate it on the main site only or separately activate it per site?
    Where you administer it from?
    Which features do not work on sub sites?

    Regards

    [ No bumping please. ]

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi @londonnet are you still having issues with Multi-site installations?

    Thread Starter londonnet

    (@londonnet)

    I don’t think so. I think I found the answer which is to install the plugin and activate it on your main site only and this will protect all sites but I have found that some features do not work like changing the sub sites login page name.

    It would be good to see a bit more support for multisite. It would be easy to detect the install is multisite and to put the configuration on the multisite network page and to support all features down to the sub sites.

    There doesn’t seam to be much documentation about multisite support.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    This issue is now resolved. I am marking it as resolved.

    Thank you

    Thread Starter londonnet

    (@londonnet)

    It would be great to get an official answer rather than an uneducated guess before you close.

    Is there an official guide on how to install on multisite?

    Thanks

    Plugin Contributor wpsolutions

    (@wpsolutions)

    There is no official guide for multi-site installation.
    However regarding configuration – basically anything which uses .htaccess directives such as the firewall rules, blacklist, and cookie based brute force can only be configured on the main site because a multisite installation uses a single .htaccess file. (These features will be hidden from subsites anyway)

    The other general features can be configured individually on each subsite – eg, each subsite will probably want to use the rename login page brute force feature, or add a captcha etc

    Therefore in summary:
    if you wish to allow each subsite to configure the applicable security features such as renaming their own login page, adding captcha, changing DB prefix etc, then DO NOT network activate the aiowps plugin because otherwise the subsite admins will not be able to see the aiowps plugin menu. Simply activate the plugin on the individual subsites.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘multisite’ is closed to new replies.