# Cakeday plugin disabled

**URL:** <https://meta.discourse.org/t/cakeday-plugin-disabled/389830>\
**Category:** Bug\
**Tags:** cakeday, fixed\
**Created:** [November 27, 2025, 3:47pm UTC](https://meta.discourse.org/t/cakeday-plugin-disabled/389830 "2025-11-27T15:47:33Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![seabass](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/seabass/32/526971_2.png) [@seabass](https://meta.discourse.org/u/seabass)\
**Post date:** [November 28, 2025, 11:40am UTC](https://meta.discourse.org/t/cakeday-plugin-disabled/389830/5 "2025-11-28T11:40:51Z")

</div>

Things did go south. It was sketchy and did not work.

I just ran a Discourse site update and couldn’t get past the clean up migration you’re talking about.

This migration is crashing out. [discourse/plugins/discourse-cakeday/db/migrate/20251127125226\_delete\_old\_default\_values.rb at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/main/plugins/discourse-cakeday/db/migrate/20251127125226_delete_old_default_values.rb)

When the migration runs `migration_timestamp("20250717093505")` and `migration_timestamp("20250811132217")` from the `up` method you get nil values. Those nil values break the sql query in the `delete_settings` method of the migration.

---

_[View the full topic](https://meta.discourse.org/t/cakeday-plugin-disabled/389830)._