I edited the message to not include any server data but i think you
get the point. Any ideas?
Because we're supporting PHP4 we can't wrap calls to the Facebook API in try/catch and catch these exceptions.
This call occurs when you write a new post or page and publish it - it's trying to update the profile boxes.
You can disable it - in wpbook.php, look at the function call on lines 674-677 - if you comment that out, WPBook will stop trying to update profile boxes.
Why it fails I can't tell you - happens on the FB side. The error - "Session key invalid or no longer valid" - is wrong, since the call I'm making (Facebook.Fbml.setRefHandle) doesn't even require a session key.
Once we move to requiring PHP5, WPBook will have to do something with this error when it occurs:
a) Ignore it
b) Queue it to try again later, maybe under wp-cron?
> --
> You received this message because you are subscribed to the Google Groups "ScholarPress Dev" group.
> To post to this group, send email to scholarp...@googlegroups.com.
> To unsubscribe from this group, send email to scholarpress-d...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/scholarpress-dev?hl=en.
>
>
----------------------------------------
John Eckman
eckma...@gmail.com
http://www.johneckman.com/
I would like to ask if there is a way to not update the profile box on
publish but instead let the user set a variable (most-likely using wp-
cron) and update it on that schedule. To me it's just annoying to see
the error where if i wasn't logged in when a cron was run i wouldn't
have to worry about seeing it.
> eckman.j...@gmail.comhttp://www.johneckman.com/