Options
No more "greater than / less than" symbols allowed?

I have made a couple of edits this morning, coffee has not kicked in yet, trying to use the "greater than / less than" symbols to create a break in the sentences only to receive an error message (ERROR: One of the values in the url has not passed validation.
Error Code: 113). I took out the code and the breaks were there...SURPRISE!
To make this coin related; I sent in a few for variety attribution and a few for crossover like this 1847 1C N1, I love the repunched date on ALL four digits!;

Error Code: 113). I took out the code and the breaks were there...SURPRISE!
To make this coin related; I sent in a few for variety attribution and a few for crossover like this 1847 1C N1, I love the repunched date on ALL four digits!;


oih82w8 = Oh I Hate To Wait _defectus patientia_aka...Dr. Defecto - Curator of RMO's
BST transactions: dbldie55, jayPem, 78saen, UltraHighRelief, nibanny, liefgold, FallGuy, lkeigwin, mbogoman, Sandman70gt, keets, joeykoins, ianrussell (@GC), EagleEye, ThePennyLady, GRANDAM, Ilikecolor, Gluggo, okiedude, Voyageur, LJenkins11, fastfreddie, ms70, pursuitofliberty, ZoidMeister,Coin Finder, GotTheBug, edwardjulio, Coinnmore, Nickpatton, Namvet69,...
BST transactions: dbldie55, jayPem, 78saen, UltraHighRelief, nibanny, liefgold, FallGuy, lkeigwin, mbogoman, Sandman70gt, keets, joeykoins, ianrussell (@GC), EagleEye, ThePennyLady, GRANDAM, Ilikecolor, Gluggo, okiedude, Voyageur, LJenkins11, fastfreddie, ms70, pursuitofliberty, ZoidMeister,Coin Finder, GotTheBug, edwardjulio, Coinnmore, Nickpatton, Namvet69,...
0
Comments
I'm trying this response without line breaks as well, I think the gt/lt symbols are still being interpreted as HTML markup.
Sean Reynolds
EDITED TO ADD: line break functionality still not working here
"Keep in mind that most of what passes as numismatic information is no more than tested opinion at best, and marketing blather at worst. However, I try to choose my words carefully, since I know that you guys are always watching." - Joe O'Connor
BST transactions: dbldie55, jayPem, 78saen, UltraHighRelief, nibanny, liefgold, FallGuy, lkeigwin, mbogoman, Sandman70gt, keets, joeykoins, ianrussell (@GC), EagleEye, ThePennyLady, GRANDAM, Ilikecolor, Gluggo, okiedude, Voyageur, LJenkins11, fastfreddie, ms70, pursuitofliberty, ZoidMeister,Coin Finder, GotTheBug, edwardjulio, Coinnmore, Nickpatton, Namvet69,...
My YouTube Channel
I just hit the enter key twice on my keyboard and that seems to do it for me.
Am I misunderstanding something?
Looking for Top Pop Mercury Dime Varieties & High Grade Mercury Dime Toners.
I had the line break problem for a short time after the software change, and then suddenly I didn't. It sounds like maybe you've crossed that mysterious threshold.
And yes, that means those symbols probably won't work for you anymore, since the boards will think they are HTML.
It also means that if you are using the Quote feature and quoting someone who is still having the line break problem and has those symbols in their post, you'll have to edit the symbols out in order to be able to quote them. This has happened to me a couple of times.
I must say I'm now blissfully free of most of the major issues with the boards that plagued me before and after the change. And mostly satisfied. I'm not crazy about the new PM format, but I'll live with it. And there are a number of new features that I do like. So all in all, my opinion of the new boards is faintly positive but tinged with a little sadness that all my old images hosted on CU are now dead, and all my old poll threads no longer have poll information attached to them.
But we move on. I hope that everyone else's glitches get taken care of, because I know all too well how frustrating they can be.
under the wysiwyg, symbols work no probs.
under coding standards, partials symbols are seen as errors, as technically they are. having said that, there are a few partial symbols i like to use under wysiwyg but i must concede.
this shouldnt kick off an error warning but just mess up the post a bit, like normal coding standards.
if it were important that errors in coding be notified of immediately, the warning would be a godsend but this is not the case here. (as much anyway)
.
Cheers, RickO