zaecus

Since you want free, no ads, and don’t want to learn PHP or mySQL, there’s most likely nothing available.
Given your list of expectations, I don’t think there’s a bloghost of any kind anywhere that will do what you want without dropping one of those at a minimum.

Nope, nevermind.
Found the problem and updated the Wiki page.
The line should have been:
$content = str_replace(array('<![CDATA[',']]>'),'',html_entity_decode( addslashes( trim($content[1]))));
If that doesn’t work, I don’t know what to tell you.
(For the curious without sharp eyes, the difference is one close parenthesis, just like this one –>)

Wow, you’re right it does say .xml. I never even noticed that.
I just edited the same .php file that you did, but since I was the last person to edit that page based on my experience, lemme see what you got before I go changing it again.
The line you changed should have been changed to:
$content = str_replace(array('<![CDATA[',']]>'),'',html_entity_decode( addslashes( trim($content[1])));
which was my edit.
The original recommended change did not work for me, but this one did. If it’s what you tried and wouldn’t work, try this:
$content = str_replace(array('<![CDATA[',']]>'),'',html_entity_decode( trim($content[1]));
That’s what it was before I changed it, and that’s the line that did not work for me.
Please, let me know if it works for you. If it does, I’ll edit the Wiki page to indicate both as possible fixes and that the file to be edited is wp-admin/import-livejournal.php.
If the HTML still doesn’t go in the way you want, go ahead and share that, too. I doubt I’ll know enough to figure out what’s wrong (or even what information you need to give to figure out what’s wrong), but someone else might.

Nevermind. Taking a very close look at it, it looks like ljArchive’s XML exporter doesn’t identify the comments well enough to really be able to properly import them.
Willing to be wrong on that, but as it stands, not willing to mess with it or hound anyone else to mess with it. My entrance into the world of real blogs will just continue to be slow.

Yeah, basically. ??

Nobody else? Darn.
Glancing over the import files, I know it can be done. Hrm…

I’ve got over a thousand entries, and that looks like a lot of work. I’m almost certain to mess something up, and the exported comments are actually threaded, which is something I’d like to keep.
Although, I realize that I’ll need a plugin for them to actually show up threaded.
It’ll wind up being a lot of work no matter how I do it, so I’ll keep this in mind and hope others have something to say that might reduce the amount of work some.

Looks like you did it right–if the xml file you have is actually named that. Make absolutley sure you haven’t missed a dash or an underscore or some other punctuation in the file name.
If you haven’t, and the livejournal xml files are in the wp-admin directory, then it should import that months entries.
Um… wait a second… Make sure you’re putting the file name in the right place:
<?php
define('FILE NAME HERE');
// Example:
// define('XMLFILE', '/home/example/public_html/rss.xml');
// or if it's in the same directory as import-rss.php
// define('XMLFILE', 'rss.xml');
The other places are just comments to give you an example, and they’re copied from the rss importing file.
If you’ve done all that, I’m afraid I don’t know what’s wrong.

In that event, invalid or deliberately broken email address, I’d assume the person has deliberately opted out of being notified when someone responds to their comment.
Thinking about it, it might be best if the original commentor is reminded that they will not be notified of responses unless they leave a valid email address (which won’t be seen by anyone/harvested by robots as standard now, right?).
If the don’t leave a valid email address, then it should fail harmlessly. If it works that you can notify more than one person that you are ‘responding’ to their comment, then one bad email address shouldn’t kill the process for the rest.
In any case, the comment should be left as normal.
Thank you for the interest. ??

podz,
I’m not sure about the original poster, but I want something that fits this description and works regardless of whether or not someone has subscribed to comments.
Basically, I want something that allows me to specifically notify one or more commentors–possibly by checking their name, possibly by replying to their comment (if it works as an adjunct to threaded comments, which is fine)–that someone has replied to their comment and provide them with a link back to that post and its comments.
Don’t bother telling me to put it on the wishlist. I already had, but when I went to take a look again, I found it’s been deleted by someone who either agrees with you about it being the same as subscribing to comments or believes it’s not worth bothering with.
If somebody with enough pull to keep it from being deleted wants to put it on the wishlist, I’d be grateful.

The link you cited above is not permanent, actually.
Aside from the things you have little control over, such as the
https://, it assumes that there will always be support, specifically browser support, for pages with a .php extension.
If php becomes obsolete in five or ten years (or tomorrow, who knows these days) and you’re still running the blog, you might find yourself transferring all of those old .php pages into a new language, hopefully by use of a nifty program that will do it for you. In the process, however, all the links like the one you gave get broken.
The permalinks, not being based on the file’s extension or location,
except by archive values based on date, post number, and/or subject, which will hopefully not change, will probably be valid for a lot longer. (I do think permanent is a bit optimistic….) But the idea is to make them as independent of, and resistant to, technological change as possible.
In addition, index.php?p=63 doesn’t mean anything to a person looking at it, but “/2004/04/03/264” or “/2004/04/03/man-bites-dog” does. If they’re looking at a link that’s talking about a specific event, they can tell just by looking at the URL how out-of-date the information may be or how close to the actual event. They can also, by removing /03/264 easily see all of the posts for April of 2004.