I think the patient has been stabilized
02/27/2010
Comments seem to be working now in a somewhat consistent if unsatisfactory way. In Firefox, if you come to the main blog page, you see "2 comments" or whatever at the end of a post. If you click on that, you get taken to a page with only that post, and, again, "2 comments". Click on that, and you get the comments box.
It works the same in Internet Explorer, except: I find that when I go the main page the number of comments doesn't appear. Reloading the page (F5) makes it appear. But even if the number isn't there, clicking on the word "comments" seems to work as above.
The Recent Comments feature is not going to be there for a while, and when it reappears it will probably be because I've moved the blog somewhere else. I had left the old Haloscan code in the blog template. The JS-Kit folks had said it would continue to work properly. As we know, it did not. After a frustrating go-round with JS-Kit support, I finally replaced it with the new Echo code. That involved discovering and correcting some things in their examples that were just plain wrong and would never work. But Echo has no Recent Comments feature as such. Instead, it has a big ugly navigation tool which includes a Comments list along with some stuff I don't want. The tool is customizable to some degree, and I could probably make it less obtrusive and perhaps remove the unwanted items, but I really don't much want to bother.
My goal now is to escape Echo for all future commenting while preserving the old comments. The good news is that I think this will be possible: it turns out Echo comments can be accessed from locations other than the one where they were generated.
If you see my Links list empty, it's because I had to start from scratch with a fresh copy of the template (that's also why it was green for a while today). I'll put them back soon.
Update 2/28/10: we now have a recent comments list, although it's rather unattractive, and I've put the links back, so I think I'm in a position to put the commenting problem aside for now and focus on the question of where to move the blog itself. Officially I have until late March to make the move, but it's going to take a while for me to evaluate the options and make the decision.
It's funny how the absence of a recent comments list made the blog seem somehow crippled--a sort of flying-blind feeling. Just shows how important the comments are.
It works the same in Internet Explorer, except: I find that when I go the main page the number of comments doesn't appear. Reloading the page (F5) makes it appear. But even if the number isn't there, clicking on the word "comments" seems to work as above.
The Recent Comments feature is not going to be there for a while, and when it reappears it will probably be because I've moved the blog somewhere else. I had left the old Haloscan code in the blog template. The JS-Kit folks had said it would continue to work properly. As we know, it did not. After a frustrating go-round with JS-Kit support, I finally replaced it with the new Echo code. That involved discovering and correcting some things in their examples that were just plain wrong and would never work. But Echo has no Recent Comments feature as such. Instead, it has a big ugly navigation tool which includes a Comments list along with some stuff I don't want. The tool is customizable to some degree, and I could probably make it less obtrusive and perhaps remove the unwanted items, but I really don't much want to bother.
My goal now is to escape Echo for all future commenting while preserving the old comments. The good news is that I think this will be possible: it turns out Echo comments can be accessed from locations other than the one where they were generated.
If you see my Links list empty, it's because I had to start from scratch with a fresh copy of the template (that's also why it was green for a while today). I'll put them back soon.
Update 2/28/10: we now have a recent comments list, although it's rather unattractive, and I've put the links back, so I think I'm in a position to put the commenting problem aside for now and focus on the question of where to move the blog itself. Officially I have until late March to make the move, but it's going to take a while for me to evaluate the options and make the decision.
It's funny how the absence of a recent comments list made the blog seem somehow crippled--a sort of flying-blind feeling. Just shows how important the comments are.
Comments