Can not set Public, Private or Unlisted without viewing other user's data

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 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • 12/04/2014 at 3:36 pm #311768
    Rick Wielopolski
    Participant

    Form does not allow overall entry and individual field selection of Public, Private or Unlisted without allowing the user to also view all of these categories. Users should be able to select a default for the entry (e.g. Private) and also select a different setting for a field (e.g. Unlisted phone number) without the rights to see all of the other users private and unlisted information.

    This is the logic currently in the Connections Roles setting. The selection will not be displayed unless the user has the rights to view that data. This is understandably by design to prevent locking yourself out of editing access but could be corrected in Form.

    Forced defaults for Public, Private and Unlisted settings for the entire entry and each field should be set in Admin but are not available.

    12/05/2014 at 9:37 am #311803
    Steven Zahm
    Keymaster

    @ Rick

    Yes, this is correct. The original design, there was no concept of a user/entry permissions. Grafting this on is complex, as such, I’m taking small steps rather get myself in a corner that I can not get out of. Each release I tackle this in one form or another. Form 2.x was a big step in this direction as the code for this type of permissions is handled by the ore Connections plugin. With that I can make my changes and Form benefit automagically.

    Right now, the “bandaid” solution is to not allow users to select visibility options that will lock them out of their data. This will be addressed in future revisions.

    As for the very last comment … I’ll add it to my feature request list, not sure I’ll add it though … may as a free extension so it’ll be available to those that do want that ability. Adding it as an extension actually seems like a very good idea, it’ll make sure that I design it in a very flexible way.

    12/09/2014 at 2:01 pm #312230
    Rick Wielopolski
    Participant

    Thanks…I understand this takes time. Adding the ability to force the entry, as well as the data fields, would help as a workaround. (BTW…I used your filter to force private for the entry, but the fields do not get forced).

    I have removed it and will wait for your next release.

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

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