Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Unpublishing #58

Open
runesandnes opened this issue Mar 25, 2023 · 4 comments
Open

Feature request: Unpublishing #58

runesandnes opened this issue Mar 25, 2023 · 4 comments

Comments

@runesandnes
Copy link

I was a bit surprised that the Scheduled Publishing plugin doesn't support unpublishing.
Is there a plan to add this, or are there good reasons it doesn't have it?

For now I'm going to add publish and unpublish date fields to our schemas, but a turn-key solution for this would be better.

@thomaslgj
Copy link

thomaslgj commented Mar 28, 2023

Second this. Also, a scheduling queue would be nice. This way we could schedule both when the document is published, AND when it is unpublished, at the same time.

@gadgetgnome
Copy link

I second this! We really need this for our Enterprise project as well.

@swee37
Copy link

swee37 commented Jan 24, 2024

I have added scheduled unpublishing in a fork, if anyone is interested in taking it for a spin:
https://github.com/swee37/sanity-plugin-scheduled-unpublishing

@thefivetoes
Copy link

@swee37 thanks for creating the fork! I am trying to install it and am getting some dependency conflicts:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/styled-components
npm ERR!   styled-components@"^5.2.0" from the root project
npm ERR!   peer styled-components@"^5.0 || ^6.0" from @sanity/[email protected]
npm ERR!   node_modules/@sanity/scheduled-publishing
npm ERR!     @sanity/scheduled-publishing@"[email protected]:swee37/sanity-plugin-scheduled-unpublishing.git" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer styled-components@"^6.1" from [email protected]
npm ERR! node_modules/sanity
npm ERR!   sanity@"^3.21.1" from the root project
npm ERR!   peer sanity@"^3.0.0" from @sanity/[email protected]
npm ERR!   node_modules/@sanity/scheduled-publishing
npm ERR!     @sanity/scheduled-publishing@"[email protected]:swee37/sanity-plugin-scheduled-unpublishing.git" from the root project

It looks like package.json is the same for both the official plugin and your fork. I am running Sanity 3.26.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants