Skip to content
This repository was archived by the owner on Jan 6, 2023. It is now read-only.
This repository was archived by the owner on Jan 6, 2023. It is now read-only.

For those of your having issues with activating the plugin... #61

Open

Description

@ran-dall

I tried hard to get this plugin to work. It took a lot of Googling to finally get it to work. Maybe some of these clarifications may eventually work themselves into the readme; but at the very least, it may save you some man hours.

If your plugin isn't activating or is giving you some sort of fatal error, you haven't followed all the steps probably.
The first step is to carefully read the readme. The specific issue is also addressed here by @tmatsuo. You must make a service worker and export the .json key. When you save it, you HAVE to make sure the place you deploy it in a place that isn't public. I usually will make this happen with secrets or simply put it in /etc, if it's something easy.

The other critical step thing (that isn't mentioned on the readme)requires you to add and edit the first few lines (Lines 34-35) of your gcs.php, as explained here by @CaptainPatate.

$config = ['projectId' => 'Google Project ID'];
$storageClient = new \Google\Cloud\Storage\StorageClient($config);

The last line should already exist at Line 34 or 35, you simply just need to add the $config inside the parentheses

The final step (which was also pretty critical), was to give the right permissions to the bucket. I created an 'allUsers' permission and created it read and write. I know it's highly advisable not to do this but unfortunately, I couldn't' find any other way. Here's a screenshot of my permissions...

This is what made it work for me. I hope this helps some of you out too.
screen shot 1
screen shot 2

You could run something like this from command line too set the permissions:

gsutil acl ch -u AllUsers:RW gs://example-bucket

More info on it here: https://cloud.google.com/storage/docs/gsutil/commands/acl

Mods, feel free to close the issue. However, I do think you should consider adding a little more clarification to the readme.

Activity

  1. logicalphase commented on Oct 23, 2018

    @logicalphase

    The project ID should really be in a field in settings page. Asking users to edit php files directly creates all kinds of avenues for trouble.

  2. ran-dall commented on Oct 30, 2018

    @ran-dall
    Author

    @HyperPress Agreed. The fix is a bit primitive.

  3. self-assigned this
    on Dec 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions