Strange Bug - Can't make Blogs readable by members only

Reply

dotnetdiva Posted: Sat, May 10 2008 5:39 PM

rated by 0 users

 Ugh, this has always been such an inconsistent  problem for me.

My members want their blogs readable by other Registered Members, but not by the public. I've tried to get this to work for a month, but I'm so frustrated not to be able to get this to work. I had a bug earlier, thought it was fixed, but my members are not seeing everyone's blogs.

Here's my setup:

Under "Blog Groups", I go to Permissions tab, and try repeatedly to add the following roles: Everyone - no permissions. Registered Members - "Read" and "Comment". I click "Save". Only to go back and find my settings gone! I try over and over again. I either am missing something else, or there's a bug, or it's very user-unfriendly.

So I give that up and try to set individual blogs' permissions. Again, I can't figure out how to get only registered members to be able to view the blog. I can either get Everyone, including non-logged in members to view all blogs. Since these are mostly mother-family blogs, we need privacy when talking about our children, so that is not acceptable. Or - none of the blogs show up for anyone. It is working with a few blogs, but when I try over and over again to replicate these settings, the settings are NOT saved.

Reply

dotnetdiva replied on Sat, May 10 2008 5:56 PM

rated by 0 users

 I applied the update posted in the other thread about "Blogs not showing up", as I've also had issues with this, but to no avail.

I cannot seem to get my updates to save properly. Why isn't anything saving?!

I just paid for my license for Community Server 2008 too. And I've invested years into working with this software. My members are all asking me to go to Vbulletin or something, but I've only worked on this and asp.net. :(

Not sure if this helps, but there is a javascript error when I try to update unsuccessfully - "Can't execute code on a freed script". If I try a dozen times, sometimes I luck out with a setting being saved. I don't want to train my moderators if it is as frustrating to save simple settings as it has been for me.

Reply

Alex Crome replied on Sun, May 11 2008 3:44 AM

rated by 0 users

 Have you looked at the thread at http://dev.communityserver.com/forums/t/498790.aspx, in particular the 6th post that includes some files from Dave Penton.  (This may possibly be the thread you meant to refer to above).

As for the Javascript errors, try uploading again as you issues can sometimes occur if you (or your server) is in a time zone that is ahead of the timezone in which Telligent built the update - as the server will get confused as the binary has not yet been built.

I'm currently looking at your site (assuming it's the dslr one in your sig) and fail to see any Javascript errors on any blog pages

Reply

dotnetdiva replied on Sun, May 11 2008 1:03 PM

rated by 0 users

 Thank you for your response.

I downloaded the CS files again, and yes, I did add Dave Penton's updates, but I still am unable to save the "Make Public" setting.

The Javascript errors are not on the public blog pages, I see them in the Blog Administration pages when I am trying to update and save the settings. And I still see them after applying the latest updates.

Reply

Alex Crome replied on Sun, May 11 2008 2:17 PM

rated by 0 users

 Have you tried accessing the Administration pages in anotehr browser - just incase your browser has cached some bad javascript, and is refusing to load a working version.

If that doesn't work, I suggest that you modify the IsPublic bit directly in the database.  Open up the cs_sections table.  You can tell which applications are blogs as they'll have an ApplicationType of 1, and you can tell which blog you're modifying by either the ApplicationKey, or the SectionID.

If you want to make all blogs in a specific group public, you could use the folowing SQL script (replacing 4 with the relevant GroupID)

UPDATE    cs_Sections
SET              IsPublic = 1
WHERE     (ApplicationType = 1) AND (GroupID = 4)

N.b. before you do anything in your database, make a backup so you can revert in the case that something goes wrong.

CS will not respect these changes until you restart the Application, which you can do by touching web.config