Just realized there’s a tech update we’ve been meaning to post for a few days, but have kept forgetting about.<\/p>\n
We THINK that we’ve figured out a way to solve the problems with HTML code (bold, italics, blockquote formatting) not working consistently in the comments.<\/p>\n
Use SQUARE BRACKETS [ ]
\ninstead of the normal angle brackets < ><\/p>\n
Thus, the code for bold text would be as follows:<\/p>\n
[b] text you want in bold [/b]<\/p>\n
We’ll keep any eye on how this works. Hopefully it will solve the bizarre problem. Feel free to send us links if comments continue to have HTML problems.<\/p>\n
IMPORTANT UPDATE:<\/b>
\nIt seems that while the square brackets work more consistently for formatting (bold, italic, blockquote, and strikethrough…), the angle brackets work best for LINKS (anchors) when posting a URL.<\/b><\/p>\n
(Note that the software does automatically format URLs for you. So if your link is short, you can just enter in the address in your comment, e.g. http:\/\/new.kendallharmon.net\/wp-content\/uploads\/ . I simply pasted in the address there without any code. The software did the formatting.<\/i>)<\/p>\n
However for long links, we prefer if you would add the anchor link coding. Here’s what that looks like:
\n <a href=”http:\/\/www….”>name of the link</a>
\nNote: the quotation marks around the URL address are essential. Without them the code does not work.<\/p>\n
Feel free to use this comment thread for tests. And do keep us posted as to any further examples of problems with HTML in the comments.<\/p>\n
==========<\/p>\n
UPDATE #2:<\/p>\n
This elf thinks she might go insane. Angle brackets seem to work “ok” for short links. But if you’ve got a longer more complex links with spaces or “arguments” (i.e. like a search result for a Bible passage or something), they don’t work.<\/p>\n