Version 1.1 of this plugin is out of date. See here for the newest version.
Here's a new version of my OpenID commenting plugin. This brings up to the current spec with Net::OpenID::Consumer 0.12. This one's also all blung out for Movable Type 3.2, with a per-blog preference for displaying the LiveJournal user icon for LiveJournal users. (See here for technical details on the OpenID functionality.)
To install:
- Download the plugin.
- Unzip the archive.
- Copy the
openid-comment/pluginsdirectory to your MT directory. - Copy the
openid-comment/mt-staticdirectory over your static assets directory. (For default MT 3.2 installs, copy it into the MT directory.) - On each blog where you want to use OpenID commenting, edit your templates to add
<MTOpenIDSignOnThunk>just above your commenting form.
That should be it. Get it here.
Comments
comment
Thanks so much for fixing this!
Here LJ will work right now, but OpenID won’t. On my site neither will.
For LJ I get: “OpenID signons are not available on this blog”
I’m probably forgetting something stupid.
As for OpenID, I get (both on mine and here) a message from my browser: “could not connect to the server “openid.imperialviolet.org”.”
That might be a temporary problem.
Thanks a ton for your work involving this plugin though. I can’t wait to get it working again. I guess I’ll keep messing around for a solution. You can try it out on one of my entries.
comment
It’s working!
I had to go to the plugin settings, turn off OpenID sign in, and turn it back on again! I think this might be a bug in the whole MT system… Have been having weird stuff like that happen a lot lately with the 3.2 betas.
I then got the old “Undefined subroutine &Digest::MD5::md5_hex called at signon.cgi line 103” problem again, which I solved using my unconventional method (getting rid of it) from last time (link).
Thanks a ton!
One more question: What’s the Digest::MD5::md5_hex needed for?
comment
Yay, glad it’s working now! Looks to me like openid.imperialviolet.org is down, yeah; the web server there is actively refusing connections. Is that the only OpenID server you tried to use?
The plugin settings thing is strange. The plugin says the default for both settings is on, so I’m not sure why it would fail until you toggled them. I thought I had seen it work, but maybe I didn’t really test before setting the settings.
Oops, I forgot about Digest::MD5! I’ll have to fix that.
The md5_hex call is just to make up a good random number to use for the session cookie value. It’s hashing an actual random number, the current time, and some numbers from the current state of the server to make that field. My understanding is that makes it a bit more secure than just using a random number, but it can fall back to a random number, failing that.
comment
does not work with dynamic publishing, is that a known bug?
comment
Yup, that’s a known problem. Thanks for the note.
comment
Hi Mark — I noticed that both your openID and LJ thunks create a div with id=”openid”, which is probably not ideal.
That said, I’m trying to get this working on my site, but the livejournal login, though it succeeds, still lists whatever the contents of the un-authenticated “Name” field as the commenter name (both on the published page and within MT) when it is posted. Do you know what the problem might be?
comment
Oops, yeah, that ID should definitely change for the LiveJournal thunk. Thanks!
Several people have reported the same problem with logins. Currently I think it might be related to how the core trick to allow OpenID where MT expects TypeKey names works and limitations imposed by MT when using MySQL and Postgres databases. (I’m using SQLite, which doesn’t enforce field size limits the same way as MySQL and Postgres do.) I’m looking into it as soon as I can.
comment
This is really odd, because someone else has since been able to post a comment on my blog using a LiveJournal ID, but I still can’t, from either IE or firefox on my machine. I wonder if it’s cookie-related? (My “remember me” checkbox seems to be constantly checked)
comment
Well, it’s not cookies, because I’ve forcibly cleared mine out. Field length might make sense, since the poster who did manage to comment has a six-character name and mine is “neon_epiphany” — much longer.
Anyways, thanks so much for this plugin!
comment
Yeah, the bug is fully reproducible as an issue with field length. OpenID Comments 1.2 only works correctly with SQLite databases (which is what I’m using here, which is why I didn’t see it).