XF 1.5 Verified Badge next to the nickname. [Help]

[rafass]

Hello. I want to put a badge next to the nickname. Something like verified accounts in Twitter or FB:



I've been playing around in message_user_info with the conditional:

<xen:if is="!{$isQuickReply} AND {xen:helper ismemberof, $user, 5}">
<div class="userInfoDot Tooltip" title="{xen:phrase verified}" data-offsetx="-11"></div>
</xen:if>

Where the group of "Verified Members" is the group #5

That's working fine:



But:
1. How can I show the horizontal Tooltip like in member page? (but without that effect):



2. How can I keep the badge always next to the username and avoid this jump when the username is long?:


--
Appreciate some help with this.

 

[Snog]

@Snog: can be easily made available by extending XenForo_DataWriter_Alert and let it store the user group ids. That'll require no additional queries.

That's true, but why modify a table when you don't have to? Extending the function in the model to include the user groups makes more sense to me. But, that's just me.

 

[Lukas W.]

There's already forced redundancy by storing the username in the alert database, so the logical step for me would be to extend the existing forced redundancy to save queries.

 

[Snog]

There's already forced redundancy by storing the username in the alert database, so the logical step for me would be to extend the existing forced redundancy to save queries.

Tomatoes, Tomatos

Either one saves the query.

 

[Lukas W.]

The XenForo_Model_Alert doesn't allow to join any tables, so unless you want to overwrite the function, I couldn't think of any way to merge the usergroups in without an additional query.

 

[Snog]

The XenForo_Model_Alert doesn't allow to join any tables, so unless you want to overwrite the function, I couldn't think of any way to merge the usergroups in without an additional query.

Correct. I believe you would have to replace the _getAlertsFromSource function.

 

[Lukas W.]

Which could lead to potential incompatibilities with other addons that extend this function in whatever way. I'd rather extend a table than risk incompatibilities.

 

[Snog]

I don't think you'd run into that. But it is a good argument for your position.

 

[Snog]

Along your lines of thinking, that's why I often wonder why join options aren't available in all models?

I posted about it in nodes a while back..
Implement Prepare Node Join Options

I should have included all models, but I was narrow minded at the time and focused on only nodes.

 

[Milano]

The way he was determining if the icon should be shown is by user group membership.

So? I believe most of the times, the user array in the helperUserNameHtml will contains the user_group_id & secondary_group_ids unless you remove them from the array.

And there are tons of resources out there. Are you willing to extend and add the template modifications for them.

 

[Snog]

So? I believe most of the times, the user array in the helperUserNameHtml will contains the user_group_id & secondary_group_ids unless you remove them from the array.

You are correct. But they are not in the alert system, so not available to the helper. The array I showed is the $user array sent by the alert templates.

Array ( [user_id] => 11 [username] => MTest [gender] => male [gravatar] => [avatar_date] => 1405082762 )

So your options are

1) Add a query for each alert
2) Extend the model
3) Extend the datawriter

2 or 3 would be the logical choices. Which you prefer is up to you.

 

[Milano]

I see, try this way, not sure if it would be the best way.

<?php

class ....Model_Alert extends XFCP_...._Model_Alert
{
    protected $alertFromSource = false;

    protected function _getAlertsFromSource($userId, $fetchMode, array $fetchOptions = array())
    {
        $this->alertFromSource = true;

        return parent::_getAlertsFromSource($userId, $fetchMode, $fetchOptions);
    }

    public function limitQueryResults($query, $limit, $offset = 0)
    {
        if ($this->alertFromSource)
        {
            $query = str_replace('user.gravatar,', 'user.gravatar, user.user_group_id, user.secondary_group_ids, ', $query);
        }

        return parent::limitQueryResults($query, $limit, $offset);
    }

 

[Snog]

Oh, I'm not the one doing the add-on. I was just pointing out that some areas don't have the required information to use a user group condition and it would require some php coding.

 

[MrCleverTrevor]

It would be nice if someone made this into a resource,

 

[Dadparvar]

Easily possible by this add-on:
https://xenforo.com/community/resources/verified-badge.5062/

 

[MrCleverTrevor]

Easily possible by this add-on:
https://xenforo.com/community/resources/verified-badge.5062/

Thanks for the referral but i dont want to pay for a unmaintain resource

 

[Paul B]

One addon with this customization is coming.
All Rights Reserved.

It seems abusively a paid addon of this customization has been released by someone else and without ask for permission. not sure if that's fine.
This is very easy to achieve with few template modifications (depends where you want to show the badge) and CSS.
really it doesn't need a specific addon, but if someone want to distribute an addon, should request permission and release it absolutely free.

You're not the first person to think of this idea, and won't be the last.

You can't own something like this and prevent others from creating their own versions of it.

 

[Dadparvar]

That's not mine.
Its on you to choose whether to use it or not. I'm just a user of that add-on, and just gave you its link to see there is such add-on.
If you don't want to pay, just don't do that.

 

[MrCleverTrevor]

I would love to see this go into a free or maintained resource

 

[iGee]

Was there ever a solution to this?