The discussion revolves around embedding Google Calendar events in Discourse using the plugin_discourse_calendar plugin, which was initially developed by DavidGNavas and Vairix. The plugin was intended to allow embedding Google Calendar events via OneBox, and a pull request was submitted to integrate this functionality into the core OneBox codebase Daniel_Fernandez_Pes. However, users report that the feature is no longer working reliably in newer versions of Discourse, particularly after updates that affected OneBox behavior molly_cushing. Issues include missing parameters in the embed URL when using customized Google Calendar links, resulting in empty or broken calendars Tom_Newsom. Some users suggest using the plain embed URL from Google Calendar’s settings as a workaround Tom_Newsom. The plugin repository is now 404, and the topic has been moved to a broken plugin category RGJ. The community is seeking confirmation on whether Google Calendar embedding is still supported and how to achieve it without relying on the now-defunct plugin.
so what is the status of this? i would rather not install another plugin but do like the idea of being able to embed google calendars in topics. it would be very useful as a team/editorial calendar on our community.
The developer of this plugin was @Daniel_Fernandez_Pes from Vairix, perhaps he wants to submit the PR, I will notificate him. But, if he doesn’t mind, you are free to do it
While the embed works on here, any time I try to embed a Calendar on my forum, it doesn’t work.
I’m on the latest version of Discourse and OneBox is included with Discourse automatically now, right? So there’s nothing I really need to add is there?
Sorry for not contribute much to the conversation, but we have the same plugins installed (plus details) on a latest version docker instance and it works perfectly
If you click on “Customize etc.” and paste the long URL with all the parameters separated with & then the important bit (src=6hnjp743blahblahblah) doesn’t make it through.
I am not a coder so I don’t have the first clue about how to a)track down this issue in the source or b)submit a pull request to fix it, but hopefully this helps someone else with the same issue!
When you go to generate your embed code, just make all of your custom modifications and then look at the iframe tag that’s generated. take everything in the source attribute.