Frontity shows `&` when ampersand is used in a title
See original GitHub issueBug report
- I’ve searched for existing issues
- I’ve checked documentation: https://docs.frontity.org
- I’ve checked community forum: https://community.frontity.org
Describe the expected behavior
If I use an ampersand in one category of my WordPress, it should display the character &
instead of &
.
Describe the observed behavior
Frontity is displaying &
in both twentytwenty-theme and mars-theme for the category Business & Marketing
.
twentytwenty-theme
mars-theme
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (14 by maintainers)
Top Results From Across the Web
AMP package - Currently in Development
In order to go through all the urls of test.frontity.org, I create a new json file at the root of the project, sitemap.json...
Read more >Ampersand Symbol (&) turning into & - Stack Overflow
This is fine when it's processed by the browser, as it will understand the & as an ampersand. However, in the context of...
Read more >including an ampersand (&) in the site title - WordPress.com
Does anyone know, please, if I will have problems if I include an ampersand (&) in the site title of my site/blog?
Read more >Analyzing the Ampersand. When to use “and” versus “&” in UX…
The ampersand should always be used when it's part of a company name, logo, proper noun, or title. This is one of the...
Read more >Sitemap - Programar Plus
24: Creación de plantillas con subrayado | Programar Plus · # 26: use complementos de jQuery ... Desde WordPress hasta Apple News, lectura...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In that case I ll change the wp-source to
unescape
in every field that is not a.rendered
. It’s technically double work, but seems like the only solution.Yeah… I don’t think this should be done at the state manager level, but either in the theme with a
decode
function exposed by frontity or automatically by wp-source.