Project

General

Profile

Roadmap

2.0.0

closed

100%

23 issues   (23 closed — 0 open)

Related issues
Bug #2143: Privacy does not seem to make a difference on user status fields Actions
Bug #2936: tab privacy still allows userlist searching Actions
Bug #2955: profile privacy does not hide on userlist Actions
Bug #3079: Bulk import Actions
Bug #3325: CB Privacy no frontend edit also functions in backend with CB 1.8 Actions
Bug #3399: Connect types are not passed through translation Actions
Bug #3528: Moderator only edit fields don't show for a moderator when editing himself Actions
Bug #3566: Field privacy settings no longer visible Actions
Bug #3932: Implement API for display and storage of privacy Actions
Bug #3947: Fix delete and disable field queries to use API Actions
Feature proposal #1709: set private based on subscription Actions
Feature proposal #1721: Add owner view only mode Actions
Feature proposal #2168: parameter to set registration display Actions
Feature proposal #2861: Select multiple connection types Actions
Feature proposal #3916: Implement Delete Me and Disable Me fields Actions
Feature proposal #3917: Implement Profile Privacy field Actions
Feature proposal #3934: Implement privacy control for Email Form Actions
Feature proposal #3936: Implement backend tools Actions
Feature proposal #3938: Implement install script for auto migration Actions
Feature proposal #3942: Redo delete and disable me fields to be links and not checkboxes Actions
Feature proposal #3943: Delete me and disable me should have optional notification Actions
Feature proposal #3944: Implement disable me and delete me reason Actions
Feature proposal #3945: Implement before and after triggers for disable and delete Actions

2.1.1

closed

No issues for this version

4.0.0

closed

100%

13 issues   (13 closed — 0 open)

Related issues
Bug #4184: Privacy records strictly looking for NULL values Actions
Bug #4193: Moderator forced tab privacy settings not taking affect Actions
Bug #4343: Show empty fields parameter causes userlist privacy to be ignored Actions
Bug #4545: Profile privacy not affecting userlists Actions
Feature proposal #4141: Upgrade default template to Bootstrap 3 style and markup Actions
Feature proposal #4239: Implement parameter to disable registration privacy display Actions
Feature proposal #4333: Remove cbprivacyData usage Actions
Feature proposal #4334: Remove custom URL functions Actions
Feature proposal #4335: Remove custom params parsing Actions
Feature proposal #4371: Remove old privacy plugin migration Actions
Feature proposal #4435: Implement display mode to force a privacy setting Actions
Feature proposal #4603: Complete UI overhaul Actions
Task #4192: Replace Select2 usage with built in Select2 Actions

5.0.0

closed

100%

24 issues   (24 closed — 0 open)

Related issues
Bug #5960: isAuthorized is not unique enough when using uniqid Actions
Bug #6141: Tab edit display parameter failing on failed edit save Actions
Bug #6142: Moderators are exempt from edit display parameters Actions
Bug #6319: fieldsFetch acting on wrong user object Actions
Bug #6414: Read Only fields can not save privacy Actions
Feature proposal #4872: allow users to re-enable themselves Actions
Feature proposal #4991: Create plugin API library files for privacy handling Actions
Feature proposal #5063: Implement moderators only display Actions
Feature proposal #5064: Add moderator only privacy option Actions
Feature proposal #5165: implement new $.cbconfirm to replace browser confirm dialog Actions
Feature proposal #5183: Implement parameter to override field display Actions
Feature proposal #5266: Implement more fine control of profile privacy Actions
Feature proposal #6144: Implement usergroup edit display value Actions
Feature proposal #6265: Improve parameter descriptions Actions
Feature proposal #6359: Rewrite how template files are included Actions
Feature proposal #6629: Replace type, subtype, and item with asset Actions
Feature proposal #6630: Restructure privacy rule storage Actions
Feature proposal #6634: Implement per usage privacy overrides Actions
Feature proposal #6637: Implement ajax privacy controls Actions
Feature proposal #6638: Implement button layout Actions
Feature proposal #6639: Implement parameter to specify custom blocked message Actions
Feature proposal #6640: Implement icon layout Actions
Feature proposal #6641: Move jQuery to custom jQuery plugin Actions
Task #6143: Remove no edit display at all for fields Actions

5.1.0

closed

100%

7 issues   (7 closed — 0 open)

Related issues
Bug #6671: Deleting or Disabling a user as moderator does not work Actions
Bug #6675: Privacy controls not displaying on registration Actions
Bug #6676: Privacy value doesn't persist with POST if save fails Actions
Bug #7124: Icon override behavior unreliable Actions
Feature proposal #6814: Implement privacy field type Actions
Feature proposal #7108: Implement CB 2.2 Bootstrap 4 fixes Actions
Feature proposal #7150: Implement raw privacy field output Actions

