Privacy Settings - Remove custom privacy group - id still in table

Some simple steps to reproduce.....

1) Create a custom privacy group

2) Set your profile blocks (yellow key) to this newly created group.

3) Delete the group

4) Check the yellow key -> None group is selected.

5) Check table sys_page_compose_privacy -> The "field allow_view_block_to" still points to this already deleted group ID. This should change back to the standard group.

Any tips where to check? I think this could be easy to fix or?

I believe that this problem is not related to "profiles blocks" privacy only, but to any privacy field.

The difficult thing here is that it is not tracked where exactly custom group id is used. 

So if we deleted it - we can't update all places where it is used.

Possible solution here is to warn user before he/she deletes the group, and use default group(or maybe "me only" group) if group is not found.

I understand what you want to say, and i already warn my users. But for them its not a very professional way for such a system because even they might not know anymore where they used the group months ago.

Isnt it possible to just query all the records of the tables which hold references to these group_id's and update them with the standard-group id if it matches the to be deleted id? So tracking isn't needed. The tables were permissions id's could be stored should be known.

 We can have a list of these fields for boonex modules only, but there are many 3rd-party modules which are using privacy too, and we can't even guess in what field/table it could be stored.

You are right, you cannot take care of third parties, that i know. I only speak about dolphins own code.

If a third party is doing their own stuff i would contact them and ask them to check the ID's being used against sys_page_compose_privacy.

I would like to have a list of tables where dolphin stores references to these IDs so i could add a function to rename them to some existing ones the user can choose or use a default key.

Hello dately!

"Privacy theme" exists in next tables in default Dolphin 7.0.9 package:

Profiles
sys_albums
sys_page_compose_privacy
bx_groups_main
bx_events_main
bx_store_products
bx_poll_data
bx_sites_main
bx_ads_main
bx_blogs_posts
bx_simple_messenger_privacy
bx_files_main
bx_map_profiles
bx_fdb_entries

Regards

Thanks for the info, that helps me a lot

One last question: Is there a way to add some information for the users to this privacy page? I already checked if there is a way in page builder, so i can add a html or php block but i couldn't find.

I also tried to find an easy way in the code of member_privacy.php but the only thing happening there looks to be some block generation passing to the template engine which yet have never dealed with. If i want to add another block above all the others on member privacy page, do i have to add an own function in BxBasePrivacyView.php and call it like the rest of the blocks in member_privacy.php? I speak about these lines here where i think i can add my block

// --------------- page components
$iIndex = 82;
$_page['css_name'] = 'privacy_settings.css';
$_page['header'] = _t( "_ps_pcpt_privacy_settings" );
$_page['header_text'] = "";
$_page['name_index'] = $iIndex;
$_page_cont[$iIndex]['page_code_add_members'] = $oPrivacyView->getBlockCode_AddMembers();
$_page_cont[$iIndex]['page_code_delete_members'] = $oPrivacyView->getBlockCode_DeleteMembers();
$_page_cont[$iIndex]['page_code_my_groups'] = $oPrivacyView->getBlockCode_MyGroups();
$_page_cont[$iIndex]['page_code_create_group'] = $oPrivacyView->getBlockCode_CreateGroup();
$_page_cont[$iIndex]['page_code_default_group'] = $oPrivacyView->getBlockCode_DefaultGroup();
$_page_cont[$iIndex]['page_code_default_values'] = $oPrivacyView->getBlockCode_DefaultValues();
// --------------- [END] page components

Maybe there is an easier solution you can tell me.

Thanks in advance