-
Notifications
You must be signed in to change notification settings - Fork 3k
feat: adds UI control to unpublish the current locale #13693
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
base: main
Are you sure you want to change the base?
Conversation
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
Similar to my feedback on #13767 - if we accomplish this logic using the snapshot approach that we have now, could we avoid the experimental flag and provide this out-of-the-box? Note: we might need a new version field for Here's what our versions list view looks like when you publish in a specific locale. What does it look like if you unpublish in a specific locale? This is why we might need that ![]() |
Also I don't think that we should do this:
When you unpublish, you should indeed have a logged version in your version history that shows that the document became unpublished here. Any user feedback regarding confusion around this is likely because they are querying with In the future, the right fix for that confusion is to rename our |
7463f56
to
2f8c9ab
Compare
What
Adds a new option to unpublish content in the current locale only.
Why
Currently, if a user wants to unpublish a document for just one locale, they must first unpublish all locales and then re-publish the locales they want to keep published. This is inefficient and is a common request from the community.
Also part of our ongoing localization improvements.
How
This feature works much like
publishSpecificLocale
. A new argument,unpublishSpecificLocale
, is passed through the update operation.When provided, it:
_status: draft
similar to the general unpublish behaviorTODO
localizeMeta
works with this when that gets merged