Re: New menu arrangement: Community - Staff - Personal
Reply #25 –
Ok, Plan #4756291 Subsection 2 Appendix 4329z..............................
Can we maybe agree to handle the personal stuffz title as follows?
My Account is perhaps (perhaps) more neutral in tone and "professional" (meaning boring) than "My Stuff", even though I am sure 99% of professionals would be fine with the latter. It's also clearly labelling by function.
So, if someone has profile permissions but not PM permissions, just give them a "My Account" title with profile stuffz in the droppy.
If they have PM permissions but not profile permissions, give them a "My Messages" title with PM stuffz in the droppy.
If they have both PM and profile permissions, give them a "My Account" title with both PM and profile stuff in the droppy (PM first, as it will probably be used more often) and...
if they also have new PM's, change the title to "My Messages", along with the usual numeric indicator. This would just be an extra bit of eye-catching when they have new PM's.
Array code works like this:
'pm' => array(
'title' => $context['allow_pm'] && (!$context['allow_edit_profile'] || $context['user']['unread_messages'] > 0) ? $txt['pm_short'] : 'My Account',
'href' => $context['allow_pm'] ? $scripturl . '?action=pm' : $scripturl . '?action=profile',
'show' => $context['allow_pm'] || $context['allow_edit_profile'],
'sub_buttons' => array(
Yeah they kinda cute. I like them. I wouldn't bother with doing them on every button, in part because there aren't enough good utf8 thingies for every button*, but for those two buttons I think they're probably a good idea.
*There are a lot of thingies, but most of them woudn't be suitable.