Plugin could not be activated because it triggered a fatal error. #38

Activity

1. tmatsuo commented on Mar 5, 2017

   

   tmatsuo

   on Mar 5, 2017

   Last edited by tmatsuo

   Contributor

   More actions

   @vivekkiran Sorry about the trouble.

   The plugin's primary use case is on GCP. Most of our Compute platform, we can automatically detect the projectId, so it's not a problem.

   If you use this plugin outside of our compute platform, you need to do several things.

   1. Visit Cloud Console, go to IAM & Admin -> Service accounts and create a service account with Storage Object Admin permission and download the json key file.

   2. Upload the json key file to the hosting server. Don't put it in a public serving area.

   3. Add the following line to wp-config.php (replace the file path with the real one).

   putenv('GOOGLE_APPLICATION_CREDENTIALS=/secure-place/my-service-account.json');
   

   Then the plugin should be able to detect the project id from the key file.

   We'll update the documentation soon.

   👍React with 👍1Reacted by Richard Octovianus Oey
2. logicalphase commented on Mar 9, 2017

   

   logicalphase

   on Mar 9, 2017

   More actions

   This works for me. They'll see this in the description, and it will save misunderstandings and potential poor reviews.
3. tmatsuo

   closed this as completedin #40on Mar 13, 2017
4. JamesVanWaza commented on Oct 25, 2017

   

   JamesVanWaza

   on Oct 25, 2017

   Last edited by JamesVanWaza

   More actions

   @tmatsuo were you able to update the documentation?
   @HyperPress, @vivekkiran how were you able to deploy your site?
5. nandenjin commented on Feb 21, 2019

   

   nandenjin

   on Feb 21, 2019

   More actions

   1. Visit Cloud Console, go to IAM & Admin -> Service accounts and create a service account with Storage Object Admin permission and download the json key file.

   In my case Storage Admin works fine, not Storage Object Admin.
6. n-paredes commented on Jun 2, 2021

   

   n-paredes

   on Jun 2, 2021

   More actions

   In my case the address was /home//etc/my-service-account.json