Just call me the Blogfather

12 thoughts on “Just call me the Blogfather”

1. But Dave, you always provide me with such great things to comment on. 😛

   P.S. Thanks for your help in this whole thing. 😀

   Reply

2. …Now If I can just get the code from you on the Most recent comments thing.

   Reply

3. See? Nobody ever wants the vanilla installation. They immediately want to customize it … 🙂

   No problem. Sorry it took so long for me to get it done.

   Reply

4. Np…you have a vacation comming up and more work type things then I know what to do with. 🙂

   Reply

5. Ok, wackiness. First of all, yay! Secondly, I seem to be having a problem commenting on BD’s blog. I’m trying to sign in, but it keeps putting me in a neverending loop of “Please allow us to send you email address/please sign in”. What up wit dat?

   Reply

6. Wierd, It seems to be an IE thing since it is doing this on the IE at work, but it is working fine on Firefox last night.

   I will blame it on Microsoft.

   Reply

7. Well, that’s always the right answer …

   Let me poke at it.

   Reply

8. Huh. Looks like it may be in part due to a drug interaction with the authentication and the BD domain being on the HK domain. I’ll have to get back to it.

   Reply

9. Ah. Well, on the up side, I was right about the multiple domain thing being part of this. On the down side … bleah.

   You are using multiple domains.

   If your Movable Type installation is on one domain, but your weblog is on another, this can cause problems with Internet Explorer, due to that browser’s designation of certain cookies as “leashed”.

   “Leashed” cookies are new to Internet Explorer 6. They’re cookies that Internet Explorer prevents from being used later, by a third-party site. So when the TypeKey commenter cookie is set (for the domain where your Movable Type installation is located), IE won’t allow that cookie to be used on your weblog, because it thinks it is a third-party cookie.

   In this case, anyone who wants to comment on your site will have to make changes to their privacy settings in Internet Explorer, by following these steps (substituting your actual installation domain name for domainname.com):

   1. Go to Tools > Internet Options, then select the Privacy tab.
   2. In the Settings area of the tab, click Sites.
   3. In the Address of website field, type domainname.com and click Allow.
   4. Click OK at the bottom of that dialogue box.
   5. Click OK on the Privacy tab.

   This change should now permit the sign in cookie to be set correctly.

   I do not expect folks who are visiting boulderdude.com to have to tweak their IE privacy settings to allow cookies to be read from hill-kleerup.org. Bleah.

   We can, however, make some changes in the comment authentication/acceptance processes. I’ll e-mail you.

   Reply

10. That answer can be found here.

    Reply

11. Toldja it was Microsoft. ;P

    Reply

12. Hey, you’re right!

    The basic alternatives (per the e-mail I sent):

    1. Status quo. Only folks with Firefox can post comments. A nicely Darwinian solution, but …

    2. Still immediately post authenticated comments, but allow non-authenticated ones through (but require them to be moderated). A bit more work on your part, and a delay in comments showing up, but the least worst solution, I think.

    3. Allow all comments through. Comment spam city and a great way to get our blogs locked down by HM. Not a viable option.

    So my recommendation is #2.

    Reply