mark elements so they’ll get highlighted regardless, including in RSS Feeds and posts syndicated in email (as long as the
mark element is supported in the client).
This extended Code block uses language auto-detection to add syntax highlighting, but you can override the language in the block’s settings sidebar. (There is currently no syntax highlighting of the Code block in the editor.) The plugin supports all programming languages that highlight.php supports (being a port of highlight.js). The Code block also is extended to support specifying the aforementioned highlighted lines. There is also a checkbox for whether to show line numbers on the frontend (with the numbers being non-selectable). Lastly, given inconsistencies across themes as to whether lines in a Code block should be wrapped, this plugin adds styling to force them to no-wrap by default, with a checkbox to opt-in to wrapping when desired.
For advanced usage, please see the plugin wiki.
This plugin is developed on GitHub. See list of current issues with the plugin. Please feel free to file any additional issues or requests that you may come across. Pull requests are welcome.
This is a fork of Code Syntax Block by Marcus Kazmierczak (mkaz), which is also available on WordPress.org. Copyright (c) 2018 Marcus Kazmierczak. Licensed under GPL 2.0 or later.
highlight.php is released under the BSD 3-Clause License. Copyright © 2006-2013, Ivan Sagalaev (email@example.com), highlight.js (original author). Copyright © 2013, Geert Bergman (firstname.lastname@example.org), highlight.php
Contributors & Developers
“Syntax-highlighting Code Block (with Server-side Rendering)” is open source software. The following people have contributed to this plugin.Contributors
“Syntax-highlighting Code Block (with Server-side Rendering)” has been translated into 8 locales. Thank you to the translators for their contributions.
Translate “Syntax-highlighting Code Block (with Server-side Rendering)” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
For the plugin’s changelog, please see the Releases page on GitHub.