Activating plug-in gives blank page

Update.

I have deleted the database and proceeded to re-install it.

After I started to activate plug-ins again I got the following error message and can’t update any other plugins.

Fatal error: Uncaught exception ‘InvalidArgumentException’ with message ‘Invalid Google Cloud Storage filename: gs://’ in /base/data/home/runtimes/php/sdk/google/appengine/api/cloud_storage/CloudStorageTools.php:345 Stack trace: #0 /base/data/home/apps/s~project-name-replaced-here/wpfromstarterproject.375460318752387030/wordpress/wp-content/plugins/google-app-engine/modules/uploads.php(238): google\appengine\api\cloud_storage\CloudStorageTools::getPublicUrl(‘gs://’, false) #1 [internal function]: google\appengine\WordPress\Uploads\Uploads::filter_directory(Array) #2 /base/data/home/apps/s~project-name-replaced-here/wpfromstarterproject.375460318752387030/wordpress/wp-includes/plugin.php(192): call_user_func_array(‘google\appengin…’, Array) #3 /base/data/home/apps/s~project-name-replaced-here/wpfromstarterproject.375460318752387030/wordpress/wp-includes/functions.php(1736): apply_filters(‘upload_dir’, Array) #4 /base/data/home/apps/s~project-name-replaced-here/wpfromstarterproject.375460318752387030/wordpress/wp-content/plugins/maxbuttons-pro/maxbu in /base/data/home/runtimes/php/sdk/google/appengine/api/cloud_storage/CloudStorageTools.php on line 345

I’m having the same issue

$ gcloud –version
Google Cloud SDK 0.9.22

$ wp status
PHP Warning: require_once(google/appengine/api/urlfetch_service_pb.php): failed to open stream: No such file or directory in /PROJECT/wp-content/plugins/google-app-engine/modules/urlfetch.php on line 72

Hi Richard

Did you get it to work?

I am having a lot of troubles due to not being able to activate the plugin. It is otherwise impossible to add posts, media, etc.

I was not able to get it running.

So the site I had on GAE runs fine on the frontend with the plugin deactivated but the backend is unusable.

With the plugin activated, I just get a white screen.

Either:

1. We’re missing something.

2. The sites we tried to install had some other issue conflicting with the plugin.

or

3. The current WordPress is not compatible with GAE.

This is the latest I discovered. It is more a workaround than a solution.

The app engine plugin interferes with two parts of my site, one is headway themes, and the other is a plugin called maxbuttons-pro.

I activate another theme (fourteen, etc.) and activate app engine without a problem. I can upload from the bucket, etc. No problems!

If I deactivate app engine, I can activate headway themes.

I have not had time to check if the same happens with maxbuttons-pro, but carefully reading the error message above, issue #4 refers to this plugin and therefore I assume it is the same as with HT.

Ultimately, I’d be good to know what is going on with bucket permissions, see first part of the error message specifies:

CloudStorageTools::getPublicUrl(‘gs://’, false)

Seems it app engine cannot read the buckets? May be?

May be connected to your issue (on local), I cannot edit certain plugins and I am told I have not enough permissions… But it is my own hard-drive.

I am not sure this means anything, but at some point, I saw a couple of buckets were created (may be the app engine automatically?) and they were related to headway theme and maxbuttons-pro, then the buckets were gone and I cannot replicate the process.

When I get the blank screen, I rename (add hyphen at end) the app engine plugin folder in my local version, upload with the launcher and it deactivates the plugin online. Just a tip to keep moving.

Anybody else reading this with ideas on how to permanently solve this, please help.

Thanks!

Solved this.

After activating app engine plugin, the instructions said to give it a bucket, once I did that I was able to activate headway themes and maxbutton-pro.

Which in turn, automatically created two buckets, one for each.

Still, the app engine plugin remains deactivated in the localhost copy, just fyi.

i am new to wordpress please some body help i am getting that wight screen of death when i activate plugin or theme and i found out there is space between some lines but dont know where

I have the exact same issue – clean install.

@lwall I’m not sure how you fixed this when you say : “After activating app engine plugin, the instructions said to give it a bucket, once I did that I was able to activate headway themes and maxbutton-pro.”

My error is the same as your original issue: once I activate the plugin I get the WSOD … so there’s no chance to “give it a bucket” as you say … or do you set the bucketname directly in the DB ?

UPDATE: I managed to a) create a bucket on my google cloud b) activate the plugin (and not having the site crash) c) entering the bucketname and saving the settings.

To obtain this, I disabled all other plugins first (I guess there are just some plugins that already try to tap into the settings of the Google App Engine plugin and hence crash the site)

Now I still need to (but not really) figure out why the default bucket is not working … I don’t seem to have a default bucket altho my cloud environment is recent (this week) so should have default bucket setup.

Hi everyone !
Can you explain me this story of bucket ?
I’m on a Compute Engine instance with WP 4.1.1 and GAE for WP 1.6
Thank you a lot !

Buckets I believe apply to storage.
Storage is is in two parts. Application Storage which hosts the MySQL operation files and is closely linked with the instance and then you can link your media files like video and pictures etc, which can be stored in their Storage offerings for which you sign up for separately in the console and later link to your application.

My own issue relates to Compute Engine. Ive tried for 7 days to get it working but at the last hurdle something always comes up e.g. Max file size. upladd for my theme. I get as far as editing the php.ini file offline and then hit problems uploading and trying to restart the instance, amongst many many other syntax gremlins in gcloud set up and the discovery of issues and errors all over the place. To be frank the whole thing feels like a beta to me. Its isnt plain sailing and Im thinking of ditching it all together and paying up at a regular vendor for some progress. I dont like Amazon… instance slowness put me off.