WPBOOK fatal error on publish

1 view
Skip to first unread message

BandonRandon

unread,
Jan 15, 2010, 2:32:12 AM1/15/10
to ScholarPress Dev
I've been doing some work on 1.5 but with the 1.4.2 everytime i
publish a page or post i get this error:
"Fatal error: Uncaught exception 'FacebookRestClientException' with
message 'Session key invalid or no longer valid' in /wp-content/
plugins/wpbook/client/facebookapi_php5_restlib.php:2618 Stack trace:
#0 /wp-content/plugins/wpbook/wpbook.php(712): FacebookRestClient-
>call_method('facebook.Fbml.s...', Array)
#1 /wp-includes/plugin.php(339): wp_update_profile_boxes(Object
(stdClass))
#2 /wp-includes/post.php(2122): do_action()
#3 wp-includes/post.php(1806): wp_transition_post_status
('wp_update_profi...', Array)
#4 wp-includes/post.php(1866): wp_insert_post()
#5 wp-admin/includes/post.php(192): wp_update_post()
#6 wp-admin/page.php(146): edit_post()
#7 {main} thrown in wp-content/plugins/wpbook/client/
facebookapi_php5_restlib.php on line 2618"

I edited the message to not include any server data but i think you
get the point. Any ideas?

John Eckman

unread,
Jan 15, 2010, 9:31:31 AM1/15/10
to scholarp...@googlegroups.com
This is exactly the problem that's driving my interest in dropping PHP4 support.

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/

BandonRandon

unread,
Jan 17, 2010, 3:09:03 PM1/17/10
to ScholarPress Dev
If i understand this right, on publish you are running the function to
update the profile box which is causing this error. I'm perfectly fine
with dropping php4 support and fixing this issue that way.

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/

Reply all
Reply to author
Forward
0 new messages