-
Notifications
You must be signed in to change notification settings - Fork 20
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Hide the Publish Date for some statuses #593
Comments
Any update on this issue? We're running into this using Custom Statuses and posts getting published in the past. We have a "Media Required" draft state and as soon as a writer sets this status the PublishDate is set. |
@mgurtzweiler You can hide the status with the Editor Features option in PublishPress Capabilities. I'll close this issue for that reason |
What would hiding the status accomplish? We use the status fields to move posts through the workflow. The issue is setting the publish date when a status is assigned. |
https://developer.wordpress.org/reference/functions/register_post_status/ It looks like setting the date_floating option to true would solve this. |
Thanks @mgurtzweiler, this seems to be a Gutenberg issue, that is not respecting the date_floating param. We are already using date_floating = true: If using the classic editor, the issue do not happens. But if using Gutenberg it sets the publishing date by itself if we change the post status for any custom status. We are still looking for a fix. |
We probably need to fix this submitting a PR to Gutenberg fixing the function That function is checking date floating for a hardcoded list of statuses. It is not recognizing custom statuses. There is an issue for this already: WordPress/gutenberg#26984 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
This looks like a good idea.
We probably couldn't remove the date field, but we could hide it:
The text was updated successfully, but these errors were encountered: