Support » Plugin: All In One WP Security & Firewall » there is no support for multi-site

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, thank you for your 3 star review.

    there is no support for multi-site.

    Yes, it does support multisite. Please read the following documentation.

    If you need more support, please open up a support ticket and we will be happy to assist you.

    Kind regards

    • This reply was modified 1 year, 8 months ago by mbrsolution.

    The documentation does not solve the problem of access to the htaccess file. It is available for changes from any sub site with a plugin AIO.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi,

    It is available for changes from any sub site with a plugin AIO.

    Are you asking if you can access the .htaccess file from a subsite? If not, what do you mean?

    The documentation states the following.

    The following list of features are not included in the network single site because they write to the .htaccess file. The .htaccess file is managed only by the network admin site.

    The above tells you that the plugin only writes to the .htaccess file in the main network admin site. Another words the Firewall rules are only managed in the main site and not the subsite.

    However the plugin does support Multi-site set up which is your main query, correct?

    Let me know if you need more help.

    Kind regards

    “the plugin only writes to the .htaccess file in the main network admin site” – is not so.
    Clicking [save] on any options of the AIO on subsite – htaccess is changing.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi, can you give me an example of what you mean? For example: what do you save in a sub site using AIOWSP that writes to the sub-site .htaccess file?

    Thank you

    1. I activate the AIO plug-in on a subsite
    2. go to the menu “Brute Force” (on a subsite)
    3. go to the menu “Rename Login Page” (on a subsite)
    4. Change admin name.
    5. Click on Save Settings button
    As a result, the htaccess is changing

    and…
    #AIOWPS_PREVENT_IMAGE_HOTLINKS does not work correctly on the multisite, images is break on the subsite.

    The security plug-in must have a separate option to support the multisite.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Hi,

    1. I activate the AIO plug-in on a subsite
    2. go to the menu “Brute Force” (on a subsite)
    3. go to the menu “Rename Login Page” (on a subsite)
    4. Change admin name.
    5. Click on Save Settings button
    As a result, the htaccess is changing

    That is correct as per the documentation I shared above.

    #AIOWPS_PREVENT_IMAGE_HOTLINKS does not work correctly on the multisite, images is break on the subsite.

    Can you try the following steps. Deactivate all your other plugins and carry out a test. Let me know if it works. If it doesn’t can you test one of WordPress default themes like Twenty Seventeen?

    The security plug-in must have a separate option to support the multisite.

    What do you suggest?

    Regards

    • This reply was modified 1 year, 8 months ago by mbrsolution.

    I’m sorry, I did not say …

    …………..
    5. Click on Save Settings button
    As a result, the htaccess is changing – A lot of variables of the main domain are deleted!
    In the htaccess file there are only the settings available for the subsite.

    Yes, I’m deactivated all other plugins and use Twenty Seventeen theme. Images on subsite does not displayed.

    Unfortunately I had to change my plans for working with the multisite. I wrote you possible problems with the plugin. I saw that it is not adapted for a multi-site.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Thank you for your information and review.

    Kind regards

    Plugin Author wpsolutions

    (@wpsolutions)

    Hi @brilliantium
    Thanks for the feedback and yes I see now what you mean regarding the .htaccess file and rename login feature.
    The plugin currently calls the “write_to_htaccess” function whenever one activates the rename login page feature. This is done in case it needs to clear any code from the cookie based brute feature because only one of those features can be active at a time.
    If you did not have the cookie based feature active (as in your case) it still calls that function even though it does not actually change anything in the .htaccess file. (it writes the same rules back into it)
    I have now improved the logic in the code so in the next release you will not see any needless writing to .htaccess file for this case.

    3 stars -> 4 stars
    4 stars because…
    The security plug-in must have a separate settings to support the multisite. And this settings should have more advanced features.

    Plugin Contributor mbrsolution

    (@mbrsolution)

    Thank you for adding one more star 🙂

    Kind regards

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘there is no support for multi-site’ is closed to new replies.