Login Required should default entry/fields to Private

Support has been upgraded!



The Support Forum is closed. Not to worry!  Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.

Premium Support

Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?

Please open a Support Ticket in your user account.

Click here to open a support ticket.

Free Support

Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.

Please open a new support topic in the WordPress support forums for Connections.

Click here to open a support topic.

This topic is: resolved

Tagged: , ,

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • 12/04/2014 at 4:05 pm #311770
    Rick Wielopolski
    Participant

    After setting Login Required to see the directory, Public or Private settings are basically redundant. Assuming all data is now set to Private is incorrect since Public will still be the default for each entry and field.

    Since a user cannot select a Public/Private/Unlisted setting (in Form) unless they have these viewing rights for all users, you are forced to use Public as the entry.

    Otherwise, forcing Private (via Admin or with a script) will restrict the entry (redundantly) but each field (in Form) still defaults to Public. This means valid users will not be able to view any field unintentionally left in Public by entering data in Form.

    Fortunately, a general public user will not see the entry that is set to Public because of the Login requirement. However, all data should have been defaulted to Private by selecting Login Required.

    This evolves similarly to another issue with being able to set Unlisted (in Form) while Login Required. A user should be able to select fields (in Form) to set as Unlisted without rights to view all unlisted entries.

    12/05/2014 at 10:21 am #311805
    Steven Zahm
    Keymaster

    @ Rick

    I had to read this a couple times … this is not a bug and defaulting to private when login is required is not going to happen; here’s why …

    I easily see how this can seem redundant … but there many people using this feature. By selecting the login required, you redefine who the public is. Public becomes those that are assigned the “Subscriber” role and private is “Author” and “Editor” by default.

    12/09/2014 at 2:33 pm #312233
    Rick Wielopolski
    Participant

    Sorry for the confusing explanation. Your response makes sense, however, with Login Required (which we mandate), the problem is that a Subscriber can not set individual fields in their directory entry to Unlisted (e.g. phone #) because the selection will not appear in FORM. This of course is because they are relegated to a Public setting.

    If I elevate their role or setting, then they would be able to see other people’s unlisted information which is unacceptable.

    The problem is that the data fields in FORM can not be set individually and do not inherit the directory entry setting (unless it is Public…the default).

    12/10/2014 at 10:23 am #312396
    Steven Zahm
    Keymaster

    @ Rick

    Right, there is that limitation, for now. It is on my todo list to allow users to set private/unlisted without requiring that view permission.

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)

You cannot reply to this support topic. Please open your own support topic.