Update to this post about fixing the comments. I figured out what I had done wrong. I put the blogitemnumber in quotes in the template (Right after the “javascript:aspcomments”) after I had already left a comment. The comment got stuck in the database with the wrong blogid, since the javascript rounded it 17 digits and…
Andy tells me that he got aspcomments working with the new, longer blogids that the new version of blogger is going to be kicking out. I haven’t tried it yet on the test blog, but probably will tonight. Hmm here’s a pretty good hint that I should learn more about programming myself, huh? I knew…
Convinced that maybe Access just plain isn’t going to support 18 digit blogid’s, I did try a couple of new commenting systems with the new blogger version while I ate my lunch. CGIcomments completely didn’t work. Again, probably it’s handling the blog_id as a number and choking on 18 digits. xcomments worked, sort of. I…
I had a sudden thought this morning in the shower about the comments. The sudden realization that I had put the link to the comments BlogItemNumber in quotes so it would look for a string instead of a number but I hadn’t put the quotes around the second part of the comments code where that…
See Andy’s post here. More details on aspcomments handling of 18 digit blog id’s. I’m going to be messing with the comments for a few, switching the field to text from long integer, you might not want to leave any comments for the moment. 🙂 Update 1: Andy’s permalinks don’t seem to be working, look…
See Phil’s post here. If you use comments in Blogger that incorporate javascript, you might want to be aware of this little change that needs to be made to your commenting system when your blog gets switched over to the new version of blogger. I did it with my copy of aspcomments on this blog…