268 points
Community rank #184
kennibc
ExpertFriendly Neighbour
MemberLikes (0)
I just updated to 1.09 and the homepage is public even though it is set to private. It worked with 1.08 properly and was only after I updated that the frontpage was open to the public. I tried resetting privacy options with no luck for the main blog.
WP 3.3.1 multisite
BP 1.5.3.1
Any ideas? Also, with 1.08 it takes exactly 30 seconds for the login redirect to work. Very puzzling!
21529 pointsCommunity rank #0Supreme DeityWPMU DEV StaffLifetime member
Support Kangaroo
(joined March 2011)
Likes (0)
Greetings kennibc,
We are currently testing this out in our development environment, and I'm going to discuss it with the lead developer - to get a fix sorted for you asap.
Thanks again for bringing this up, and of course for being a WPMU Dev member, we'll get back to you asap
What's really troubling is that initial login on our server takes about 30 seconds for the redirect to work. Then the login page displays and the site works normally for a period of time. Then we get a 30 second wait for the site to load again with the login screen. Typically if I set the browser to clear all cache when it shuts down then it takes 30 seconds to login. If I do not clear all cache then the login page will load normally until something stored in the cache is removed and it has to cache it again.
Oh no... I noticed a strange file being attached via the .htaccess file and quite possibly the site might have been hacked. I will just wait on this and mark it solved for now...
21529 pointsCommunity rank #0Supreme DeityWPMU DEV StaffLifetime member
Support Kangaroo
(joined March 2011)
Likes (0)
Greetings Chris,
Just following up with my findings and thank you for your patience.
After some time playing with this it seems clear to me that this was not considered to protect the main site by design considering that in every WordPress installation that I am aware of the main site is designated as the working horse of the network and therefore should not be blocked from the search engines.
However, it can be done manually for this particular site by simply logging into the main site and going to Settings --> Privacy --> Site Visibility
Furthermore, if this is not suitable for your purposes either you can simply change which is the main site so you can then apply the privacy settings of the plugin to it.
To change which site is the main site log into the main site and go to --> Dashboard --> My Sites --> Primary Site and change from the drop down box which site is to be the main site and that is not contrary to the privacy setting available for the main site designation.
aecnu,
I do not want to change which blog is the Primary Site. When users login they are taken to my primary site. I want it to remain private as a walled garden. This functionality was originally built into the plugin prior to the latest release and if you set the main blog to be private you had to login to view stuff.
We are trying to create a private network in a closed environment. We aren't looking to have search engines find anything and we definitely don't want outsiders creating accounts (We use LDAP for login). The problem is that the main blog displays all the recent site activity using Buddypress. From the main site they would be able to see the users and blogs of the community. We do not want this.
We'd like the plugin to function as it did prior to the latest update which changed it.
I was having the same issue with the privacy plugin. I think it's an issue with Buddypress. To fix it, I set the root domain to fully open (so the front page is accessible by Google) and then added this snippet of code to the functions.php file of my child theme. It keeps the main page open, but redirects users who are not logged in from being able to access the Activity stream, directory, etc. You can see it at work at http://commons.hwdsb.on.ca
Responses (11)
Support Kangaroo (joined March 2011) Likes (0)
Greetings kennibc,
We are currently testing this out in our development environment, and I'm going to discuss it with the lead developer - to get a fix sorted for you asap.
Thanks again for bringing this up, and of course for being a WPMU Dev member, we'll get back to you asap
Cheers, Joe :-)
Member (joined October 2008) Likes (0)
Thanks Joe.
I downgraded to version 1.08.
What's really troubling is that initial login on our server takes about 30 seconds for the redirect to work. Then the login page displays and the site works normally for a period of time. Then we get a 30 second wait for the site to load again with the login screen. Typically if I set the browser to clear all cache when it shuts down then it takes 30 seconds to login. If I do not clear all cache then the login page will load normally until something stored in the cache is removed and it has to cache it again.
http://engage.dearbornschools.org
Any ideas?
Member (joined October 2008) Likes (0)
Oh no... I noticed a strange file being attached via the .htaccess file and quite possibly the site might have been hacked. I will just wait on this and mark it solved for now...
Thanks,
Chris
Member (joined October 2008) Likes (0)
Fixed all my previous issues and I can say that verson 1.09 does not protect the main blog in a multi-blog setup even if it is set to private.
So the original issue is still valid.
Version 1.09 does not block the main blog.
Thank you for looking into this. Let me know if there are any details I can provide.
-Chris
Support Kangaroo (joined March 2011) Likes (0)
Greetings Chris,
Just following up with my findings and thank you for your patience.
After some time playing with this it seems clear to me that this was not considered to protect the main site by design considering that in every WordPress installation that I am aware of the main site is designated as the working horse of the network and therefore should not be blocked from the search engines.
However, it can be done manually for this particular site by simply logging into the main site and going to Settings --> Privacy --> Site Visibility
Furthermore, if this is not suitable for your purposes either you can simply change which is the main site so you can then apply the privacy settings of the plugin to it.
To change which site is the main site log into the main site and go to --> Dashboard --> My Sites --> Primary Site and change from the drop down box which site is to be the main site and that is not contrary to the privacy setting available for the main site designation.
Thank you for being a WPMU Dev member.
Cheers, Joe :-)
Member (joined October 2008) Likes (0)
aecnu,
I do not want to change which blog is the Primary Site. When users login they are taken to my primary site. I want it to remain private as a walled garden. This functionality was originally built into the plugin prior to the latest release and if you set the main blog to be private you had to login to view stuff.
We are trying to create a private network in a closed environment. We aren't looking to have search engines find anything and we definitely don't want outsiders creating accounts (We use LDAP for login). The problem is that the main blog displays all the recent site activity using Buddypress. From the main site they would be able to see the users and blogs of the community. We do not want this.
We'd like the plugin to function as it did prior to the latest update which changed it.
Member (joined June 2011) Likes (0)
Hey kennibc,
I was having the same issue with the privacy plugin. I think it's an issue with Buddypress. To fix it, I set the root domain to fully open (so the front page is accessible by Google) and then added this snippet of code to the functions.php file of my child theme. It keeps the main page open, but redirects users who are not logged in from being able to access the Activity stream, directory, etc. You can see it at work at http://commons.hwdsb.on.ca
Developer (joined April 2011) Likes (0)
Hi guys,
I will check it
Developer (joined April 2011) Likes (0)
Hi kennibc,
How I already wrote in other topic:
Really I can't install "WPMU LDAP Login" on my hosting
But I think I found solution - if the 1.0.8 works for you.
I need test it with WprdPress iOS before released.
But I haven't iPhone :(
I will try to take it from my friend tomorrow.
I will write here.
Developer (joined April 2011) Likes (0)
Hi guys,
I think I fixed problem.
Please update the plugin.
Member (joined October 2008) Likes (0)
Thank YOU! Initial tests indicate it is working as expected.
-Chris
Become a member