FANDOM


This is the talk page for discussing improvements to the UserTags page.

Replacement filing cabinet Archives
12

Tags Update

These tags should be updated to include the user tag for content moderators. Content Moderators don't have an existing user-identity box, unlike Administrators - User-identity-box-group-sysop - but then Roll-backers don't have an existing user-identity box either, and this script still allows Roll-backers to have the rollback user tag next to their username. Similarly because this script is still outdated, with Discussions Moderators still being tagged as Moderators. I tried to update the user tag name for Discussions Moderators on my wiki, but it broke, so I had to revert back to the user tag saying Moderator. ― C.Syde (talk | contribs) 09:14, August 12, 2016 (UTC)

Did you add "content-moderator" to both, tags and default groups?
window.UserTagsJS = {
	modules: {},
	tags: {
		threadmoderator: { u:'Discussions Moderator' },
		content-moderator: { u: 'Content Moderator' }
	}
};
 
UserTagsJS.modules.mwGroups =  ['bureaucrat', 'chatmoderator', 'threadmoderator', 'rollback', 'content-moderator', 'sysop', 'bannedfromchat'];
 
importArticle({type:'script', article:'u:dev:MediaWiki:UserTags/code.js'});

Could you provide a link to your edit, where changing the default groups and labels (like above) didn't give you the correct result? AmonFatalis@fandom 10:15, August 12, 2016 (UTC)

Yes for the Discussions Moderator identity box, but the change prevented the tag from appearing altogether. So I was forced to undo the changes.
I haven't updated the tags on my wiki to add content moderators, because I don't know how to get it to work. And I've never felt quite the same about editing Java Script pages since they became covered by the review process. ― C.Syde (talk | contribs) 10:31, August 12, 2016 (UTC)
[1] I've integrated the groups you were missing into your script configuration.AmonFatalis@fandom 12:00, August 12, 2016 (UTC)
The only problem is that now the Custom Java Script review module is in a different language. And I don't know why it's like that, or how to fix it. ― C.Syde (talk | contribs) 12:04, August 12, 2016 (UTC)
Known bug. It doesn't change the overall behavior of the module (same colors and layout as before), so you can just wait it out and report it through Special:Contact.AmonFatalis@fandom 12:29, August 12, 2016 (UTC)

Does not work on Special:Following

Hi there,

This script is really nice, but it does not work on Special:Following. In our wiki we use the following two functions to identify a user page and get the username therefrom. If you think it is useful, you can combine it with your script ;)

function isUserpage() {
    return ($.inArray(wgNamespaceNumber,[2,3,1200,500]) !== -1 || (wgCanonicalSpecialPageName && $.inArray(wgCanonicalSpecialPageName,['Contributions','Following']) != -1));
}
 
function getUserByPage() {
    if($.inArray(wgNamespaceNumber,[2,1200,500]) != -1) {
        return /:(.*)/.exec(wgPageName)[1].replace('_',' ');
    }
    else if(wgCanonicalSpecialPageName == 'Contributions') {
        return /\/(.*)/.exec(wgPageName)[1].replace('_',' ');
    }
    else if(wgCanonicalSpecialPageName == 'Following') {
        return wgUserName;
    }
}

Agent Zuri ?ber mich Nachrichtenseite Ank?ndigungen 07:39, August 26, 2016 (UTC)

Disabling Modules

Hey, I’ve noticed that certain modules, like the MediaWiki Groups, are listed as “enabled by default.” Does this imply that they can be disabled? The way I’m structuring my Staff on my Wiki is cascading, so if a Staff member is a Discussions Mod they will also be a Chat Mod & Rollback, & if a Staff member is a Content Mod they will also be a Discussions Mod & a Chat Mod & a Rollback, et cetera. Because of this, they get not only their tag but those below them, which is unnecessary since this is common knowledge on my Wiki. For this reason I was wondering if I could somehow disable the MediaWiki Groups so that I could use only Custom Tags, because I wouldn’t want to have to write whole User Filters for each & every staff member, I’d rather just have the other tags be off so that only the tags I assign to them will show up. Can this be done? How? Are there alternatives? Pls halp :) —Preceding unsigned comment added by Ursuul (talkcontribs) . Please sign your posts with ~~~~!

Faulty implode module

I believe I have correctly followed the installation process. Below is the code relevant to an odd issue I am having with the implode module. It works, I guess, but for some reason, the generated tag instead of saying 'moderator' says '¿moderator?' and the console detects some sort of error. I am aware that the two moderator variants are relatively new usergroups, and there was recently an update that I think properly introduced internal code for the 'content-moderator' group, although I am not sure how this might relate with my issue here. Any help in diagnosing or solving it would be much appreciated. Thanks.

window.UserTagsJS = {
    modules: {},
    tags: {}
};
UserTagsJS.modules.implode = {'moderator': ['content-moderator', 'threadmoderator']};

Hackey5 (talk) 04:37, October 30, 2016 (UTC)

This is due to not having set up the custom 'moderator' tag that you've created via implode module. Check the Core Configuration section in the docs for details on this.
Basically, you'll need to add a line like below to the UserTagsJS.tags object:
moderator: { u: 'display text for the moderator tag here' }
- OneTwoThreeFall (talk) 06:46, October 31, 2016 (UTC)
Ah, the other modules had worked on their own, so I assumed this one would too. Thanks for clarifying! Hackey5 (talk) 17:20, October 31, 2016 (UTC)

Disappearing tags

I inserted the script in importjs and added to the wikia.css and monobook.css according to the page but the "bureaucrat" tag disappeared, while the "autoconfirmed user" and "new editor" tags showed up. Can someone tell me how to choose which tags to be displayed on profiles, please?

Masson Thief (talk) 03:12, November 23, 2016 (UTC)

Recurring Bug

I’ve noticed that certain User-Name gradients, such as this:

