Both in the Global hook and when viewing the full shoutbox or archive. The smile shows in the post editor but doesn't in the resulting shout.
Typing the code or clicking the smilie.
Since the board upgrade the db only shows the code for the smilie not the full path.
Can you PM me the details for your site (Admin account user/password and FTP) so I can diagnose this? This is very strange, I didn't touch anything in recent versions that should have had any effect on this.
No, there isn't. I mean, you can restrict MEMBERS group by post number, that's what I did. On my board, only who has 150 posts (or more) can USE the shoutbox... At the same time, users on MEMBERS group with 0, 1, 2 or 100 posts can VIEW the global hook, but can't use. I don't think it makes sense a group view the shoutbox but can't use it 'cause the user doesn't have the number of posts required. Admins should have the option to choose: USE AND VIEW shoutbox.
It's just a new IF, as I posted above! 10 seconds of your work can accomplish it on a new version.
I don't think you're understanding how the setup works currently. There are currently two boolean group options, can view the shoutbox, and can use the shoutbox. There's the additional option for allowing it to be used only when you reach a certain post threshold. With your suggestion, even if the option that said they could view the shoutbox was set to Yes, they couldn't view it if they didn't have enough posts. That's not what the post count setting is there for; it's there to indicate how many posts they need before they can use it. It's perfectly valid to have a setup where people of a given group can view the shoutbox but not post in it.
I think what you're actually asking for is a new setting for the number of posts they need before they can view the shoutbox. If that's really what you need, then I suggest you setup group permissions that would promote people after a certain group to a new group that does have permission to view the shoutbox. Otherwise, if you still want the new setting, it's definitely not just a quick 10 second fix like what you're suggesting. If that is what you want, you can make that suggestion in the Tracker.