How does admintools function with wordpress multisite networks?
Mike Biolsi
#33157 wordpress multisite
Posted in ‘Pre-sales and Account Questions’
This is a public ticket
Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Latest post by on Sunday, 05 July 2020 17:17 CDT
Thursday, 04 June 2020 16:33 CDT
mbiolsi
Friday, 05 June 2020 00:07 CDT
nicholas
Akeeba Staff
Manager
WordPress multisites is really not multiple sites. It's just smoke and mirrors. You have one, big site with some duplicated tables. The whole lot pretends to be multiple sites by using some trickery.
From the perspective of Admin Tools this is still one big site. The protection is at the fundamental WordPress level, before WordPress' multisite code kicks in. This means that the configuration is set globally, through the Network Administrator. All blocks also apply globally. Each individual network blog has no control over Admin Tools' settings. It should go without saying that the .htaccess Maker settings are of course applied globally since the entire blog network has a single .htaccess file anyway.
From the perspective of Admin Tools this is still one big site. The protection is at the fundamental WordPress level, before WordPress' multisite code kicks in. This means that the configuration is set globally, through the Network Administrator. All blocks also apply globally. Each individual network blog has no control over Admin Tools' settings. It should go without saying that the .htaccess Maker settings are of course applied globally since the entire blog network has a single .htaccess file anyway.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Sunday, 05 July 2020 17:17 CDT
System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.