Dave,
I completely understand your concerns about the category hierarchy. I actually already even mentioned that above:
It's flexibly confusing, is the term I think we're going to call it... the biggest issue with EasyBlog or K2 is that the category drop down doesn't show the hierarchy. Something we will be adding, but right now, it's a flat and confusing list. Enjoy!
The EasyBlog update was rushed out due to the issue you found. We're planning a new update for K2 and EasyBlog next month that will display a hierarchy. 2 things to know for now:
1) The update won't change any functionality you configure now. So, doing it now (even if tedious) won't set you back later on.
2) Even though the categories aren't shown in a hierarchy, if you select a parent category in the drop-down, it's sub-categories will inherit the settings you choose. That functionality is there.. so if you pick the upper-most parent, you can set the type for all of your categories. Of course, you may not want an action on them all, but just letting you know.
Failed Submission
More importantly, your action failed. Well, that's no good! First off, in the future, before you submit your action to them, copy your instructions to a doc on your computer or something. If it's rejected, then you can post the instructions to me (to help diagnose) and it will also help when you resubmit since you have to type it all again.
Next, we've had actions denied too. Please know that actions are manually tested by real people. And they have to approve a lot of actions every day. So, if your instructions are just a little off, they're not going to investigate too much.
With that said, here's what I'd recommend doing:
1) Go to your Developer App and "Switch" to the test user you created.
2) Go to your site to /index.php?option=com_jfbconnect&controller=opengraph&task=viewactivity Delete any activity that user may have.
3) Test the action again, and make sure it goes into the user's Activity Log both in JFBConnect and on Facebook.com
4) Though tedious, repeat steps 2 and 3 a few more times to ensure that it really does 'consistently' work.
5) When confident, delete any actions you have (step #2) so the FB test will not have any issues where it doesn't try to post for them since it already has.
Then, re-submit. Be meticulous about where to login, what pages to go to, what to do, etc. Also, I'm not sure if it's necessary, but give the full information about your test user. From your developer app, click on the "Modify" button by your Test User area. From there, you can see the user's info. I'd paste the whole line into the submission dialog, like:
I tested with the following test user:
Name: Mark Amdffacejcgf Seligsteinstein
ID: 100004661350376
Email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Beyond that, no other suggestions other than really test and try again. If you find any gotchas, either in your testing or our documentation, let us know. I'll try to feed a lot of the above back into our documentation as well.
Thanks, and good luck!
Alex