a[href$=":Gunpowder2830"],
a[href$="/Gunpowder2830"]{
    color: #9999FF !important
    font-weight: bold !important;
    font size: 100%;
    background: -ms-linear-gradient(left, #FFFFFF 0%, #6699FF 50%, #000033 100%); background: -moz-linear-gradient(left, #FFFFFF 0%, #6699FF 50%, #000033 100%); background: -o-linear-gradient(left, #FF1493 0%, #FF0000 50%, #0A16F9 100%); background: -webkit gradient(linear, left top, right top, color stop(0, #FFFFFF), color-stop(0.5, #6699FF), color-stop(1, #000033)0; background: -webkit-linear-gradient(left, #FFFFFF 0%, #FFFFFF 50%, #000033 100%); background: linear-gradient(To Right, #FFFFFF 0%, #6699FF 50%, #000033 100%);
-webkit-background-clip: text;
-webkit-text-fill-color: transparent;
}

When placed in the Wikia.css page, they conflict with the UserTags JS. I’ve noticed this problem twice, both times it desaturated the colors of the Tags. An example can be see here.

As you can see, the Tier 5 Ship tag, which has a color in the Wikia.css, is completely desaturated for some reason. I have no idea why, but I can only assume that it is either a bug or that something about the gradient conflicts with the a.tag color inherit CSS which gives the tags their colors. Has anyone else had this issue? If so, is there a fix?
~Ursuul 21:04, December 8, 2016 (UTC)

I'm not sure what the problem is, as I don't normally use JavaScript for anything other than scripts. I tend to just use Cascading Style Sheets for changing the designs of wikis. Is there any reason why you're using both CSS and JS for this stuff? I usually tend to find it easier using just one, or the other. ― C.Syde (talk | contribs) 22:00, December 8, 2016 (UTC)
Because, as it states in the Styling/Appearance guide, you use CSS to control the colors of the tag which is made by the JS. Something about the CSS in the gradient I posted is interfering with the CSS that controls the UserTag colors, I just don’t know what it is or why it’s happening.
~Ursuul 22:04, December 8, 2016 (UTC)
That's probably because part of the code you presented is wrong. Instead of a[href$="/Gunpowder2830"] you'll want a[href="/wiki/User:Gunpowder2830"].C.Syde (talk | contribs) 22:09, December 8, 2016 (UTC)
Well, if that is the case, then how is that on this Wikia.css page, those gradients are used without the “User:” part added (or the $ removed) & don’t cause problems? I know that page is a bit of a mess & needs to be simplified, but if you look you can see they’re used without that tag & they still work; it’s just the above gradient that doesn’t work. I know there’s something wrong with it, because when I remove it the problem goes away, & when I re-add it the problem reappears, but I don’t think it’s the “User:” or $ parts. However, I will try it out to see if it works.
~Ursuul 22:30, December 8, 2016 (UTC)
EDIT: Still caused the problem. See how it looks here? It’s like that everywhere now. My main solution is just to not add this gradient.
~Ursuul 22:33, December 8, 2016 (UTC)
Okay, well, I'm not sure if there's anything I can do, since that's all that I can think of that would be causing the problem. I've recoloured all the user tags on the Community Central Wiki, when I used CSS to revert back to the design before it was redesigned to match the Fandom brand change, and I succeeded in recolouring the user tags. So unless this message will be of any use, this problem will be out of my hands. ― C.Syde (talk | contribs) 22:37, December 8, 2016 (UTC)
That’s ok. Thanks for trying. I’m just hoping someone with the right solution will come along, or at least someone who’s experienced this problem before & has some advice.
~Ursuul 22:40, December 8, 2016 (UTC)
Just discovered that the way those username highlights were added to CSS also work. I suspected that they didn't work because I was unfamiliar with those CSS codes, as I hadn't memorised them. But I recently revised some codes in MediaWiki:Wikia.css on a wiki and discovered that they colour the usernames using the same methods that you presented. ― C.Syde (talk | contribs) 02:37, December 9, 2016 (UTC)

Script is Broken

Sometime in the last week the script broke (confirmed on multiple wikis), likely the result of a bad script edit here. DEmersonJMFM 15:42, January 31, 2017 (UTC)

I noticed that too. ― C.Syde (talk | contribs) 22:34, January 31, 2017 (UTC)
So, no one has volunteered to fix it yet?--Luma.dash (talk) 18:42, February 2, 2017 (UTC)
After clearing my cache the script seems to be fixed on my side. -- Cube-shaped garbage can 18:52, February 2, 2017 (UTC)
Clearing cache/purging does nothing for me. DEmersonJMFM 19:19, February 2, 2017 (UTC)
Nothing for me, too. Cannot we ask one of the staff for help?--Luma.dash (talk) 19:42, February 2, 2017 (UTC)

(reset indent)
Could you open your JavaScript console and check which error are you getting? -- Cube-shaped garbage can 19:49, February 2, 2017 (UTC)

It's fixed at my end. I didn't even have to clear my cache. ― C.Syde (talk | contribs) 23:06, February 2, 2017 (UTC)

Uncaught Error: JavaScript parse error: Parse error: Illegal token in file 'w:dev:UserTags/module.i18n.js' on line 293 DEmersonJMFM 03:24, February 3, 2017 (UTC)

I don't get it. The issue seems to be fixed. At least at my end. Are you saying that you're still experiencing issues? ― C.Syde (talk | contribs) 03:34, February 3, 2017 (UTC)
I had the same error before refreshing my cache. That file also doesn't seem to have any parsing errors, I can import it normally.
Weird. Does anybody else have an idea what might be causing the issue? -- Cube-shaped garbage can 06:23, February 3, 2017 (UTC)
The original issue here (a stray non-breaking space at the end of MediaWiki:UserTags/module.i18n.js; caused by an editor bug, I believe) was fixed a few days ago, however it seems the server caches for some wikis still haven't updated (another issue I've noticed a lot recently…). - OneTwoThreeFall talk 07:57, February 3, 2017 (UTC)
The issue is finally resolved for me. DEmersonJMFM 02:50, February 7, 2017 (UTC)

Applying a Background Image/Texture to User Group Tags

I have been attempting to apply a background image/texture to the tags themselves (not the tag container), rather than a solid color. Working in MediaWiki:Wikia.css, I believe I followed each of the steps correctly, but for some reason, my code does not appear to be working. This is the current state of the code:

/* ~~ User Tags  */
.tag.usergroup-founder,
.tag.usergroup-bureaucrat,
.tag.usergroup-sysop,
.tag.usergroup-rollback,
.tag.usergroup-discussionsmoderator,
.tag.usergroup-chatmoderator,
.tag.usergroup-temp,
.tag.usergroup-bot,
.tag.usergroup-inactive,
.tag.usergroup-blocked,
.tag.usergroup-bannedfromchat {
    background-image: url('http://vignette2.wikia.nocookie.net/minecraft/images/7/7d/SignTexture.png');
    color: #000000 !important;
    font-family:'Arial';
    font-weight: 700;
    border: 2px #6b4226 outset;
    box-shadow:0 2px 5px #000000;
}

