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

No publish button #5874

Closed
maddisondesigns opened this issue Mar 29, 2018 · 11 comments
Closed

No publish button #5874

maddisondesigns opened this issue Mar 29, 2018 · 11 comments
Assignees
Labels
[Type] Bug An existing feature does not function as intended

Comments

@maddisondesigns
Copy link

Issue Overview

I tried creating a new Page to test something. I entered a title and pasted in three paragraphs of text.

I went to Publish the page but there's no Publish button. Only a Schedule... button.

gutenberg_nopublishbutton

Steps to Reproduce (for bugs)

  1. Create new page
  2. Enter page title
  3. Try and click the publish button

Expected Behavior

There should be a Publish button

Current Behavior

No Publish button

Gutenberg 2.5.0
Firefox Quantum 59.0.2 (64-bit)
WP 4.9.4

@maddisondesigns
Copy link
Author

As a side note: Even after saving as a draft, the button remains as Schedule... instead of turning into an Update button

@Soean
Copy link
Member

Soean commented Mar 29, 2018

This normally happens, if you publish date is in the future. The Classic editor has the same behavior.

@maddisondesigns
Copy link
Author

maddisondesigns commented Mar 29, 2018

I wasn't trying to Publish in the future. The Schedule... button only appears (or should only appear) if you specifically set a future date, which I didn't. I simply tried to create a new page.

@johnbillion
Copy link
Member

I'm seeing this too. To reproduce, simply open a new Post or Page and note that the Publish... button says Schedule....

The button's behaviour appears to work as expected, but its label is incorrect. In order to get the button to say Publish... you need to change the post date to something prior to the current day.

@johnbillion johnbillion added the [Type] Bug An existing feature does not function as intended label Mar 29, 2018
@gziolo
Copy link
Member

gziolo commented Mar 29, 2018

@jorgefilipecosta, is it related to your latest changes in #5767 and test removal #5858?

@jorgefilipecosta
Copy link
Member

Yes @gziolo, It may be related to the changes, but I'm not being able to reproduce, maybe it's a timezone related problem.
@maddisondesigns and @johnbillion thank you for reporting this issue, could you please share your time zone? (as it relates to dates it may happen just in some time zones)

@jorgefilipecosta jorgefilipecosta self-assigned this Mar 29, 2018
@johnbillion
Copy link
Member

My timezone is set to Europe/London.

@Soean
Copy link
Member

Soean commented Mar 29, 2018

Berlin is UTC+2

  • If I select Berlin as Timezone I see the Schedule button
  • If I select UTC+2 I see the Publish button

Same in both settings:
Universal time (UTC) is 2018-03-29 14:52:14.
Local time is 2018-03-29 16:52:14.

@jorgefilipecosta
Copy link
Member

Thank you @Soean and @johnbillion this information was very useful!
I'm now able to reproduce the problem. If we select a city as the time zone of the website the problem happens if we select a UTC version the problem does not happen. I will submit a fix soon.

@maddisondesigns
Copy link
Author

Looks like you don't need it anymore, but my timezone is set to Australia/Melbourne

@jorgefilipecosta jorgefilipecosta added the [Status] In Progress Tracking issues with work in progress label Mar 30, 2018
@jorgefilipecosta jorgefilipecosta removed the [Status] In Progress Tracking issues with work in progress label Apr 3, 2018
@jorgefilipecosta
Copy link
Member

Thank you all for the reporting and debugging, a fix for this was merged #5916 and should be available in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

5 participants