Google Docs embedding issue

[tomt1999]

Forum URL: 509th-vbw.proboards.com/

Embedding Google Docs does not work anymore. Probably for like the last 10 days or so. Did something change?

Thanks,

TomT

[Scott]

tomt1999 - I'm not aware of anything changing, but let me look into it.

[Eton Bones]

Aug 28, 2024 10:56:57 GMT -8 tomt1999 said:

Forum URL: 509th-vbw.proboards.com/

Embedding Google Docs does not work anymore. Probably for like the last 10 days or so. Did something change?

Thanks,

TomT

After reviewing recent posts on that forum, I think this might be a bad resource link rather than some systematic failure. Can the post's author verify that the Google Docs resource used in the post exists and it has been published? 

SPOILER: Click to show

[Source]

Publish file

Important:

• When you publish a chart to the web, people can see the data used to create it. Be careful when publishing a chart with private or sensitive info.
• Any changes you make to the original document will be updated in the published version. The automatic update might take a few minutes.
• To remove a file from the web, you must stop publishing it. Learn how to stop publishing a file.
• To stop sharing a file with collaborators, learn how to change sharing permissions.

1. In Google Docs, Sheets, or Slides, open a file.
2. At the top, click File  Share  Publish to web.
3. Choose a publishing option:
   • Spreadsheet: Publish the entire spreadsheet or individual sheets. You can also choose a publishing format.
   • Presentation: Choose how quickly to advance the slides.
4. Click Publish.
5. Copy the URL and send it to anyone you’d like to see the file. 

509th-vbw.proboards.com/post/25910/thread

509th-vbw.proboards.com/post/25881/thread

ETA:

I also missed the discussion in the shoutbox saying just as much

campsawyer: Any one have a tech support contact for the forum to ask what happened to Goggle docs?Aug 24, 2024 at 8:28pm

campsawyer: Something changed with the embed function in this forum. You need to go to an old Goggle doc post and copy the link, to a new post. Then get the ID of the doc from Goggle and change this in the link in the new post. Painful yes, but a workaround.Aug 24, 2024 at 8:28pm

tomt1999: You can create a share link of a google sheets document and paste it as a link. Opens in a new tab. I know that's not optimal, but it works. docs.google.com/spreadsheets/d/1pEFfkN-LgDEh5xXQfunLXyUMn3Dx5F9xzFeAxiblALY/pubhtmlAug 24, 2024 at 7:11pm

[tomt1999]

I cannot speak to the example post, but I tried it myself with a properly-published google sheet to no avail.

TomT

[Eton Bones]

Aug 28, 2024 14:22:02 GMT -8 tomt1999 said:

I cannot speak to the example post, but I tried it myself with a properly-published google sheet to no avail.

TomT

Thanks for that! 
I just noticed that you have the Gsheet plugin installed so could you perhaps post an example of what is being tried but is failing?

I am seeing mentions of "old" and "new" suggesting there are multiple methods being used (perhaps the plugin as well as the one built into Proboards)

I am also puzzled by the malformed BBCode at the bottom of this post, mainly because I cannot hit edit to see the actual BBCode being used.
An actual sample of the BBCode being used might help (wrap in code tag  to prevent inadvertent parsing).

Edit:
Also, just confirming that you haven't made any changes to your censored words list in recent days which might be impacting the use of google drive URLs ?

[rhreiss]

Aug 28, 2024 15:45:34 GMT -8 Eton Bones said:

Aug 28, 2024 14:22:02 GMT -8 tomt1999 said:

I cannot speak to the example post, but I tried it myself with a properly-published google sheet to no avail.

TomT

Thanks for that! 
I just noticed that you have the Gsheet plugin installed so could you perhaps post an example of what is being tried but is failing?

I am seeing mentions of "old" and "new" suggesting there are multiple methods being used (perhaps the plugin as well as the one built into Proboards)

I am also puzzled by the malformed BBCode at the bottom of this post, mainly because I cannot hit edit to see the actual BBCode being used.
An actual sample of the BBCode being used might help (wrap in code tag  to prevent inadvertent parsing).

