# Bug when discobot assigns the name in the certificate

**URL:** <https://meta.discourse.org/t/bug-when-discobot-assigns-the-name-in-the-certificate/64220>\
**Category:** Bug\
**Tags:** discobot\
**Created:** [9. Juni 2017 um 10:38 UTC](https://meta.discourse.org/t/bug-when-discobot-assigns-the-name-in-the-certificate/64220 "2017-06-09T10:38:18Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee)\
**Post date:** [12. Juni 2017 um 17:34 UTC](https://meta.discourse.org/t/bug-when-discobot-assigns-the-name-in-the-certificate/64220/21 "2017-06-12T17:34:34Z")

</div>

It’s very clear that the bot is not to blame since the real name is in the database, as evidenced by the rails command above.

Of course, the big question remains, how that name got there when `enable names` has been disabled from the start.

I have a strong feeling that this is a good lead to follow:

> [@Mittineague](#):
>
> Way back when, did you do more than CSS when you were working on group titles showing on the user cards?

Changing the CSS obviously wont write names into the db, but that’s precisely why @Mittineague asked about other activities at the time…

---

_[View the full topic](https://meta.discourse.org/t/bug-when-discobot-assigns-the-name-in-the-certificate/64220)._