Get help on Discord

Calendar plugin schedule button not showing despite adding document type

17 replies
Last updated: Jan 28, 2026
Hello Sanity people, do you have any experience with the https://www.sanity.io/blog/calendar-plugin ? I can’t make it work, the schedule button does not show even though I’ve added my document in the content-calendar.json:

{
  "types": [
    {
      "type": "homePage",
      "field": "publishedAt"
    }
  ]
}
Does anyone know what could be wrong here?
🤔 
homePage
is the name of my custom document
AI Update

I need to give you some important news: the Content Calendar plugin you're trying to use is officially deprecated and archived. The GitHub repository was archived on April 12, 2023, and the README explicitly states: "NOTE: This plugin is deprecated. Use Sanity Scheduled Publishing instead."

This means the plugin is no longer maintained or supported, which is why you're having issues getting it to work. Even if you troubleshoot the configuration, the plugin isn't compatible with modern Sanity Studio versions and has been intentionally discontinued by the Sanity team.

Here's what you should use instead:

Sanity now has native scheduling capabilities built directly into the platform. There are two main options depending on your needs:

  1. Built-in Scheduled Publishing - For scheduling individual documents, Sanity has native scheduling features that work directly in the Studio without needing external plugins. This is the direct replacement for the old calendar plugin.

  2. Content Releases - If you need more advanced capabilities like bundling multiple document changes together, Content Releases is Sanity's modern solution (available on Growth plans and above). It lets you:

    • Stack and stage content updates across multiple documents
    • Schedule releases for automatic publishing at specified times
    • Preview and validate everything before it goes live
    • Coordinate complex content launches without manual tracking

Why the old plugin doesn't work:

The calendar plugin was built for Studio v2 and hasn't been updated for Studio v3's architecture changes. The repository is archived, meaning no updates or bug fixes will ever come. The Sanity team deprecated it specifically because the native scheduling features are more reliable, better integrated, and actively maintained.

Next steps:

  1. Remove the old content-calendar plugin from your project entirely
  2. Delete the content-calendar.json configuration file
  3. Check the current Sanity documentation for the built-in scheduled publishing feature that matches your Studio version
  4. If you need bundled release workflows, evaluate whether Content Releases fits your needs

Sorry you hit a dead-end with the archived plugin, but the modern native alternatives are genuinely better and will save you future headaches! The plugin being deprecated is actually why it's not working, not a configuration issue on your end.

Show original thread
17 replies

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Get started for freeExplore the demo

Was this answer helpful?