Edit:
Also, just confirming that you haven't made any changes to your censored words list in recent days which might be impacting the use of google drive URLs ?

I am also a member of the same group as TomT   the post at this link 509th-vbw.proboards.com/post/25918 shows the results when embeding the same google spreadsheet with the old  code   which looks like this 
[gdoc]https://docs.google.com/spreadsheets/d/e/2PACX-1vTWs9NH8vy0GnrqbPCBe9ErdI5iofoJ-8Hoo3J8g15ziCFqzxSb0eC_7BomlLUO4sGICQOfNmpjIFtC/pubhtml?single=true&gid=1723183790[/gdoc]


and does work correctly when used in a new thread reply. And this new code that does not work 

[gdoc data-url="https://docs.google.com/spreadsheets/d/e/2PACX-1vTWs9NH8vy0GnrqbPCBe9ErdI5iofoJ-8Hoo3J8g15ziCFqzxSb0eC_7BomlLUO4sGICQOfNmpjIFtC/pubhtml?gid=1723183790&single=true["]insert code here

RoyR

[Eton Bones]

Thanks rhreiss

May I ask what process you use to produce the second (malformed) BBCode? How are you inputting the URL, and specifically, from where did you copy the URL?

The data-url attribute on that malformed BBCode is brittle since it requires stricter formatting rules as an attribute as opposed to nested text within the BBCode. It also looks like it contains an inadvertent quotation mark or square brackets, which resulted in prematurely closing the attribute and ultimately truncating the BBCode itself. The entified ampersand suggests it passed through a managed HTML source at some point, even if initially copied from a valid form field.

If I manually remove that errant opening square bracket from the attribute and complete the BBCode by giving it an ending tag, it then has no problem displaying in the post

[gdoc data-url="https://docs.google.com/spreadsheets/d/e/2PACX-1vTWs9NH8vy0GnrqbPCBe9ErdI5iofoJ-8Hoo3J8g15ziCFqzxSb0eC_7BomlLUO4sGICQOfNmpjIFtC/pubhtml?gid=1723183790&single=true"][/gdoc]

Jul 19, 2018 4:06:27 GMT -8 Scott said:

FYI everyone...

When you click on the embed icon and then the Google Drive icon, there is a link for help:



Clicking on the help link gives these instructions which include the need to 'publish' the document:




In addition we have a new Help Guide article on How to Use the Google Drive™ Embed   

[rhreiss]

Aug 28, 2024 19:35:27 GMT -8 Eton Bones said:

Thanks rhreiss

May I ask what process you use to produce the second (malformed) BBCode? How are you inputting the URL, and specifically, from where did you copy the URL?

The data-url attribute on that malformed BBCode is brittle since it requires stricter formatting rules as an attribute as opposed to nested text within the BBCode. It also looks like it contains an inadvertent quotation mark or square brackets, which resulted in prematurely closing the attribute and ultimately truncating the BBCode itself. The entified ampersand suggests it passed through a managed HTML source at some point, even if initially copied from a valid form field.

If I manually remove that errant opening square bracket from the attribute and complete the BBCode by giving it an ending tag, it then has no problem displaying in the post

[gdoc data-url="https://docs.google.com/spreadsheets/d/e/2PACX-1vTWs9NH8vy0GnrqbPCBe9ErdI5iofoJ-8Hoo3J8g15ziCFqzxSb0eC_7BomlLUO4sGICQOfNmpjIFtC/pubhtml?gid=1723183790&single=true"][/gdoc]

Jul 19, 2018 4:06:27 GMT -8 Scott said:

FYI everyone...

When you click on the embed icon and then the Google Drive icon, there is a link for help:



Clicking on the help link gives these instructions which include the need to 'publish' the document:




In addition we have a new Help Guide article on How to Use the Google Drive™ Embed   

To answer your question for the code provided I copied a link that worked earlier along with the code that worked for the first example then I copied that url . then clicked on the embed icon then the Google Drive icon and pated that url into the popup window for the Google drive url. You may have identified that the new code proboards embed feature is
producing "malformed BBCode".  Can you explain in simpler less technical terms exactly  what your changes to the malformed BBCode were.  When I look at the BBCode code it looks like the old version that worked in the past. 

