plnelson

I Got It Working !!

. . .
. . . but I don’t know how.

I was experimenting around to see if SH-E was interacting with other plugins on my blog so I disabled Preserve Code Formatting. When I did that SyntaxHighlighter Evolved displayed the XML correctly! But I couldn’t leave Preserve Code Formatting disabled because it would break my whole blog – I use it everywhere. So I reactivated it expecting that SH-E would be broken again but it seems to still be working.

I’ve made a blog entry (with an artificial date so it would be buried in the past) to test/monitor the situation. It recounts the whole sorry tale. Here

This is the result you got from editing post in the Visual Editor. The Visual Editor of WordPress will convert all those special characters to HTML entities.

Nope. I did not edit the post in the Visual editor.

I only edit my posts in the HTML editor. I have to because I’m using the Preserve Code Formatting plugin, as I mentioned in the OP, and as you note, the Visual Editor plays havoc with stuff like that.

I really appreciate everyone’s attempts to guess here, but, please let’s stop speculating! My original post was about the sourcecode shortcode described in https://en.support.wordpress.com/code/posting-source-code/. Does anyone actually know what it takes to get that to work properly? (and also why the link in the credit section doesn’t point to what it says it points to)? Which plugin does it really need?

If I use the shortcode syntax [sourcecode language="xml"] with SyntaxHighlighterEvolved activated, I get exactly the same output I had in the screenshot above:

https://blog.nelsondev.net/images/SH_Evolved_1.jpg

I’m still confused by why the link in the credits points to SytaxHighlighterEvolved instead of SyntaxHighlighter. But I noticed that Viper007Bond’s first name is Alex, so is it the same author?

Anyway, does anyone actually know what’s going on with the sourcecode shortcode or are we all just speculating?

. . . also, the link in the credit doesn’t go to Alex Gorbatchev’s Syntax Highlighter; it goes to SyntaxHighlighterEvolved by someone named “Viper007Bond”. And I already have that installed! That was the one I posted the screenshot of, above.

So getting back to my original question: what are the steps needed to get the sourcecode shortcode to work?

ie. it specifically mentions which plugin those shortcodes are based upon, so that should have been your starting point.

I don’t want to implement my own shortcode, i.e., I don’t want to reinvent what they’ve already done; I just want to use the shortcodes described in the link. Also, everything is based on Alex’s code – I’ve already installed SyntaxHighligher-Evolved and SyntaxHighlighterPlus which are also based on it, and they include it in their own installs.

Anyway, I though the comment you quoted was just giving credit to Alex – are you saying that if I install Alex’s plugin the the shortcodes will just automagically work?

For self hosted installs, check the credits section on that page on WordPress.com

Thanks, but my question is really about the shortcodes mentioned in https://en.support.wordpress.com/code/posting-source-code/.

Take a look at some of the posts in my site. I use the plugin SyntaxHighlighter Evolved.

I tried it; it worked great for Java but mangled my XML. Here’s a screenshot: https://blog.nelsondev.net/images/SH_Evolved_1.jpg

So I posted a question to their forum, https://www.viper007bond.com/wordpress-plugins/syntaxhighlighter/ I included some sample XML which I placed between [code]...[/code]‘s as it suggested. And it mangled the display of that XML, too! Not only that, it failed in a different way than in the screenshot, and it failed differently in Firefox and IE.

Anyway, my original question was about the shortcodes mentioned in https://en.support.wordpress.com/code/posting-source-code/. How do I get that to work?

BTW, I’m using WP 3.0.1

Thanks!!!

My question is really about the style.css for that theme in general, rather than about a particular page. Here’s a page I have that uses it . . .
https://blog.nelsondev.net/

Do all of these perform the same function as Preserve Code Formatting – i.e., allowing the blogger to drop in code such as HTML or XML and having WordPress not try to interpret it? How can they do that and still have embedded line numbers and/or colors?

In other words: are there any disadvantages to using those instead of Preserve Code Formatting? Or am I not getting what they do?

I tried some different themes and the problem went away. So it seems to be a bug in the iNove theme I’m using.

It’s a PITA because I generally tweak my themes with my own colors and images, so now I gotta select a new theme and tweak it, but at least I know the bug is in the theme, not WP.

See, THIS is why this forum needs a “Preview” feature. I wasn’t sure how to include <pre> in the Title, so I figured, to be safe, I would embed it in backticks. But all we get to see is the backticks .

All you have to do is wrap your code in the appropriate pre tags with this plugin:

<pre lang=”PHP” ><?php get_footer(); ?>

What plug in? get_footer()’s not a plug in.

There seem to be several plug ins out there that claim to handle
<pre> and singlequotes correctly. What’s the best one?

The visual editor is meant for non-coders, beginners, and others who just don’t ever want to mess with any code.

You’re saying the ENTIRE blog entry has to be done in HTML, not just the parts I want to display as HTML?! WYSIWYG editors are NOT just for non-coders – they are for writers who want to see what the reader will see before publishing it. Besides being a software engineer I’m also a writer and good writing requires seeing how something lays on the page before publishing it to the world.

Is all blogging software this primitive or is this something unique to WordPress?

Here’s what I’d recommend:

https://www.ads-software.com/extend/plugins/wp-syntax/

But am I correct in interpreting that we’d still have to hand-edit the HTML of our blog postings? (to add <pre> ... </pre> ) I can’t believe in 2009 we don’t have a WYSIWYG blog tool – hand-editing HTML is so last century! (“Sherman, set the Wayback Machine for 1993 and while you’re at it, put “Achy Breaky Heart” on the 8-track . . . “)

Also, does it survive across edits Publish – Edit – Publish – Edit ?

<i>They can show up as though they are comments, yes.</i>

OK, I’ll try disabling pingbacks and trackbacks (thanks!!), but meanwhile, is there a way to tell when something in the Comments queue didn’t really come is as a comment?