1.0 beta questions/issues

With the 1.0-beta update, we’re switching from the now inactive Google Docs API to the Google Drive API v2, which doesn’t use plaintext user/pass, so those can be removed regardless, and should be.

As for the other fields, if they are present, Docs to WP will default to those values, and lock out the fields in the Options page (it’ll display as greyed out and you won’t be able to alter the values).

If you have created the API connection properly, it will connect. When it says Connection Status: Error! that generally means that it’s unable to use that connection, for one reason or other.

Unfortunately, this is a critical update, as Google has shut down their previous API. We are working on better debugging tools, but don’t have an ETA on when those will be pushed out.

From the sounds of it, though, it’s not able to see the connection as active.

private function _verifyConnection() {

                $this->_drive->connect(
                                        array(
                                                'access_token' => get_option( 'docs_to_wp_auth_token' ),
                                                'token_type' => 'Bearer'
                                        )
                                );

                $response = $this->_drive->get( '/about' );
                return !isset($response->error);

        }

That is the method used to verify the connection status. If a proper API key has been generated, this will always work. This hints to me that there is an issue with the App settings.

One thing that I would suggest is verifying that you have the Drive API activated in your App. You can do this by visiting the API Console and checking under APIS & Auth -> APIs under the Enabled tab, and if you don’t see Drive API there then that is the issue.

All you have to do is find it in the API Library tab and enable it, and Docs to WP should start working again.

That one I can tell you what the issue is. I use some anonymous functions which I’m thinking are breaking stuff for you. I’ll push out an update later tonight / early tomorrow moving away from anonymous functions.

Just pushed v1.1 with PHP 5.2 fixes. Let me know if this fixes it for you.

Yes and no. The API returned an invalid result, that didn’t come out as JSON, and the code I use to define what the error is uses json_last_error() which apparently wasn’t present in PHP until 5.3.

The solution is two-fold, but really I think you should email your hosting provider and upgrade your PHP, 5.2 is outdated, and in serious need of upgrade.

If you’re getting json_last_error as an undefined function, the PHP version thats being used to run your code is earlier than 5.3.0 according to http://php.net/manual/en/function.json-last-error.php

The personal vendetta is begging to sound plausible.

In all seriousness, I’m at a loss. If you have 5.4 now, you definitely should be fine running all the code.

if that doesn’t work, to make it work for you, you can simply remove this entire block:

switch (json_last_error()) {

                        case JSON_ERROR_NONE:
                                $error = null; // JSON is valid
                                break;

                        case JSON_ERROR_DEPTH:
                                $error = 'Maximum stack depth exceeded.';
                                break;

                        case JSON_ERROR_STATE_MISMATCH:
                                $error = 'Underflow or the modes mismatch.';
                                break;

                        case JSON_ERROR_CTRL_CHAR:
                                $error = 'Unexpected control character found.';
                                break;

                        // only PHP 5.3+
                        case JSON_ERROR_UTF8:
                                $error = 'Malformed UTF-8 characters, possibly incorrectly encoded.';
                                break;

                        case JSON_ERROR_SYNTAX:
                                $error = 'Syntax error, malformed JSON.';
                                break;

                        default:
                                $error = 'Unknown JSON error occured.';
                                break;

                }

                if( !empty( $error ) ) {

                        throw new JsonException($error);

                }

out of wrAPI/apis/Abstract_Api.php

That’s not something I’d be willing to take out of production, but for your case it would make the code work.