On my self-hosted Grist, the calendar widget has stopped working and now only shows: “Custom widget (not configured)”.
I know there was a recent discussion of the calendar widget, but I don’t have any ad blockers installed.
I’ve tried removing and then reinstalling the calendar widget, but to no avail.
Any thoughts?
Hi @J_Y!
I’d suggest setting the environment variable GRIST_SKIP_BUNDLED_WIDGETS=true on your installation for now.
In the last release of Grist, we changed to bundling the Calendar widget with the server (instead of loading it from our remote widget repository), due to issues with ad blockers.
However, some users have reported issues, as it requires another port to be opened on the server.
You can also try setting that port via GRIST_UNTRUSTED_PORT=XXXX and opening up your firewall. (Don’t worry about the environment variable name, it’s safe and doesn’t expose any additional security risk by default, it’s used to isolate bundled plugins from the main server). However, your mileage with that solution may vary, as it’s very dependent on how you’re hosting.
You can view the current port that the plugin server is running on in the console, with a line like this:
2026-06-18 23:05:10.901 - info: pluginServer available at localhost:43243
Next month’s release (end of July) should contain a permanent fix for this issue.
Hope that helps! Let me know if you have any issues.
Thank you for the reply!
I tried setting the environmental variable GRIST_SKIP_BUNDLED_WIDGETS=true, but it didn’t help.
It’s okay; I’ll wait until next month’s release. 
Ah, sorry to hear that didn’t solve things!
I did some more testing locally, and these two combined should do it:
The first disables the bundled version (which requires the extra port), the second ensures the hosted version still shows up in the “Add new widget” menu!
Thank you again!
Alas, adding those two lines didn’t help. I just get a blank screen
It’s okay; thanks again!