Script needs review and more testing

I think this script was deployed a bit too quickly.

1. It is sending out console.log output, for no good reason. This should really be tested out in a sandbox.
2. It isn't always retrieving the latest revision due to the caching and use of the wrong API.
3. You might want to use versions to make it easier to discern what is working or not, and also so that people don't get puzzled by wrong documentation relating to a previous version.

A suggestion to solve problem 2 is an api call that does retrieve the latest version :

mw.loader.using('mediawiki.api', function () {
            (new mw.Api())
                .get({
                titles: "MediaWiki:ProfileTags",
"prop":"revisions",
"rvprop":"content",
                indexpageids: ''
            }).done(function (data) {
var id = data.query.pageids[0]
                console.log(data.query.pages[id].revisions[0]["*"])
            });
        });

—Preceding unsigned comment added by Dessamator (talk • contribs) 11:46, 16 January 2016‎ (UTC). Please sign your posts with ~~~~!

1. The console output is just debugging code I forgot to remove. It was tested using the built in test mode, as every script should be now.
2. It's true use of index.php rather than api.php can add caching which end-user might not expect. However, api.php also contains caching, so you're example doesn't solve the percieved issue. I don't think a small amount of caching (which I think is client side) is a major issue.
3. For the time being, I'm inclined to add features and associated documentation in tandem. If there's confusion it's trivial to explain what's happened, and chances are it'd be resolved within 24 hours anyway. It's fairly easy to get an un-cached version of the script if needs be, but exposing that sort of information to the target end user is excessive. —Preceding unsigned comment added by Cqm (talk • contribs) 17:10, 16 January 2016‎ (UTC). Please sign your posts with ~~~~!

Good points.

2. A good idea would be to add some notification in the profile pages that the script is loaded. People tend to be baffled about whether it is working or not, for example if for whatever reason there's a typo in the names or a script error they may never realize it. Some sort of interface cue at least for administrators would be helpful. Dessamator (talk) 12:34, January 17, 2016 (UTC)

Discussing a possible improvement - Allowing customization of standard tags

Many wikis want to customize the text of the existing tags, rather than adding custom tags. Since the corresponding system messages are not editable by local admins anymore, and the UserTags script is not compatible with UCP, I want to discuss the option to add that ability to the ProfileTags script.

My idea is to expand the existing allowed syntax with rows starting with exclamation marks (similar to the exisiting !nohide switch). For example:

!Sysop | Admin
!Rollback | Time-turner

Would like to get feedback.

Nam 23:52, 22 March 2021 (UTC)

Might be better to put this on the Talk:ProfileTags page instead, but wouldn't it be easier to make UserTags work rather than making ProfileTags into UserTags? Especially sine if I remember correctly, ProfileTags is supposed to be a simple version of UserTags without a lot of the bells and whistles that UserTags has. --Sophie ♦ 00:26, 23 March 2021 (UTC)

True, I didn't notice I have put it in the wrong place.

UserTags is a huge multi-module script, not my level at all, and no one else has touched it all this time. Personally, I think the improvement I'm suggesting still fits into the "simple" category and matches a very common need.

Nam 00:58, 23 March 2021 (UTC)

Hm maybe, tho I don't know if it's a good idea (eg, someone renaming the staff tag), plus you can just change the system messages, but that needs WR (if you have one) or staff to make the edit. --Sophie ♦ 01:06, 23 March 2021 (UTC)

Also, Doru attempted to make UserTags work, so there has been atleast an attempt, but he kinda dropped it due to issues, so I don't know it if works. --Sophie ♦ 01:13, 23 March 2021 (UTC)