Network setting overwritten by primary site setting?

Note: the message itself seems to be the bug. Activating or de-activating the cache from the network settings itself seems to be working as expected in spite of the message…

Hi,

I have reproduced some issue on network setting , could be related to your case

we will work out something for next release about this.

Best regards,

Great! I noticed the same message on other network settings too. Like when toggling the Object Cache option.

I cant activate de cache on a multisite. it says OFF
and when I activate on primary site it says
?? Esta ajuste es sobrescrito por los ajuste del sitio primario, actualmente establecido en OFF

but there is no link to settings on the multisite network plugin direcotry

what can i do?

Im sorry i have found where to touch the config. thanks

@ravanh Please try the latest commit and see if it is fixed or not. Thanks.

@hailite just downloaded from master branch on github (v3.3-rc10) but toggling the network wide cache option still shows the message. Or should I download from elsewhere?

Now the setting can show correctly. Please try v3.3-rc11.

Hi, just tested and the behavior has changed (I think) but not improved, I’m afraid. Now, when the primary site == network cache setting is ON and I switch it to OFF, the error message “This setting is overwritten by the primary site setting, currently set to ON” appears again, but this time the cache itself remains ON. Unlike in the current stable version where the cache would switch OFF in spite of the message. And when I reload the settings page, the Network Cache option is back ON again and the message has change to “This setting is overwritten by the primary site setting, currently set to OFF” (while the cache appears to be ON still)… Very weird and confusing.

To make sure this is not related to admin object caching, I tried to switch off Object Cache or even just the option Cache Wp-Admin but there too this happens. I cannot switch off object caching anymore…

Hi I was getting the same error when I tried to connect LSCWP with a Redis.
Maybe it’s something about the write permission for wp-config.php
When I added the permission “write” 640 to-> 660 the info error disappeared

define( 'WP_CACHE', true ) ; finally got succesfully added to wp-config.php and info error vanished

Do you think this could be the problem and the soulution?

Hi,

@lvnt this sounds to me , more like PHP suexec and/or file/dir permission issue ?

@ravanh please create a ticket here, we will investigate it further.

Best regards,