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

Site Editor: View on the editor back end doesn't match the front-end #52307

Closed
franzaurus opened this issue Jul 5, 2023 · 3 comments
Closed
Labels
[Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Bug An existing feature does not function as intended

Comments

@franzaurus
Copy link
Contributor

franzaurus commented Jul 5, 2023

Description

In WordPress 6.3-beta3, the template view at the back-end, doesn't match the front-end view. I noticed that at the front-end, bulleted list blocks are automatically inserted in the query block for blog posts, and in the navigation page list as well. It seems padding values are being ignored too.

Step-by-step reproduction instructions

  1. Activate Twenty twenty-three theme
  2. Open Editor
  3. Observe the home template content are displayed properly
  4. View the front-end
  5. Observe the front-end view doesn't match the back-end view

Screenshots, screen recording, code snippet

Back-end view

beta3-editor-view

Front-end view

beta3-front-end

Video

localwp-view

Environment info

  • Localwp 7.02+6395
  • WordPress: 6.3-beta3
  • PHP: 8.1.9
  • Server: nginx/1.16.0
  • Database: mysqli (Server: 8.0.16 / Client: mysqlnd 8.1.9)
  • Browser: Chrome 114.0.0.0 (Windows 10/11)
  • Theme: Twenty Twenty-Three 1.1
  • MU-Plugins: None activated
  • Plugins:
    • WordPress Beta Tester 3.5.0
    • WordPress Importer 0.8.1

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

@jordesign jordesign added the Needs Testing Needs further testing to be confirmed. label Jul 5, 2023
@jordesign
Copy link
Contributor

Hey @franzaurus - I haven't been able to recreate this with a fresh installation of WordPress (apart from the beta tester plugin). Are you able to recreate it in any other environments?

I also notice that you've got some additional content in your site. I don't expect that would make a difference - but are you able to check again with a totally empty/default installation of WordPress?

@jordesign jordesign added the [Type] Bug An existing feature does not function as intended label Jul 5, 2023
@franzaurus
Copy link
Contributor Author

franzaurus commented Jul 5, 2023

Hi @jordesign, thanks so much for your help in testing the issue. For this test, I used a WordPress fresh install in Localwp instance. But since your report said you can't replicate the issue, I've setup a different test environment via instawp. Apparently the issue is not reproducible there.

So I guess this back-end/front-end mismatch view is specific to a certain environment. In this case the issue is introduced by Localwp environment. I added a video in the original post for clarity.

Instawp environment

  • WordPress: 6.3-beta3
  • PHP: 8.1.20
  • Server: Apache/2.4.57 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/1.1.1f
  • Database: mysqli (Server: 10.6.14-MariaDB-1:10.6.14+maria~ubu2004 / Client: mysqlnd 8.1.20)
  • Browser: Firefox 115.0 (Windows 10/11)
  • Theme: Twenty Twenty-Three 1.1
  • MU-Plugins: None activated
  • Plugins:
    • WordPress Beta Tester 3.5.0

instawp-view

@t-hamano
Copy link
Contributor

t-hamano commented Jul 5, 2023

Hi @franzaurus,

This issue was also reported in #52199, but it is probably specific to the Windows OS environment.

Here is the ticket for the core: https://core.trac.wordpress.org/ticket/58711

This problem has also been fixed in Changeset 56136. Therefore, the fix will be reflected in the nightly build or the next beta version.

I would like to close this issue, but if I have missed something, please comment.

@t-hamano t-hamano closed this as completed Jul 5, 2023
@t-hamano t-hamano added [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed and removed Needs Testing Needs further testing to be confirmed. labels Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

3 participants