To replicate…
- Create an untimed bookmark
on a poston a topic. - Refresh the page and delete the bookmark
I’m using the Discourse official hosting.
A user reports an error when creating and deleting an untimed bookmark on a topic, which consistently occurs on hosted Discourse sites. joe90 initially describes the issue, noting it happens across two different sites with various theme components. IAmGav and JammyDodger attempt to reproduce it without success until JammyDodger clarifies that the error only occurs when bookmarking a topic, not a post. After further testing, JammyDodger confirms the issue is resolved after updating to a newer version of Discourse. sam confirms the bug was fixed by @martin the previous day, and thanks JammyDodger for reporting it.
To replicate…
I’m using the Discourse official hosting.
i tried this on my test discourse, but i cant repo this.
Do you have any theme components installed ?
Yes, I do.
I run two different hosted sites and it happens on both of them. With the exception of “discourse gifs” (which was only installed a few days ago - I’m pretty sure the error was happening before that), theme components are different on both sites.
can you list them so that i can install them as well and then try to repo it
I’ve tried it in my test site, my live site, a site I’m on that’s discourse hosted, and here on meta and I can’t replicate it.
Are there are other steps I may be missing?
Here’s what I’m doing…

when last did you upgrade discourse, the theme & components ?
I’ve got it. You have to bookmark the topic, not a post. ![]()
Discourse is hosted so upgrades are automatic.
Themes/components are up to date. Site 2 is a new one - only started a couple of weeks ago - and everything started off up to date.
you can bookmark a post.
Not if you want to replicate the error
Oh, yeah. I just tried it on a post (not a topic) and it doesn’t cause the error.
I can reproduce it on my test site, my live site, and the Discourse hosted site I’m on, but not here on meta.
I’m not on the latest, latest update - so it could be that this is already fixed. I’ll update my test site and try again.
Steps to reproduce:
Edit: Updating to 28b00dc6fc has cleared this up on my test site. ![]()
Oh I think this was fixed yesterday by @martin . Thanks for confirming @JammyDodger and bringing this up!