WordPress.org
Get WordPress

Make WordPress Core

Opened 12 months ago

Closed 12 months ago

#59397 closed defect (bug) (reported-upstream)

Footnotes not saved if the Custom Fields panel is open

Reported by: greglone's profile GregLone Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Editor Keywords: has-testing-info
Focuses: Cc:

Description

How to reproduce:

  1. Create a post with title and some content.
  2. Add a footnotes block: add 1 or 2 footnotes to your content.
  3. Save your post.
  4. While still in your block editor, go to Options (top right of the screen), Preferences (very bottom of the menu), Panels, enable "Custom fields", click "Show & Reload Page".
  5. Now the "Custom fields" panel is displaying your post's metas.
  6. Note that the meta storing the footnotes' content is named footnotes, without the _ prefix, so it is a public meta. Its value is a JSON string.
  7. Edit your post content by adding another footnote and save your post.
  8. Reload the page:
    • The anchor in the post content is still there.
    • The new footnote has disappeared from the footnotes block.
    • The post meta in the "Custom fields" panel doesn't contain the new footnote either.

I haven't investigated but I guess this issue could be solved by making the post meta private, so it isn't displayed in the "Custom fields" panel.

Change History (5)

This ticket was mentioned in ​Slack in #core-test by ironprogrammer. ​View the logs.
12 months ago

#2 @oglekler
12 months ago

  • Keywords needs-patch added

Reproduction Report

This report validates that the issue can be reproduced as described.

Environment

  • OS: Windows 10, v22H2
  • Web Server: Nginx
  • PHP: 7.4.33
  • WordPress: 6.4-alpha-56267-src
  • Browser: Chrome 117
  • Theme: Twenty Twenty-Two
  • Active Plugins: -

Actual Results

  • ✅ Error condition occurs (reproduced).

#3 @ironprogrammer
12 months ago

  • Keywords has-testing-info added; needs-patch removed

Thank you for the report @GregLone! This issue may need to be addressed upstream in Gutenberg, so would you please report it in ​Gutenberg Issues? (I've removed needs-patch assuming this will be addressed in GB.)

You can copy contents of your report into the issue there. Please refer to this Trac ticket, and note that it was reproduced during Test triage.

Once the GB ticket has been created, please drop a note (and link) here and we can resolve this with reported-upstream. Thank you!

#4 @GregLone
12 months ago

Thanks for the instructions.
[Gutenberg ticket](​https://github.com/WordPress/gutenberg/issues/54653) open.

Version 0, edited 12 months ago by GregLone (next)

#5 @ironprogrammer
12 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to reported-upstream
  • Status changed from new to closed

Thank you for the follow-up, @GregLone!

Note: See TracTickets for help on using tickets.