Users of
Internet Explorer 6.x
or before should be aware
that this site works best in
Firefox (best choice) or
Internet Explorer 7.x.
Some helpful links:
 |
| IE 7 at Microsoft |
Disclaimers
Site
Anybody else getting this error when trying to sign in through TypeKey?
Can’t locate object method “new” via package “Crypt::DSA” at lib/MT/Util.pm line 1648.
Visitor Isaac emailed me to let me know that he’s received this error. I decided to log out at TypeKey from my TypeKey account, revisit the blog, and try hitting “Sign In.”
Now I’m getting that error. I can’t comment on D5GW anymore.
Things like this make me wish — really really wish — I had never heard of LivingDot. Who knows if it’s a problem with the fact that the commenting script is still on FastCGI? Or is it the upgrade to MT 3.34? I do know that the Managing Director of LivingDot was rather insistent that I should require TypeKey authentications; and I suspected (but could only guess) that the two plugins I used before to filter out spam may have been causing a problem with server load; but now I’ve done it and MT is rather useless for me again. And valued visitors like Isaac — and who knows how many more, who gave up on commenting after one failed attempt — are finding this site rather useless for engaging in conversation about 5GW.
I realize that asking the question is rather silly. If you’re having the problem, you won’t be able to comment on it! Sigh. I had no problem leaving comments before logging out at TypeKey, but now I’m logged in at TypeKey but still can’t leave comments, still get the error.
I’ll update this post as more information becomes available.
UPDATE: Problem appears to be fixed.
UPDATE #2: For additional info related to commenting errors or submitting feedback related to errors while commenting, check out a list of entries tagged “Commenting Errors.”
I do know, as of 3-23-07, that some users of Internet Explorer who sign in successfully through TypeKey may get a Runtime Error on the redirect back to an individual post. My understanding of javascript, and especially how the MT-utilized javascript works, is quite limited; but I’m searching for solutions. Users experiencing this problem should be able to comment still.
Posted by Curtis Gale Weeks on Mar 17, 2007 05:03 AM
0 TrackBacks
Listed below are links to blogs that reference this entry: Commenting Errors.
TrackBack URL for this entry:
http://dreaming5gw.com/cgi-bin/mt/mt-t.cgi/86.
3 Comments
Test comment
Quite possibly, the problem was a missing perl module. We’ll see. I have to say, for decency’s sake, that despite my rant above, I’ve been getting some very friendly, concerned, and timely assistance from LivingDot concerning this matter.
Truth is, I think that the FastCGI-MT conundrum may be a learning curve issue for everyone involved. Our OODA loops aren’t able to cycle fast enough, although we’re trying! But God forbid you should go to the Movable Type Community Forums for help: there is a desert without oases.
The reason that I’m able to comment now is that we’re running the commenting under regular cgi. But FastCGI should prove much better, if the kinks can be worked out. So for a time, any post receiving a comment from someone already able to comment will be rebuilt with the cgi links for commenting, which means everyone should be able to log in through TypeKey on those posts; but older posts still have the .fcgi links and will not work for everyone who wants to comment.
Thanks to Bill at LivingDot for the great support! The problem seems to be fixed; the missing perl module must have been the culprit. Commenting is back on FastCGI.
One note, however, for anyone who might happen (?) to receive a 404 not found error when attempting to sign in through TypeKey: you may need to reload the page or clear your cache. The redirect back to the commenting script from TypeKey should use a link to the commenting script with an .fcgi file extension. If not, then you probably have a cached entry page with the old cgi link on it.