After updating to 4.7.20, when the Event Info Page is accessed, it generates the following error, "API permission check failed for Event/get call; insufficient permission: require access CiviCRM and access CiviEvent and view event info". If I roll the system back to 4.7.18 it works. Any suggestions on a fix or work-around are much appreciated.
6
-
Hmm - if you had said this only for 4.7.19 i would have said github.com/civicrm/civicrm-core/pull/10325 was the fix. but that is in 4.7.20 afaik - can you check the 4.7.20 code you had and confirm if that fix was in there. that said, may be entirely unrelated. just been applying this to a number of 4.7.19 sites hence on top of my mind – petednz - fuzion♦ Jun 14 '17 at 22:26
-
this was related jira - issues.civicrm.org/jira/browse/CRM-20549 – petednz - fuzion♦ Jun 14 '17 at 22:27
-
Thank you for the suggestion, but it didn't resolve the issue. I compared the file with the one on githubusercontent.com, but couldn't see any changes, so I replaced my event.php with the one there. No change, still getting the "API permission check failed for Event/get call; insufficient permission: require access CiviCRM and access CiviEvent and view event info" error message. – CSDweb Jun 16 '17 at 1:12
-
After updating to 4.7.22, I'm still receiving the following error: "API permission check failed for Event/get call; insufficient permission: require access CiviCRM and access CiviEvent and view event info" when I try to access Event Info. Any suggestion for a fix/work-around would be appreciated. Currently, the only option I have is to roll back to civiCRM 4.7.18. – CSDweb Jul 14 '17 at 23:02
-
It may not be a valid work-a-around, but I've discovered a way to run 4.7.22 without getting the API permission error when trying to view Event Info from the front-end. I changed the ACL, 'CiviCRM: access CiviCRM' permissions for 'Public' users from the default, 'Inherited' to 'Allowed'. – CSDweb Jul 15 '17 at 1:35
|
Show 1 more comments
I ran in to this on an inherited site. It fixed itself once I removed the permission for "access CiviEvent" (which i assume had been erroneously given by previous developers)
Once removed the other permissions worked fine.
Maybe this counts as a bug. Will raise up a level.
answered Jun 13 '18 at 0:53
-
This worked for me too on Drupal. Specifically, in the CMS permission "CiviEvent: Access CiviEvent" for anonymous users. – Harold Shinsato Nov 24 '18 at 20:14
-
Thx Harold. StackExchange works best if you Up vote tickets that are useful to you. – petednz - fuzion♦ Nov 25 '18 at 18:35
I've confirmed this bug and reported at https://lab.civicrm.org/dev/core/issues/1517
PR https://github.com/civicrm/civicrm-core/pull/16266 should fix the problem.
