Getting huge error when used with varnish/pantheon/mercury... anyone else? Its a huge pop up error after clicking on the submit

There are a couple other similar issues in the queue -- it's not a bug in FBSS. The problem is that you have other modules on the page that are causing JavaScript errors. FBSS silently re-loads the page when a status is submitted, and if there are any JavaScript errors on the page, you will get that error. You should be able to use a tool like Firebug to trace the source of the JS error causing this problem.

Read my first comment. This is not a bug in FBSS. It is up to you to figure out which other module is causing a JS error on your page.

I've had the same issue. It is another module which is causing the issue. You just have to figure out which module is causing the problem and disable it. I am also using pantheon/apc/memcache/varnish, and with ahah and can get Facebook-style status updates working without a popup error

antiNSA, did you manage to find what's causing this?
I have the same issue...

It doesn't seem to be another module causing it.
Just ran a clean install of Mercury/pantheon/varnish and only enabled the facebook-like statuses module and when I submit a status I get a popup that says: an error occurred /facebook_status/js and than all the html (code) of the page.

I think it has something to do with memcache or varnish. Cause it works once (I assume when the page isn't cached) and then if you try to update the status again you get the popup.

Any advice on how to fix that? Maybe something in the varnish vcl file?

It is due to a JavaScript error and it is not FBSS's fault. That's as much insight as I have.

Any idea what's causing this javascript error?
Do you have experience setting up this module to work with Pressflow/Varnish/Memcache?

No and no, although the fact that Pressflow, Varnish, and Memcache are all basically caching tools might be a hint.

Look, I'm just going to keep marking this issue "won't fix" if you keep changing it back, unless you can demonstrate that a change to FBSS's code will fix this problem without reducing functionality for other users. Your problem seems to be that your particular configuration of Pressflow, Varnish, and Memcache is causing JavaScript errors. Your problem is not that there is a bug in FBSS.

Which is why I changed it from bug report to support request.

I don't think that there's a "bug" in FBSS, and I'm not sure that there's necessarily something "wrong" with my configuration. Nothing is wrong with pressflow, varnich, memcache, mercury or pantheon either. There is definitely a compatibility issue though! It seems like a few people have this problem and I can't seem to find a proper solution.

You know your module inside and out and I was hoping that even though NOTHING is wrong with it, you might still be able and willing to help resolve this issue.

If you wanna help, I've now found that the issue resolves when I delete this bit of code from my settings.php file:

$conf['memcache_servers'] = array(
         '127.0.0.1:11211' => 'default',
         '127.0.0.1:11212' => 'menu',
         '127.0.0.1:11213' => 'filter',
         '127.0.0.1:11214' => 'form',
         '127.0.0.1:11215' => 'block',
         '127.0.0.1:11216' => 'update',
         '127.0.0.1:11217' => 'views',
         '127.0.0.1:11218' => 'content',
         '127.0.0.1:11219' => 'apachesolr',
       );
$conf['memcache_bins'] = array(
          'cache'        => 'default',
          'cache_menu'   => 'menu',
          'cache_filter' => 'filter',
          'cache_form'   => 'form',
          'cache_block'  => 'block',
          'cache_update' => 'update',
          'cache_views'  => 'views',
          'cache_views_data'  => 'views',
          'cache_content'  => 'content',
          'cache_apachesolr'  => 'apachesolr',
       );

But I'm not sure what to do, cause I need this for memcache to work properly.

Anyway, if you don't wanna help, mark this as "won't fix" and I won't bother you again.
Cheers

Anyway, if you don't wanna help, mark this as "won't fix" and I won't bother you again.

It's not that I don't want to help. I want very much to help, I'm just not able to do so. I do know a lot about FBSS, but this is not an FBSS issue, and I know very little about Varnish and Memcache. You will have much more luck asking the question "Varnish and Memcache are causing a JS error" in a setting where people know something about Varnish and Memcache than asking me the question "Varnish and Memcache are causing a JS error, and FBSS doesn't like JS errors."

gorgo - it might help: make sure your default.vcl tells varnish to not cache /ahah/ paths, or the paths this module uses to do its magic.