These are chat archives for collectiveaccess/support

16th
May 2017
TBthegr81
@TBthegr81
May 16 2017 11:08
What is the practical difference between a "Full Access" user and a "Public Access Only" user?
Isn't that something that is already covered by what Groups and Roles the user-account is in?
Anita Ruijmen
@aruijmen
May 16 2017 11:56
Greetings all. I have a question about object/object relationships (with interstitial information) in CA 1.6.2 (and Pawtucket2). Normally self-relationships appear in both objects. CA knows when to put the reverse direction of the relationship_type in the UI. My questions are:
  1. Is it possible to suppress the relations in the 'reverse direction'. Meaning: when my object is the object_left_id in ca_objects_x_objects, I want to see the relation. But when the same object_id is the object_right_id, I want to suppress the relations?
  2. Is there a way to access the correct sense of the relationship in the display format of the relationship in a display created in My displays (used to build the summary screen of an object)?
  3. What are the possibilities to implement this also in Pawtucket?
If you need more information, .... Thanks in advance
CollectiveAccess
@collectiveaccess
May 16 2017 12:24
@TBthegr81 Full access can log into both front (Providence) and back-ends (Pawtucket). Public access users logins only work on the front-end (Pawtucket)
@aruijmen Regarding #1 you can't do it currently
Regarding #2 the display template should automatically figure out what the correct sense is. If it's not then file a bug report.
Regarding #3 Pawtucket is almost entirely the same code as Providence so the same issues apply there. There are no plans to implement what you're asking for soon.
Anita Ruijmen
@aruijmen
May 16 2017 12:39
@collectiveaccess Regarding #2: so using ^relationship_typename in the display template should give the correct sense? Unfortunately this is not the case in CA nor in Pawtucket. Or is there another way to access this information?
CollectiveAccess
@collectiveaccess
May 16 2017 13:45
@paintedsky No only PHP 5.6 or better is supported for the latest code. You can grab older version off of GitHub
@aruijmen Try it in 1.7 and if it doesn't work there file a bug report
TBthegr81
@TBthegr81
May 16 2017 13:53
@collectiveaccess How does that work with the API? Say I make a custom frontend using the API?
The API is on the backend but can be used for frontend stuffs, so I guess it should work for public users?
CollectiveAccess
@collectiveaccess
May 16 2017 14:58
@TBthegr81 Logins on the back-end, even service logins, require a login with the "full user" class
Any login on the front-end only requires the "public user" class
TBthegr81
@TBthegr81
May 16 2017 15:13
Is there any way to enable public-users to use the service api? Seems wrong to make all users full-users or to run every API call via a single full-user when there is a system in place allready