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.

Sign up for GitHub

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

Jump to bottom

Custom field parsing in Classical and Gutenberg editors #10323

Open
dariaknl opened this issue Jul 11, 2018 · 0 comments
Open

Custom field parsing in Classical and Gutenberg editors #10323

dariaknl opened this issue Jul 11, 2018 · 0 comments
Labels
severity: trivial Yoast: Content Preview Yoast Feature

Comments

@dariaknl
Copy link
Contributor

How can we reproduce this behavior?

  1. Open post and create custom field in lower case:

screen shot 2018-07-11 at 10 05 00

2. Scroll to Snippet Editor preview and add this custom field:

screen shot 2018-07-11 at 10 06 22

3. Open this post in Gutenberg editor and check Snippet Editor preview:

screen shot 2018-07-11 at 10 07 52

The custom field does not start with lower case anymore, which is not expected.

Technical info

  • WordPress version: 4.9.7
  • Yoast SEO version: 7.9 RC1
@dariaknl dariaknl added bug regression Label for high-prio issue labels Jul 11, 2018
@dariaknl dariaknl removed the regression Label for high-prio issue label Aug 8, 2018
@Djennez Djennez removed the type: bug label Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
severity: trivial Yoast: Content Preview Yoast Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dariaknl @Djennez