Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted January 13, 201015 yr Reference: http://community.invisionpower.com/topic/302077-username-parsing-hook/page__view__findpost__p__1898326 I want to get as many opinions on this matter as possible, because it makes your board look much more colorful and attractive. Should IPS implement a more extensive workaround into parsing usernames using the group prefix/suffic values? So names that appear in the shoutbox may appear elsewhere. If yes/no, should it be optional? So that users may turn it on and off at will, making it a more customizable feature? :)
January 13, 201015 yr You know I want it. The amount of edits required to do it currently is extensive and painful. Its theres an on/off button, then theres no harm :P My vote.
January 15, 201015 yr Are you talking about doing the group name formatting in more places? I got confused by this part:So names that appear in the shoutbox may appear elsewhere. The names that appear in the Shoutbox are just the display names, they do appear elsewhere, everywhere someone's name is mentioned.
January 17, 201015 yr Ah, but 3.1 has been deliberately written to make it possible to do this - the updated hook system finally allows overwriting that terrible cludge that gets put in the DB for last poster values and all that.
January 18, 201015 yr Author Yeah, but it would be simpler if there was a simple setting for this... @Michael, I am referring to formatting the display names across the board with their groups associated prefix and suffix, making the board more overall attractive. Looking at a skin, and it's just constant one color (links)... gets kind of bleh after a while.
January 20, 201015 yr Community Expert Actually there is already a setting to disable the name formatting globally but the problem is that the name formatting is only applied in a few areas and no one uses it :P
January 21, 201015 yr Author It can't be that hard with all the new settings being added / re-routed.. :(
Archived
This topic is now archived and is closed to further replies.