-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Authorization failed" on new build at install civivolunteer #486
Comments
I'm getting the same error. |
does this mean that VOL is d8 incompatible? |
Sorry, this is on a d7 build. |
I wondered about the api4 stuff but just figured as it's being pushed now that maybe v3 defers/uses v4 in doing its thing now. (but this was just a guess, I'm v. unfamiliar with apiv4 and also the way buildkit works) |
against core master branch?? |
To clarify, I'm just running
|
I believe it will be fixed by civicrm/civicrm-core#15741 |
Quite right. Specifically, a recent commit swapped Tangential factoids:
Anyway, the fix is merged into |
Thanks all |
@totten for the uninitiated muddling through what .php file do I need to edit? Which one in the Api4 folder is "...the main API call"...? I had this bork a wordpress site and this is surely the "fix" but I can't figure it out :p Error from a CLI: thrown in /home/hosted_site/civi.hosted_site.net/wp-content/plugins/civicrm/civicrm/Civi/API/Kernel.php on line 232` Thanks. |
@wolfsden3 is your issue related to this specific issue? Because this issue was solved by the following commit in 2019: and affected building a buildkit dev version of civi, but it sounds like you're getting an authorization failed error while running a cli command on a pre-existing wordpress site? If so, this isn't the right place to get help. You could try posting more info at civicrm.stackexchange.org or on chat.civicrm.org But if you are trying to build an offline test version of Civi and getting this error during the build, then we should reopen this issue. |
No it's not but the permissions issue from cli is the issue. I farted around with it for a hot minute then decided to just upgrade to the .0.0.1 release above what I had (the latest) LOL. It "fixed" whatever the issue was. Others had similar problems where the cli was working along just fine calling an api for things like sending email and they suddenly got that authorization problem. Why it magically happened who knows but doing the upgrade seemed to resolve this issue. The real problem is it crashed the entire Wordpress website just because civi crashed. That seems rude :P Thanks for your reply.
|
@wolfsden3 Yeah, that error doesn't quite tell you enough to pick a file to edit. It would help to:
In terms of quick mitigations, if there's a CLI command that hits a permission error, you can often resolve it by specifying a user, e.g. cv php:eval 'doSomething();'
cv php:eval --user=admin 'doSomething();' (I'm pretty sure |
Might be related to this: https://lab.civicrm.org/dev/core/-/issues/4362#note_91616 |
Expected: successful build
Actual: I get this error:
The text was updated successfully, but these errors were encountered: