So there's one bug I'm still experiencing which I presume results from some sort of form validation issue. I'm not very aware of the underlying causes for these types of issues so let it be known that I could be very wrong. This may not be FBSMP specific and it might not be Facebook Status specific. Anyway, here are the steps to produce the bug:
Leave the Facebook Status form open on a web browser window for a while. Then try to submit a status with an attachment. The result is no status having being submitted and the following error report (not a very helpful one either):
An error occurred.
/fbsmp/js
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<script src='http://platform.twitter.com/anywhere.js?id=HbBmCyYjuwgosNeeNLyqYg&v=1' type='text/javascript'></script>
<script type="text/javascript">
twttr.anywhere(function(twitter) {
twitter.hovercards();
});
</script>
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/fasttoggle/fasttoggle.css?x" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/activity/activity_comments/activity_comments.css?x" />
... (and it just goes on like this)
This is an intermittent issue so I'm setting this to a minor status. My hunch is that if this is a simply form validation issue then at least it would be great if we could create some sort of hook that would reload the page, or provide a user friendly error report (like "please try again after reloading the page"), if form validation is not met. Users are never happy with crazy looking error reports. Of course, like I said, I could be way off on diagnosing this.
Best,
Thomas
Comments
Comment #1
pribeh commentedWhops - forgot to wrap that html in < . code . >.
Comment #2
publicmind commentedI have not yet closed this issue, because I really want to see this fixed but unfortunately as by its nature it is intermittent and I am unable to reproduce it. Can anyone help?
Regards,
Comment #3
pribeh commentedHi publicmind, I'm going to get a programmer to look at this issue and I will report back this week.
Comment #4
publicmind commentedAny updates, pribeh?
Comment #5
publicmind commentedAny updates, pribeh?
Comment #6
pribeh commentedNo, sorry publicmind. Our in-house programmer can't even figure it out. I'd be fine if we set this to won't fix until more people start to experience this with the 2.x branch.
Comment #7
publicmind commentedThanks,
Comment #8
jmrivero commentedI have the same problem. Looking at the code found that this error is generated by drupal_validate_form_new, and a issue for ctools that may be related here http://drupal.org/node/957894
This error happends right after a user logs in and try to post a link, if the user navigates to another page and try again there is no error.
Here is the code that generates the error, the session after login may be the cause thought.