I just bumped into an issue that rendered a whole section of Flashmagazine.com useless. Anywhere there was a code snippet showing array access, the automatic pmCode turned:

into this:

Needless to say - every tutorial using a for-loop and a variable named “i” to iterate over an array displayed half the page in italics and the code broke… It is quite common to use the letter “i”, though it’s often considered bad practice as well. The point is really that it’s no good that this is enabled by default for absolutely any Weblog field. A global on/off that defaults to “off” would be wise, though a default to “on” is probably preferred not to break existing installs.

Robin pointed me to a workaround in this thread, but a permanent fix would be better.

J

Not saying that your FR is not a valid one, but have you tried to put your snippets inside of [ code ] tags?

Yep. Using a <code> tag made no difference.

J

Not < code >, as in HTML, but [ code ], as in pmCode.

Seems to work.

Right, but I don’t want to use pmCode or BB-code? I didn’t even know that EE supported it before I ran into this issue. I prefer to use either LG TinyMCE on Rich fields or plain fields with no formatting. Why should I have to even think about this (if you see my point)?

I understand that there is some heritage to pmCode and that it’s a good feature, but not make it ossible to turn it off? EE is used on many sites related to programming and odds are they won’t know that their code is mangled until somebody points it out.

J

I see your point, and I only suggested it as a temporary workaround until your FR gets implemented.

Ah. Right. Sorry, I misunderstood. Just deleting the line in “core.typography.php” actually makes it easier for me since I then don’t need to type in tags.

Yes, but it’s a hack which we discourage as much as possible. But, of course, whatever works for you )