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

Preview doesn't work after modifying on published posts #4099

Closed
2 tasks
idpokute opened this issue Dec 20, 2017 · 16 comments
Closed
2 tasks

Preview doesn't work after modifying on published posts #4099

idpokute opened this issue Dec 20, 2017 · 16 comments
Assignees
Labels
[Type] Bug An existing feature does not function as intended

Comments

@idpokute
Copy link
Contributor

Issue Overview

Preview doesn't work after modifying on published posts.

Steps to Reproduce (for bugs)

1.Add new post.
2.Write a title and add new paragraph block.
3.Publish it.
4.Delete the paragraph block.
5.Click Preview

Expected Behavior

Display the preview.

Current Behavior

The blank popup is showed and shows the message"Please wait…Generating preview." but nothing happens.

Possible Solution

Screenshots / Video

The post in the gif was already published. I did Step 4 and 5 of "Steps to Reproduce"
PreviewGIF

Related Issues and/or PRs

Todos

  • Tests
  • Documentation
@danielbachhuber danielbachhuber added the [Status] Needs More Info Follow-up required in order to be actionable. label Jan 23, 2018
@danielbachhuber
Copy link
Member

Hi @idpokute,

Thanks for the report. I can't reproduce this on master:

previewpublished

Does the issue still reproduce for you? If so, can you look at your console to see if there are any relevant JavaScript or network errors?

@idpokute
Copy link
Contributor Author

Hi @danielbachhuber

I updated Gutenberg V2.1, and I can still reproduce it.
In the screenshot, it seems you miss fourth step; Delete the paragraph block.

As you delete the one block, click the preview button. Than you could reproduce it.
Console doesn't show any related error so far.

@danielbachhuber danielbachhuber added [Type] Bug An existing feature does not function as intended and removed [Status] Needs More Info Follow-up required in order to be actionable. labels Jan 26, 2018
@danielbachhuber
Copy link
Member

Thanks for following up, @idpokute. As a matter of fact, I ran into this issue independently yesterday too (working on something unrelated).

@skorasaurus
Copy link
Member

skorasaurus commented Mar 5, 2018

Confirming that I am able to reproduce this on gutenberg 2.3 and wordpress 4.9.4 (I was about to report this myself); console does not display anything.

I'm also able to reproduce this on a vanilla wordpress install spun up with vvv with no plugins installed except gutenberg.

@skorasaurus
Copy link
Member

skorasaurus commented Mar 23, 2018

Just confirming that I'm still experiencing this on gutenberg 2.4. I should also note I am able to reproduce this as well if I follow steps 1-3 in the reproduction but instead for step 4, I add another block and added some text to it in case you were hypothesizing that a post without any blocks in it was the cause.

(confirming that this is still the case on gutenberg 2.7 as well)

@skorasaurus
Copy link
Member

Just following up, I'm still able to reproduce this on gutenberg 2.6 and wordpress 4.9.5; I have tried this on the vanilla wordpress spun up w/ vvv w/ no plugins; have experienced this on both firefox and chrome.

@skorasaurus
Copy link
Member

skorasaurus commented Apr 20, 2018

Just following up, I'm still able to reproduce this on gutenberg 2.7 and wordpress 4.9.5; I have tried this on the vanilla wordpress spun up w/ vvv w/ no plugins; have experienced this on both firefox and chrome.

I'm also able to reproduce this on my staging instance on my server used by production (php 7.1, apache)

@jhackett1
Copy link

jhackett1 commented Apr 25, 2018

I'm also seeing this on 2.7. I can't see any PHP or JS errors or obvious reason what's gone wrong.

I guess this is an effect of this unsupported functionality.

@skorasaurus
Copy link
Member

Still experiencing this on 2.8.

I've narrowed down that this only occurs if you do not click update before clicking preview.

@aduth
Copy link
Member

aduth commented May 31, 2018

Noting that this is a known as-of-yet unimplemented feature, since it relies on the ability to autosave published posts, which until recently was not possible.

Related: #4112 #1773

@danielbachhuber danielbachhuber self-assigned this May 31, 2018
@danielbachhuber
Copy link
Member

Let's make this happen!

@aduth
Copy link
Member

aduth commented Jun 6, 2018

Closing as duplicate of #2544.

@iamgini
Copy link

iamgini commented Jun 12, 2018

@danielbachhuber thanks.
Yes, I have mentioned that in #7253 , if you save the draft/post, then preview will work.
is that a bug or missing feature ?

@danielbachhuber
Copy link
Member

@ginigangadharan This is a known bug that's being worked on. While work is being tracked in #2544 and others, we can keep this issue open for visibility until it's addressed.

@aduth
Copy link
Member

aduth commented Jun 20, 2018

Closed by #7130.

@aduth aduth closed this as completed Jun 20, 2018
@MichelleBruegger
Copy link

I do have a slightly different behaviour after updating Gutenberg plugin to version 4.1.0
Worked fine with version 3.9, now all I get to see when I click on the Button "Vorschau" (in the German WP-version is no eye for the preview) it shows me an Error 404 page not found.

The url of the preview has id (example: www.mydomain.com/?p=190) and I don't know where this number comes from... post-id would be "2" and the page-url is /about

Is that "the same" issue or something completely different?

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

7 participants