H
by kno
0 (0 reviews)
Highlight Source Pro
Powerful, XHTML-compliant, server-side code highlighting for pretty much all languages
Tested up to WP 2.5 (Current: 6.9.4)
v1.3
Current Version v1.3
Updated 17 years ago
Last Update on 10 Apr, 2008
Refreshed 6 hours ago
Last Refreshed on
Rank
#23,371
-164 this week
Active Installs
30+
—
No change
KW Avg Position
N/A
—
No change
Downloads
13.5K
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 40
30+
40+
986
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 2 more installs to reach 40+
Rank Changes
Current
#23,371
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 0 of 0| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| No keyword data available yet. | ||||
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.3
- Last Updated
- Apr 10, 2008
- Requires WP
- 2.3+
- Tested Up To
- 2.5
- PHP Version
- N/A
- Author
- kno
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
WP Adminify – White Label WordPress, Admin Menu Editor, Login Customizer
7K+ installs
#2,711
Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits
30K+ installs
#953
Gutenberg Essential Blocks – Page Builder for Gutenberg Blocks & Patterns
200K+ installs
#267
A
Adminimize
200K+ installs
#278
The Plus Addons for Elementor – Addons for Elementor, Page Templates, Widgets, Mega Menu, WooCommerce
100K+ installs
#321
Frequently Asked Questions
Common questions about Highlight Source Pro
As long as they aren't wrapped in <pre>-tags with a lang=-attribute nothing is going to happen - your markup will stay untouched. Highlight Source Pro only hooks in for those <pre>-tags having a lang=-attribute.
The line-numbering is the one problem here, because - currently - it requires to break with the XHTML-Standard. Because the <ol> is always and guaranteed inside a <div> with the .geshi-class there is no need for the class-attribute on the list element. Also due to the fact that a CSS-classname is not allowed to start with a number, this solution is valid XHTML for downgrading and can never interfere with existing CSS-rules.
Yep. The basic idea is, once again, backwards compatibility. If you consider your code-blocks being important you'll most likely want to add a heading instead of just a line, on the other hand you can simply use the title-feature to show which file is being talked about. Since the title-string will be placed inside a <div> you'll be fine as long as there's no line-break (and your markup is valid)
There's two ways of handling code-listing in your original post source. You can either use the HTML-input and hardcode PHP, C or whatever you think about, statements in there, Highlight Source Pro will handle those listings without any problems (in fact, it's the safer version to use for Highlighting as all characters are present in their original form). On the other hand this will get problematic if - for any reason - you stop using Highlight Source Pro, because WordPress (and every other serious software) will strip lots of those listings for security and compatibility reasons. If you want to be sure that your listings don't break when moving to another platform you should consider using htmlentities() on your listings, or writing them with the Visual Editor in the first place, so when falling back everything will be displayed as you want. In this case you'll have to use the enc__-prefix to tell Highlight Source Pro to apply html_entity_decode() before the actual syntax-highlighting. While this might be the more default case it's still the one requiring the alteration with the prefix, for compatibility reasons. If encoded scripts would be marked with the original language-signature and the source would later on be used in another GeSHi-environment things would get very, very complicated and confusing.