Users report issues with Google Docs oneboxing in Discourse, primarily due to Google’s requirement that documents be published (not just shared) for embedding. downey first identified the problem, noting blank placeholders and X-Frame-Options errors. techAPJ clarified that publishing is mandatory and confirmed embedding works for published docs. riking asked if URLs could be auto-converted to publish format, but techAPJ explained only owners can publish, and appending /pub doesn’t suffice.
Users like alehandrof and Andrew_Shanahan expressed frustration over broken functionality, especially for shared-but-unpublished docs, and requested disabling oneboxes or adding domain blacklists. Workarounds include adding a space before the URL or avoiding standalone lines. codinghorror and sam agreed embedding full docs is excessive and suggested opt-in or generic link previews instead.
techAPJ implemented improved previews with bold type labels (e.g., “Google Docs”) for private docs and made icons clickable. mcwumbly and erlend_sh suggested adding status notes like “Document is private,” which was implemented [22]. alehandrof reported URL path inconsistencies, later fixed [25].
Concerns were raised about overly long, redundant summaries for public docs [26], with sam proposing metadata like edit dates instead — though techAPJ noted this requires Google API access. Some users, like ewanly, still saw “Private” errors on published sheets, suggesting edge cases remain.
Community members like Andrew_Shanahan lamented lost functionality (e.g., weight-tracking spreadsheets), with Falco suggesting custom plugins as a workaround. Others, like burke and Hugh_Roberts, miss embedded docs and slides, urging reconsideration of opt-in embedding.
That worked. Thanks for the insight!
