Pluskit & Google Doc Key Question

Classic
1

Hello to all who are reading this.

I am in the process of helping a friend build an educational website and I am running into a problem with integrating a gdoc via Pluskit. In the past (obviously a while ago), I’ve not encountered this issue.

I have searched the form an the web for a solution but still no luck. In one of the posts I found here, I followed the directions to the letter (similar to the Pluskit page).

In Isaiah’s example, he says to enter the key where the key is the alpha-numeric string after the d/ and before the /p:

@gdoc((https://docs.google.com/document/d/1wPlbk8Gs1aKVfNEUW2P6CpreKjZJI8HW_jXXik3ra0/pub))

When I go publish the document to the web and get the link, it reads with extra characters (I.e. e/ after the d/).

The document will not show up on a Styled Text page when using the command:

@gdoc((+ key/pub))

I’ve tried leaving the e/ and also without the the e/ (and even the 2PACX) but cannot get it to work. Is this an issue with how Google is now creating the links or am I completely missing the context?
I would reach out to Yourhead directly, but I’m still waiting for a response to a ticket # from several weeks ago. I thought that here might bring a quicker resolution.

Any help will be appreciated. Thanks in advance.

Slavi

2

Hi @Slavi,

PlusKit hasn’t been updated in quite a while by its maker (Yourhead Software). It looks like Google has changed how their docs are accessed and that PlusKit is still trying the old way.

Google, of course, wants you to embed the file rather than load it in a reader, as that will fetch them more data (and Google thrives on collecting data).

Here’s how to do that, if PlusKit fails:

Cheers,
Erwin

1 Like