Google Spreadsheet only showing as link

AI-generated summary

Users are discussing a change in Discourse’s handling of Google Spreadsheets, which previously embedded spreadsheets directly into posts but now only displays them as links after upgrading to version 1.6.10. mikechristopher notes this disrupts workflow, as users could previously edit sheets inline. codinghorror confirms the change was intentional due to security and performance concerns, citing a prior decision to avoid embedding full spreadsheets. mikechristopher expresses disappointment and asks if an opt-in embedding feature was possible; codinghorror replies that while previews have improved, full embedding won’t return. Stephen laments the loss, noting teams now resort to screenshots, which are less functional. codinghorror suggests a potential workaround via whitelisting iframes, though no solution is confirmed. The thread reflects user frustration over lost functionality and hopes for future alternatives.

Hi Has there been any changes to the one box for google spreadsheets?

We have had an upgrade during the week to 1.6.10 - b0fe5d383ec1c9f1ccd888e793a321193d376e6a

Before the upgrade when putting in the link for gsheets they were parsing as per below:

Where as now they are only showing as per below

The guys used to update the sheet without having to go into it and could do it within the post

Correct, it was a dire mistake to load the entire spreadsheet inside Discourse. See

OK thanks @codinghorror

I think we are going to have to revisit this then as is rather unfortunate for us. I take it there was no way of having it as an opt in feature to have it embed the whole thing

I would love to be able to get a special weight recording system built at some point.

Yes, @techapj recently improved this, so there’s more of a preview but we still won’t be embedding any time soon :wink:

It’s a shame it had to go, I’m aware of a couple of team sites who used it quite effectively.

Their latest solution is to screenshot the content which isn’t remotely as useful :persevering_face:

There might be some workaround to whitelist an <iframe> maybe, I’m not sure.