In the WordPress classic editor, avoid the SyntaxHighlighter Code Block
Posted by jpluimers on 2023/10/25
When you use the WordPress classic editor (which for me still works far better than the Gutenberg one), avoid at all cost the use of the [Wayback/Archive] SyntaxHighlighter Code Block – Page 2 – WordPress.com Support.
Each time you switch between from Text View back to Visual, some characters are html-encoded, like:
&becomes&>becomes>
Switching twice makes & into &>.
Switching three times makes & into &&&gt.
I already explained why to avoid the Gutenberg editor in Bookmarklet to force WordPress classic-editor.
Via:
- [Wayback/Archive] SyntaxHighlighter Code Block – WordPress.com Support
- [Wayback/Archive] Code Block – WordPress.com Support
- [Wayback/Archive] wordpress code block language classic editor – Google Search
–jeroen
Rate this:
Share this:
- Click to share on Mastodon (Opens in new window) Mastodon
- Click to share on Bluesky (Opens in new window) Bluesky
- Share on Tumblr
- Click to share on Reddit (Opens in new window) Reddit
- Click to share on Threads (Opens in new window) Threads
- Tweet
- Click to share on Telegram (Opens in new window) Telegram
- Click to share on Nextdoor (Opens in new window) Nextdoor
- Click to share on WhatsApp (Opens in new window) WhatsApp
- Click to print (Opens in new window) Print
- Click to email a link to a friend (Opens in new window) Email
Related
This entry was posted on 2023/10/25 at 12:00 and is filed under Classic editor, Development, Gutenberg editor, SocialMedia, Software Development, Web Development, WordPress, WordPress. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
This site uses Akismet to reduce spam. Learn how your comment data is processed.






Leave a comment