Privacy Levels Settings.

I tried setting up the default privacy levels in the database but Public level kept being set even though the Public Group was unchecked in Admin.  Has anyone else had this issue?  Since the site is private, there is no need for the Public Group.  I set the default values in sys_albums and in sys_privacy_actions to 4.  Yet, when a member joined their default albums were being set to Public, 3.  I tried looking in the code that creates the albums but finally just went into BxDolPrivacy.php and set the All group to value 4.  However, I should not have had to done that; not having Public Group checked in the admin should have been all that was needed to not have albums being set to Public.

define('BX_DOL_PG_DEFAULT', '1');
define('BX_DOL_PG_NOBODY', '2');
define('BX_DOL_PG_ALL', '4');
define('BX_DOL_PG_MEMBERS', '4');
define('BX_DOL_PG_FRIENDS', '5');
define('BX_DOL_PG_FAVES', '6');
define('BX_DOL_PG_CONTACTS', '7');
define('BX_DOL_PG_HIDDEN', '8');

I think the Dolphin developers should look at this.  The issue came to the front on a site being developed in which the public group is not going to be used.  Photos were not showing up except for the owner.  I had set the privacy default in the database as was outlined in a forum topic similar to our situation.  In searching I came across another forum topic in which photos were not showing up.  Deano answered that the person needed to set the public group and that fixed the issue for the person posting the topic.  However, that is not a solution when you don't want the public group enabled; no content will be public.  Yet, albums are set to public even without the public group enabled.  My "hack" is not the solution here; I will use it for now because it is a simple fix to the issue.  When public group is not enabled, albums should not be set to privacy level 3.

Create an item in a module and set it to be viewed by "me only". then look in the database and see what the entered value is. Then set all those view_to fields for the modules you are going to use to default to that value, then remove the view_to section from your modules 'Add' forms.

But that is not a Boonex solution to this issue.

it is not a Boonex solution, but a solution to accomplish what you need. Keep in mind - dolphin is just a base setup. A lot of things will have to be customized. Like street racers. They do not expect to get a 9 second car from off the dealership lot. So, they buy something that they can customize exactly to their likings.

There are too many wnats and desires when dealing with websites and it is hard for Dolphin to accomplish what everyone desires, so they offer a base that you can customize. I choose to just customize rather than complaining.

My fix that I outlined is a solution that can be implemented when we don't want to enable public privacy group.  Go back and look at the post, That red 4 is normally a 3 for public group.  What that does is that any time Dolphin assigns public to an album, it will store 4 in the database.  When Dolphin goes to read the value for the privacy it will find 4 and thus show the content to anyone that is a member of the site.  What I did was to reset public to members and thus fixes the problem with Dolphin assigning public value of 3 in the database even though public privacy group is not enabled.  I need to post this in the bug forum.

I was not complaining.  I was illustrating a bug in Dolphin code.  As I stated, I need to post this in the bug section of the forum as this bug has caused issues with others as well.

It would not be considered a bug. Technically, the way the system is setup is that all things are set to public. And since it is working properly, it is not a bug. Since you want it to function different than what is was setup for, that would be considered a modification. Just because YOU - or anyone - may want a different functionality does not mean the existing functionality is wrong. There are those who think the default settings are perfect for their needs.

Yes it is.  It prevented photos from being displayed on the site.  Public group was NOT enabled in the admin.  However, it sets albums to public anyway and the end result is that one can not see the photos that members are posting.  That is a bug.  Plus, I am not the only one to experience this bug.

Here is SQL query to change privacy which is selected by default, I suppose you need to run it if you disabled Public group:

http://www.boonex.com/forums/topic/View-Settings-in-Dolphin-7-1-4.htm#234603

No Alex, you missed the problem, probably due to the noise from the other poster.  I set it up in the database to assign group 4 as the default for new albums.  I disabled Public Group in the Admin.  However, when a new album is created, it is still assigning group 3 in the database and the photos in the album are not visible.  I outlined this very carefully; even with Public Group disabled, even with the database set to assign group 4 as the default, Group 3 is assigned in the database, the field in the database will be SET to 3 by the album creation code.  Do you now see the bug?

As I understand you, this should be exactly what you are looking for, and no need to make any changes in the code, like you did here - http://www.boonex.com/forums/topic/Privacy-Levels-Settings-.htm#234711

The way I understand this, there is a bug here.  When I get time, I will recreate it on Boonex.com, try to include some screenshots and maybe you will understand better.  Of course I can not take screenshots of the privacy code sticking a 3 in the database when public group is disabled.  Gee Whiz, can't boonex do a little bit of this bug checking on their own?

It maybe that I didn't understand you properly, so some clarification maybe make things clear.

Also did you try to run the specified here query to see if it helps (without any modifications in the code) ?