Potential caching issue

Mark,
Thanks for the reset access on the dev site. We just played around in there (as you saw).

On the dev site, it's configured to use "Local Storage" for avatars, and thing seem to be working normal there. Are you planning to use S3 storage on the live site? We're investigating how JomSocial supports this, but we currently don't in our plugin. You're the first we've heard of to use this feature, but if you plan to keep it enabled live, we'll do some digging.

Finally, on the dev site, we couldn't get anything to work (JFBConnect related) unless we disabled SEF Advanced. I checked that JFBConnect was supposed to be 'skipped', but it didn't seem to be. Not sure what's happening there either, unfortunately, but hopefully you can test and report back with anything you know about, especially if it's working for you when SEF is enabled.

Thanks!

We didn't touch a thing, actually. We disabled SEF Advanced, and simply tested. On the dev site, JomSocial is configured to store the avatars locally, and that seems to work.

We did remove your Facebook API/Secret keys from JomSocial's Facebook Configuration area. They aren't necessary there, and wanted to prevent any conflicts that they can cause, but I don't think this was the cause for things to start working.

Definitely test and let us know how it goes. Like the new look on the dev site, by the way!

That error simply means that you've been testing too much There's a limit for how many times an application can post to a user's wall in a timeframe, and it's variable depending on the app, number of users, number of posts, etc. For a new app with a lot of posts (especially to a few accounts), it can start to look like spam, and Facebook rejects them. It's not something to worry much about as it clears itself up.

That error also won't be displayed to users if you disable the "Show Facebook Errors on Front End" setting, so while the post won't be made (if you hit that limit) the user's won't see some screwy error.

Hope that helps!

Mark,
I just tested on the dev site with IE8. I'm assuming SEF is enabled (I didn't check), but logging in worked fine for me. After logging in, I always remained on the same page (which I'm assuming is how you have it configured).

So, the obligatory questions...
- Is there a specific page that you log in from and get the 404 error?
- What is the link in the address bar that's giving the 404 error?
- And, of course, does this happen from different FB accounts and/or on different computers?

We'll get ya going, don't worry!