Viktor Szépe

<h4>Only for development!</h4>
<p>Displays:</p>
<ul>
<li>Header</li>
<li>Thumbnails</li>
<li>The Loop (content)</li>
<li>Footer</li>
<li>Included template parts</li>
<li>Highlight script, link and style elements</li>
</ul>
<p>To remove <strong>all</strong> registered scripts and styles add <code>?remove-scripts</code> to the URL. All these scripts and styles will be listed at the bottom of the footer as HTML comment. This way it is possible to detect non-WordPress script printing.</p>
<p>If you are not an administrators add <code>?view-source</code> to the URL to activate Frontend Debugger.</p>
<p>Notice: This plugin uses regular expressions and <code>eval()</code> to get the current template apart.</p>
<p>TODO: sidebar, search-form.</p>
<p>The mini control panel contains:</p>
<ul>
<li>Header, Thumbnails, The Loop, Footer, Included files anchors</li>
<li>Toogle button for line numbers</li>
<li>Toggle button for line wrapping</li>
<li>Toggle button for showing line ends</li>
<li>Button for script and style highlighting</li>
</ul>
<p>From the second click on the <code>Highlight</code> button loops through (scrolls to) all scripts and styles.</p>
<p>The control panel’s state is kept in your browser’s <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage" rel="nofollow ugc">localStorage</a>.</p>
<p>Development of this plugin goes on on <a href="https://github.com/szepeviktor/frontend-debugger" rel="nofollow ugc">GitHub</a>. Please contribute by sending PR-s implementing my TODO-s.</p>


Frontend Debugger

Display prettified page source on the frontend.

<p>Powerful, flexible, XHTML-compliant, server-side code highlighting, credits for everything<br />
but ‘making it a plugin’ go to <a href="http://jpipes.com/index.php?/archives/216-Syntax-Highlighting-and-Allowing-HTML-in-Comments.html" rel="nofollow ugc">Jay Pipes</a><br />
and <a href="http://geshi.org/" rel="nofollow ugc">GeSHi</a>.</p>
<h4>Features</h4>
<ul>
<li>Highlight sources of any language</li>
<li>automatically, server-side (no javascripts)</li>
<li>XHTML-Compliant, <code><div></code>, <code><ul></code>, <code><span></code> with class-attributes and a css-file are used for styling    </li>
<li>optionally add a heading for every code-block</li>
<li>optionally specify line-number offset (BREAKS XHTML COMPLIANCE)</li>
<li>optionally don’t display line-numbers</li>
<li>set per-codeblock if the code is html_entity_encoded or not</li>
<li>only parses <code><pre></code>-tags with the <code>lang=</code>-attribute, thus does not interfere with any regular preformatted contents you might have</li>
<li>degrades beautifully through <code><pre></code>-tags (if you keep the sources clean, that is)</li>
<li>all settings through logical, valid arguments for the main container</li>
<li>comes with generic cross-browser CSS (tested: IE5.5+, FF, Safari, Opera)</li>
</ul>
<h4>Version History</h4>
<ul>
<li>1.3: Thanks to a tipp now the link-path to the stylesheets is correct, sorry for the inconvenience</li>
<li>1.2: Leading whitespace isn’t stripped anymore (indents as well as newlines), when there’s no title the title-div is not being generated anymore</li>
<li>1.1: Solved the issue with single-quotes being changed to typographical quotes</li>
</ul>
<h4>Known Issues</h4>
<p>While the plugin is basically XHTML 1.0 Strict compliant there’s just no way of getting the offset-based line-numbering to display without inadequate (ab)use of javascript and css hacks, so be warned that <em>IF you use the line-number offset, your documents will <strong>NOT</strong> validate</em> because of the forbidden <code>start=</code>-attribute for the <code><ol></code>!</p>
<h3>Documentation</h3>
<p>More on the <a href="http://blog.kno.at/tools/highlight-source-pro/" rel="nofollow ugc">Highlight Source Pro Page</a></p>


Highlight Source Pro

Powerful, XHTML-compliant, server-side code highlighting for pretty much all languages

Frontend Debugger vs Highlight Source Pro