anubisthejackle

Nevermind. I’ve figured it out.

For anyone with the same issue, where I was going wrong was using the {thumb} and {title} tags, instead of {thumb_img} and {text_title}. The thumb and title tags are already wrapped in anchors, which breaks any wrapping anchor you attempt to use.

That extension looks like exactly what I’m looking for. I will have to keep it in mind the next time I have some spare change to invest in my little venture.

I have more tag customization slated for the next minor release. As for the spacing, you can accomplish that by adding this to your style.css file, or by using a custom css plugin, like Jetpack:

a.more-link{
    display: block;
}

Sorry for the late reply, I’ve only recently started development again.

Currently there’s no way to say “after the first paragraph” but that’s definitely doable for a future release. One way to get around this would be to make sure your paragraphs are all of the same length, and then set the word count to that length. After that you’ll want to set the Break On character to the end of line character.

That said, I’ll add paragraph expansion to the list.

ok, what I’ll have you do instead of relying on the notice from your host, is to take the cron job and make sure that you have these two lines:

$result = $docs_to_wp->startTransfer();
wp_mail( "YOUR_EMAIL_ADDRESS", "Docs To WordPress", print_r( $result, true ) );

And then forward the email you get to tweston AT bangordailynews DOT com

Without being hands on, it’s extremely difficult to debug this. When you visit the Options page for the plugin, does it say it’s connected? If so, is Drive API activated? If both of these things are true, then it’s possible that it wasn’t activated with the correct account. If thats not the case, I’m at a loss as to what it could be.

Where are you seeing the message?

It’s sounding like the plugin is working, but the app isn’t setup properly.

And you’re completely up-to-date with Version 1.1?

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.

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.

After a bit more reading, it looks like JSON is actually an extension, so if the code is 5.3 and you still aren’t getting the JSON functions, it may be that the extension isn’t loaded, which your host can fix easily enough.

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 https://php.net/manual/en/function.json-last-error.php

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.

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

I’ll make that a priority for the next release than.