Help - Search - Members - Calendar
Full Version: Openid Login For Lj Gives Error. Mt 4.12
Movable Type Community Forum > Using Movable Type > Commenting System
Symian
Hiya!

I just updated with the mandatory upgrade to 4.12 and now the openid/LiveJournal is giving me this:

---
unclosed token at line 1869, column 8, byte 100990: <foaf:member_name>~ Dawna ~</foaf:member_name> <foaf:tagLine>Its sellinbees!</foaf:tagLine> <foaf =======^ at /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/XML/Parser.pm line 187
---

This was me trying to login to make a reply comment as a test. Dawna is an LJ member on my LJ friends list.

I have the basic installation, nothing else added, no modifications, intital layout, everything. Fresh install basically. The LJ login was working the last time I tried it (a few weeks before this upgrade).

Any clues anyone?

Su-
That looks to me like a complaint about the information being returned. Have you tried logging in someplace else with your LJ account? Did it work there?

Next, if it is a software error, it's coming from a Perl module on your server, not one included with MT, so maybe do a quick check with your host to see if they upgraded/changed something?
Symian
QUOTE (Su- @ Jun 27 2008, 05:06 AM) *
That looks to me like a complaint about the information being returned. Have you tried logging in someplace else with your LJ account? Did it work there?

Next, if it is a software error, it's coming from a Perl module on your server, not one included with MT, so maybe do a quick check with your host to see if they upgraded/changed something?


You must be right, Su. I tried logging into another MT site and got this:

000
no element found at line 1849, column 70, byte 100091: <foaf:member_name>bluesgirly</foaf:member_name> <foaf:tagLine>Write On</foaf:tagLine> <foaf:image>http://p-userpic.livejournal.com/57446750/12107274 =====================================================================^ at C:/Perl/lib/XML/Parser.pm line 187
---

I guess LJ is mucking it up.
Symian
Ah! It is actually MT causing this issue because it does not handle FOAF feeds greater than 100 KB in size.

People will a lot of friends on their friends list might well get errored out because each journal's data feeds include a FOAF file ("Friend-of-a-Friend"). By default, everyone on the Friends list is placed in the FOAF "knows" section. This is pushed back at MT when trying to login with an LJ ID.

The fix for it is to create (in LJ) a custom friends group called "FOAF-knows" and add only your own journal to it. This fixes the login issue with MT. At least it did for me. smile.gif
Su-
QUOTE (Symian @ Jul 6 2008, 06:28 PM) *
Ah! It is actually MT causing this issue because it does not handle FOAF feeds greater than 100 KB in size.

Says what? (I've just never seen anything about this before.) Seems like an odd limitation. Is it documented somewhere?
Symian
QUOTE (Su- @ Jul 6 2008, 11:25 PM) *
QUOTE (Symian @ Jul 6 2008, 06:28 PM) *
Ah! It is actually MT causing this issue because it does not handle FOAF feeds greater than 100 KB in size.

Says what? (I've just never seen anything about this before.) Seems like an odd limitation. Is it documented somewhere?


Not that I am aware of. I don't really know if MT is limited to 100K or more. I am just going by what I was instructed by LJ support. Once I created the little foaf-group thingee my login issues disappeared, so I have to assume that MT can't handle a foaf feed over a certain amount.

*shrugs*

Su-
QUOTE (Symian @ Jul 8 2008, 08:49 AM) *
Not that I am aware of. I don't really know if MT is limited to 100K or more. I am just going by what I was instructed by LJ support. Once I created the little foaf-group thingee my login issues disappeared, so I have to assume that MT can't handle a foaf feed over a certain amount.

Weird. I'll file a bug on it. Might at least get us some corroboration, I guess.
Su-
For what it's worth, the 100k limit has been confirmed by the MT team and is going to be in release notes for 4.2. Looks like the current plan is to make the error happen more gracefully, though, and not to increase the cap.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.