6.0.0

closed

100%

18 issues   (18 closed — 0 open)

Related issues
Bug #6926: Moderator account disable/delete causes logout Actions
Bug #7204: Moderator only display not working Actions
Bug #7205: HTML not working in display overrides Actions
Bug #7218: PHP 7.2: session object cache pointer causes count warning Actions
Feature proposal #4969: Implement block user Actions
Feature proposal #6927: Implement parameter to disable account re-enable Actions
Feature proposal #6979: Email form should respeect email field privacy Actions
Feature proposal #7094: Implement download my data field Actions
Feature proposal #7095: Improve selected privacy rules visibility Actions
Feature proposal #7100: Implement hidden layout usage for privacy controls Actions
Feature proposal #7102: Implement simple profile privacy mode Actions
Feature proposal #7163: Implement menu endpoint to disable/delete account pages Actions
Feature proposal #7169: Implement parameter to allow moderators to delete or disable themselves Actions
Feature proposal #7375: Implement delete me and disable me email confirmation Actions
Feature proposal #7416: Improved getPrivacy API with prefetching Actions
Feature proposal #7417: PM form should respect privacy Actions
Feature proposal #7422: Implement privacy fieldtype Actions
Feature proposal #7441: Request connection endpoints not checking profile privacy Actions

6.1.0

closed

100%

16 issues   (16 closed — 0 open)

Related issues
Bug #7498: Block user menu item when using menu list does not display properly Actions
Bug #7570: Userlist removal of users may not be working in some cases Actions
Bug #7573: If no privacy rules are available the privacy selection should not be available Actions
Bug #7584: Disable/Delete Account endpoints fail while logged out if their field is not public accessible Actions
Bug #7616: User blocking too aggressive Actions
Bug #7660: Hidden _noPrivacy not fully working Actions
Bug #7708: Connections privacy check only checking the first few hundred connections Actions
Feature proposal #7459: Remove email from block form Actions
Feature proposal #7507: Implement profile privacy redirect URL parameter Actions
Feature proposal #7603: Implement block user menu item for private messages Actions
Feature proposal #7605: Prevent messaging and emailing of users you have blocked Actions
Feature proposal #7636: Improve simple privacy to work with ajax edit views Actions
Feature proposal #7684: Implement ACL for privacy rule selection Actions
Feature proposal #7694: Implement tab display overrides Actions
Feature proposal #7704: Improve simple privacy with grouping Actions
Feature proposal #7707: Implement support for overriding tab and field privacy asset Actions

7.0.0

closed

100%

18 issues   (18 closed — 0 open)

Related issues
Bug #7764: Hidden privacy controls are attempting to output in simple privacy Actions
Bug #7765: Hidden privacy controls causing database storage Actions
Bug #7767: Saving a privacy control via ajax with simple privacy enabled wipes out privacy rules Actions
Bug #7962: PMS block links in modal window return to wrong page Actions
Bug #8020: If no view access levels or usergroups are available optgroup still displays Actions
Bug #8184: Default display overrides not being considered when removing field output Actions
Bug #8235: Simple privacy tab description does not function Actions
Bug #8330: Dropdown missing zindex Actions
Feature proposal #7544: Implement specific users privacy rule Actions
Feature proposal #7762: Implement parameter to control privacy controls location Actions
Feature proposal #7766: Forced privacy controls with a custom asset should check the asset for a rule Actions
Feature proposal #7768: Fields without profile edit views can't have privacy controls Actions
Feature proposal #8021: Implement parameter to allow all view access levels to be output Actions
Feature proposal #8170: Improve blocking to output generic avatar, canvas, and name Actions
Feature proposal #8312: Implement compatibility with select2 update in core Actions
Feature proposal #8403: Implement name API for specifying privacy controls input name Actions
Feature proposal #8404: Improve params parsing reliability Actions
Feature proposal #8405: Implement support for field group field triggers Actions

8.0.0

open

33%

6 issues   (0 closed — 6 open)

Related issues
Feature proposal #4945: implement query based filtering of users by privacy rule Actions
Feature proposal #7440: Implement trigger handling for plugin privacy controls Actions
Feature proposal #8230: Implement support for outputting ajax privacy controls in profile view Actions
Feature proposal #8475: Implement support for field groups field fullAccess variable Actions
Feature proposal #8572: Implement support for forced profile privacy Actions
Feature proposal #8640: Remove usage of zero datetime Actions