Thanks

[tomt1999]

I will try to post a Google Doc here. If it works, it may be setting in our own forum:

[tomt1999]

Not only did the doc not post (above), but the text after it that said "Google doc above here" did not post.

TomT

[tomt1999]

https://docs.google.com/spreadsheets/d/1pEFfkN-LgDEh5xXQfunLXyUMn3Dx5F9xzFeAxiblALY/pubhtml

[Eton Bones]

Aug 29, 2024 4:24:37 GMT -8 tomt1999 said:

I will try to post a Google Doc here. If it works, it may be setting in our own forum:

Aug 29, 2024 4:25:46 GMT -8 tomt1999 said:

Not only did the doc not post (above), but the text after it that said "Google doc above here" did not post.

TomT

Aug 29, 2024 4:26:03 GMT -8 tomt1999 said:

https://docs.google.com/spreadsheets/d/1pEFfkN-LgDEh5xXQfunLXyUMn3Dx5F9xzFeAxiblALY/pubhtml

OK thanks for that.
That definitely cleared up some questions

The docs.google.com/spreadsheets/d/1pEFfkN-LgDEh5xXQfunLXyUMn3Dx5F9xzFeAxiblALY/pubhtml leads to a valid GDoc URL but Proboards is not seeing it as such when it converts. Switch back and forth between Preview tab and BBCode tab once the URL has been entered to see what happens.

1. Without the gid=# in the URL, the WYSIWYG is not recognizing it as a valid gdoc URL
   https://docs.google.com/spreadsheets/d/1pEFfkN-LgDEh5xXQfunLXyUMn3Dx5F9xzFeAxiblALY/pubhtml?gid=0

   
   

2. Without the "e" path in the URL, the WYSIWYG is not recognizing it as a valid gdoc embed URL
   https://docs.google.com/spreadsheets/d/e/1pEFfkN-LgDEh5xXQfunLXyUMn3Dx5F9xzFeAxiblALY/pubhtml
   
   *according to the shoutbox discussion tomt1999 referred to that as a "share link" (as opposed to an embed link).

   
   

3. With no pattern recognition then no conversion occurs and no ending [/gdoc] tag is produced, resulting in the BBCode eating whatever comes after it before encountering something that forces it to close. Then the tag is removed, including whatever it ate.

I'm not a Google Drive user, so I am not overly familiar with its URL patterns. But it appears that if you use a URL with the proper "gid=#" and "e/" (for embed) path, the embed works. There is obviously a difference between a share link and an embed link. Try following the instructions to get the embed link and give that a try

Jul 19, 2018 4:06:27 GMT -8 Scott said:

FYI everyone...

When you click on the embed icon and then the Google Drive icon, there is a link for help:



Clicking on the help link gives these instructions which include the need to 'publish' the document:




In addition we have a new Help Guide article on How to Use the Google Drive™ Embed   

[rhreiss]

A couple of points to reset some of the discussion. This is a problem the at least 5 people using the group in question have encountered and using it successfully in the pasts. Something has changed.

Eton Bones has identified that the code using embed function is different.
But this new code that does not work  using a URL with proper "gid=#" and "e/" (for embed) path does (url below) so the fact that those are missing from some of new URLs generated by Google are not the reason attempts to embed are failing.

gdoc data-url="https://docs.google.com/spreadsheets/d/e/2PACX-1vTWs9NH8vy0GnrqbPCBe9ErdI5iofoJ-8Hoo3J8g15ziCFqzxSb0eC_7BomlLUO4sGICQOfNmpjIFtC/pubhtml?gid=1723183790&single=true["]
The latest urls produced for new spreadsheets produced by Google drive do not contain the /e.  Can anyone point to something had explains that requirement. 

One final request, quit posting "Try following the instructions to get the embed link"  multiple people have been doing that and it is not working which is why the original request for assistance was made. If some one else wants to try the embed feature using the url above they are welcome to try.

[jokerswild]

We also have this same problem. 

Certainly hope ProBoards can resolve this one. 

[Scott]

Unfortunately I do not have an answer for you at this time, however we are still looking in the issue.