The border shape, colors, and font of the user rights group tags are all displaying as desired, but the background of the tag itself remains a light-brown color, rather than the defined background image (I assume the color being used is defined elsewhere in our wiki's CSS). Have I messed up the syntax above in some way, or have I missed an essential step? To see an example of what the tags currently look like, click here.
-Sitb (talk) 15:16, February 18, 2017 (UTC)

It's been quite a while since I asked this question, but I thought I should provide the answer I eventually discovered for this, in case anyone else in the future ever comes looking. The final format of the code which has now been functioning nicely on the wiki for over two years is as follows (usergroup tags are defined earlier in the CSS):
.UserProfileMasthead .masthead-info .tag {
    background: url("https://vignette.wikia.nocookie.net/minecraft/images/7/7d/SignTexture.png");
    background-size:cover;
    color: #000000 !important;
    font-family:'Arial';
    font-weight: 800;
    border: 2px #6b4226 outset;
    box-shadow:0 2px 5px #000000;
}

-Sitb (talk) 11:04, March 24, 2019 (UTC)

Bug with NewEditors module

It's been going on for sometime since early this year. The New Editor tag is now be given to all users who haven't edited within the frame specified by the 'days' parameter, irrespective of how many edits they have made when combined with the 'edits' parameter, meaning that the majority of users are now being marked as new editors.

A suggestion I have would be to automatically add tags to certain groups. Like the Custom module, except for groups as well.Raven King (talk) 02:19, April 20, 2017 (UTC)

Not sure if it is the same bug as above, but it gives some users in my wiki this label even if they have made 10 edits and have contributed for more than four days overall.--Luma.dash (talk) 17:41, June 16, 2017 (UTC)

Is it just me?

Is it just me, or user tags don't seem to be working. Instead they seem to be blanking all the user tags from user pages. I'm not sure if it's a bug, or what it is. ― C.Syde (talk | contribs) 08:44, October 31, 2017 (UTC)

It's caused by Wikia's breaking of list=usercontribs API yesterday. Wait for them to fix it. -- Cube-shaped garbage can 09:01, October 31, 2017 (UTC)
Ah. Nice to know what the issue now is, and that it will be fixed. My navigation popups haven't been working properly either as of now, which could very likely be a result of the same bug, since the issues seem very alike. ― C.Syde (talk | contribs) 09:04, October 31, 2017 (UTC)

Issue with Discussion Moderator tag

Not sure why, but I've had an ongoing issue where trying to change the MediaWiki:User-identity-box-group-threadmoderator to anything other than "Moderator" will cause the tag to not show up. I'm pretty sure it's usertags that's causing the issue, and I've never been able to get it to display when I change the tag from "Moderator" to "Discussion Moderator". ― C.Syde (talk | contribs) 00:21, November 16, 2017 (UTC)

Translation

I would like you to translate the tag "NEW EDITOR" into Brazilian Portuguese, which would be "NOVO EDITOR", it is the only tag that missing to translate... Sorry if my English has errors, it's not my native language. --Gustavo64151889 (talk) 01:50, January 25, 2018 (UTC)

Bannedfromchat Not Appearing

I added the bannedfromchat tag from mwGroups, but it never shows on any users who are currently banned. The only way to get it to work is by manually adding it with custom. Is there something wrong with the code?

window.UserTagsJS = {
	modules: {},
	tags: {
		'bannedfromchat': {u:'testing'},
	},
	oasisPlaceBefore: ''
};
UserTagsJS.modules.mwGroups = ['bannedfromchat'];

—|| Grudgeholderr ||— 23:14, April 1, 2018 (UTC)

It's a known bug that's existed for years. It's probably partly due to "banned from chat" not existing as a user-group, though it did used to exist as a user-group several years ago. Not sure why it doesn't work properly anymore. ― C.Syde (talk | contribs) 02:56, April 2, 2018 (UTC)
Thank you. Is there a known way to fix this?—|| Grudgeholderr ||— 04:17, April 2, 2018 (UTC)
That, I do not know. ― C.Syde (talk | contribs) 04:27, April 2, 2018 (UTC)

Order Parameter

When I put the order parameter into existing groups, the tags are unaffected. Am I missing something? This is my code:

window.UserTagsJS = {
    modules: {},
    tags: {
        'rollback':             {order: '-1/0'},
        'bot':                  {order: '-1/0'},
        'founder':              {order: '1'},
        'bureaucrat':           {order: '2'},
        'sysop':                {order: '3'},
        'content-moderator':    {order: '4'},
        'threadmoderator':      {order: '5'},
        'chatmoderator':        {order: '6'},
    },
    oasisPlaceBefore: ''
};
 
UserTagsJS.modules.mwGroups = ['rollback', 'bureaucrat', 'sysop', 'content-moderator', 'threadmoderator', 'chatmoderator', 'bannedfromchat', 'blocked'];

—|| Grudgeholderr ||—16:54, April 6, 2018 (UTC)

Does the order parameter work for anyone else?—|| Grudgeholderr ||— 03:55, September 19, 2018 (UTC)
In your code above the order values are strings, but they need to be numbers. Try using {order: -1/0} (with no quotation marks) rather than {order: '-1/0'}. - OneTwoThreeFall talk 09:49, September 19, 2018 (UTC)
Thanks a lot! It works!—|| Grudgeholderr ||— 05:25, September 20, 2018 (UTC)

Custom Tags Not Working

On my Common.js, the custom tags won't work. See. w:c:playerkiller001s-mcpe-addons:User:PlayerKiller001

You didn’t install the script as shown in the documentation.
UrsuulTalkCMDate3:18 AM Tuesday, June 5, 2018 (UTC)

Replaces ProfileTags

Even though UserTags is not meant to replace ProfileTags, UserTags does. For example, here is how to generate the "Ancient One" tag using UserTags :

window.UserTagsJS = { modules: {}, tags: { ancientone: {'Ancient One'} }

Thus, ProfileTags could be considered obsolete, like UserBadges. —Preceding unsigned comment added by JoeyPknowsalotaboutthat (talkcontribs) . Please sign your posts with ~~~~!

I disagree. ProfileTags is much simpler and there is no JavaScript review system involved. Also, there is should be no reason both scripts are installed on the same community.—|| Grudgeholderr ||— 01:12, June 6, 2018 (UTC)

Can't share UserTags setting

I tried to get another Wiki's setting via ImportJS, but not working. Also, collisions. http://ja.battlefordreamisland.wikia.com/wiki/MediaWiki:ImportJS --*Lac*() 03:08, October 6, 2018 (UTC)

The error is:
Uncaught TypeError: Cannot set property 'isblocked' of undefined
Try submitting the latest version of your UserTags.js and waiting for it to be reviewed, since you removed the code that throws that error. -- Cube-shaped garbage can 03:17, October 6, 2018 (UTC)

JS Reviews

I personally would review UserTags over ProfileTags if it didn't require JS reviews, since it's better. However, because of the JS reviews, when choosing which one to import on my own, I chose ProfileTags because it's easier (doesn't require JS reviews). Is there a way that the code could be updated so that it doesn't require JS reviews like ProfileTags? If so, could that please be done? THX! -ThePokegeek5000 19:41, November 5, 2018 (UTC)

Basically, could someone update the script so that configuration options can be drawn from a MediaWiki page, similar to DiscordIntegrator? You'd need to make sure it only does this if a variable = true, since right now it is configured via JS pages. Patrik 20:38, November 5, 2018 (UTC)

Council tag

With window.UserTagsMergeMWGroups set to true (and maybe without it set?) the council tag does not show up unless UserTags' debug mode is enabled. Could that please be fixed, so I don't have to force-enable debug mode just to see the council usertag? --Sharkie 04:37, January 8, 2019 (UTC)

I've been looking at UserTags' source to know more about the situation and possibly inform whoever wants to provide a solution some more insight into it, and it has taken a toll on my brain. But here goes: this is due to core.js defining in the UserTags.OasisTagsModule object a _blacklist property that lists all usergroups that will be ignored by the script, which does some gobbling up with the usergroups returned by mwGroups.js to filter the blacklist depending on whether there is a mw page for it. That's why there can be vstf and staff in the list and those still display, because MediaWiki:Group-staff-member and MediaWiki:Group-vstf-member do exist, but MediaWiki:Group-council-member doesn't. A possible solution could be just scrapping council from the blacklist, or always concatenating council to the config in mwGroups.js, though I think there should be some sort of peer review before publishing any changes. -D 05:59, January 8, 2019 (UTC)
if the script works in the debug mode, then it's more likely cache issue. i can check it for u, if u will provide some links. Fngplg (talk) 06:20, January 8, 2019 (UTC)
Its not cache. --Sharkie 06:31, January 8, 2019 (UTC)
without links, it will be hard to help u Fngplg (talk) 06:37, January 8, 2019 (UTC)
https://steven-universe.wikia.com/wiki/User:Ursuul (for example) --Sharkie 06:39, January 8, 2019 (UTC)
should be fixed now. intermodule communications in the script is rly hard to follow to sometimes. Fngplg (talk) 07:36, January 8, 2019 (UTC)
Yep, that fixed it, thanks~ --Sharkie 07:41, January 8, 2019 (UTC)

Problem with the above

As you can see at w:c:diepio:User:TheGoldenPatrik1, the Councilor tag is now showing out of order, when previously the tag would follow the UserTagsStrategy. If the order could be corrected, that’d be most appreciated.
UrsuulTalkCMDate5:58 PM Tuesday, January 8, 2019 (UTC)

vanguards were not blacklisted (allowed to reposition and other abusive actions). fixed. probably Fngplg (talk) 19:26, January 8, 2019 (UTC)
Thank you.
UrsuulTalkCMDate7:48 PM Tuesday, January 8, 2019 (UTC)

Other tags disappear

I'm an admin over on the Shovel Knight Wiki and I'm attempting to use this code to change the background color of custom tags on user profiles. I added the import code to ImportJS and added the following code to the CSS:

a.tag {
    color: inherit;
}
 
.tag.usergroup-bureaucrat {
	background-color: #E300DC !important;
	color: black !important;
}
.tag.usergroup-sysop {
        background-color: #4CCBFD !important;
        color: black !important;
}
.tag.usergroup-content-moderator {
	background-color: #FD4C00 !important;
	color: black !important;
}

However, the colors did take effect, but it only shows one tag per user. For instance, my profile is supposed to display the "Enchanter" (bureaucrat) and "The Order" (sysop) tags, but only the bureaucrat tag shows. However, the sysop tag appears for the other wiki admins (without bureaucrat rights). I'm curious to know if the script is bugged, if I missed something, or if this is part of the script to reduce redundancy. If it is meant to reduce redundancy, is there a way to show both sysop and bureaucrat tags appear? Any help would be great, thanks! NinjaFatGuy (talk) 20:54, December 2, 2019 (UTC)

you have bureaucrat tag, so it is not needed to show other ones. if you want to show all groups, you have to configure the "mwgroup" module. something like
window.UserTagsJS = {
    modules: {
        mwGroups: ['bannedfromchat', 'blocked', 'bot', 'bureaucrat', 'chatmoderator', 'checkuser', 'content-moderator', 'council', 'helper', 'rollback', 'staff', 'sysop', 'threadmoderator', 'vanguard', 'vstf', 'global-discussions-moderator', 'content-volunteer']
    }
};

you can read the documentation for details.Fngplg (talk) 21:56, December 2, 2019 (UTC)

Hook request

Hi,

If it's possible to request additions to the script, I'd like to ask if someone could add a hook to the script that fires when its tags load. The reason why I ask this is because that way, UserTags would become compatible with scripts like MastheadGender (Where it has already been requested on the talk page) and UserAccountAge, which it currently isn't because UserTags removes the tags these scripts add.

It'd be really cool if someone could add said hook to the script. Thanks! Wither 14:23, March 1, 2020 (UTC)

this will not work: hook works when script1 loads script2, and script2 fires the hook to show that script2 is ready. scripts above doesn't load usertags, they doesn't even know whether usertags will be running. so if you want to use other incompatible tagging scripts, you have to add support to these scripts: usertags already is flexible enough to use 3rd-party tags. Fngplg (talk) 14:54, March 1, 2020 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.

Fandom may earn an affiliate commission on sales made from links on this page.

Stream the best stories.

Fandom may earn an affiliate commission on sales made from links on this page.

Get Disney+