Sorry for the delayed response. Open Graph (as mentioned a few times) still isn't an area of expertise for us, so some things do take some research. It's also not a developed feature, so it gets lower priority for now. Anyways...
Tadas,
You've found a bug! Currently, our jfbc.login.login_custom() function is not properly requesting extended permissions. You can easily fix this by editing the /components/com_jfbconnect/includes/jfbconnect.js file. Around line 26 you'll see the following code:
Update that to:
That should properly request all of the permissions on login.
Ivan,
As far as I know, the code you used above from that post is still correct. There are certain actions that are 'core' functionality for Facebook, like scores in Games. Other custom actions just for your app should operate the same way. That message that you get when you try to publish an action is definitely confusing. We think it means that you basically need to test the action before you publish it. So:
* You create the action and noun objects in the Open Graph area of your Application
* You then implement it on your site somewhere and publish it to your Timeline. You can check your history in your Activity Log on your profile
* Once it's there, then you can submit it to Facebook for approval.
I think Facebook just wants to make sure you plan to use the custom actions, since they have to manually approve everything. By making you post it to your own timeline first, it helps them verify your intent. I'm not sure if you can only post to an Admin's timeline while an action is unpublished, but that sounds reasonable.
Hope that all helps!
Alex