testing comments 2
testing testing
posted by Kim Mackenzie / Kim Hubbeling @ 3:56 PM
9 comments
Sunday, November 21, 2004
About Me
- Name: Kim Mackenzie / Kim Hubbeling
- Location: San Antonio, TX
Musician and graphic designer with roots in Hawaii, now living and working in south Texas.
Blogging for self-amusement, so the the posting frequency is spotty and the range of topics is broad: music, design, travel, gardening, taking dark and blurry snapshots, or whatever else strikes my fancy.
Many weekends, you'll find me performing. Schedule below.
Contact
Via email
Via voicemail / text:
210-338-0083
9 Comments:
Here's a problem - in order for Blogger's comments to work, it has to use the feature where it makes a separate web page for every post. We turned that feature off, because we were getting errors that the filenames were too long when we published (it takes the filenames from the title of the entry).
I have another test blog that I wasn't even able to turn comments on for, because I had not been using title fields, so it was trying to make the filename out of the whole blog entry.
This sucks.
Can't edit a comment after I make it. Can only trash. I don't like that.
And I don't like how the comments visually run together into the blog entry. It's confusing.
Waaaaaaah! :)
yes, the previous one was better. input of comments to this new feature doesn't show up right away. plus navigational is a bit confusing. i guess the only good thing is the type is bigger. good for my old eyes. also it has a preview feature. (was that there before??)
my 2 cents worth.
Ouch. That's really not good. I guess we made the right decision when we talked about this before. Smart us. I guess we need to make Haloscan work for us as best we can.
We ought to let Blogger know what's better about Haloscan.
That's a good idea (letting blogger know).
1) not having to use Blogger's separate web page for each post "feature," which is incredibly buggy.
2) Comments opening in a popup window.
3) Being able to edit comments.
Those are three biggies for me. But the first one is a deal breaker, because we had so many problems with that "feature" in the past.
Haloscan (our current comment solution) doesn't have a preview.
But it does have a button to edit after you post, which (to me) is better. I never notice typos until after I've posted sopmething, even if I look at a preview.
Post a Comment
<< Home