Username Management - Control who can change Usernames plus history

<font size="4">Username Management - Version 1.04</font>

Hack: Username Management
Version: v1.04
Author: MarcoH64

Description
With this modification installed you can let your members change their own username, or let Staff members change the usernames of other members.

Also a history of previously used names for a member is kept.

Features
- Users can change their own username controlled by Usergroup Permissions. If needed a time limit between changes can be set.
- Staff can change the Username of other members. This is again controlled by Usergroup Permissions.
- Previously used Usernames of a member can be viewed in posts, by hoovering over their Username. This is also controlled by Usergroup settings
- Full searchable history of Username changes in AdminCP
- Fully Phrased
- Optimized for server performance
- Documented API for addon developers

Changelog
23-12-2005 v1.04
- Changed master="true" to false in cpnav file.
- Fixed bug where history was generated when running Update User Names from Update Counters

v1.03
- Changed the size of the 'mh_unm_changelimit' & 'mh_unm_changelimit' columns in the usergroup table
from TINYINT to SMALLINT to support values > 255

23-11-2005 v1.02 (maintenance release)
- Improved internal caching routines
- Added internal routine for retrieving the latest changed usernames
- Coders: Parameter value change for parameter '$overridelimit' in 'mh_unm_fetch_username_history'
This release is needed if you want to use some fo the new Addon's!!
Known issues: Coder documentation not complete, no examples are given, although the 2 released addon's can be used as examples.

22-11-2005 v1.01
- Fixed bug messing up Private Messages (thanks mini2)
- Fixed bug in install routine that would create a wrong tablename if using table prefixes
- Changed the internal caching routines
- Added more parameters to mh_unm_fetch_username_history for more flexibility for Addon coders
- Added extended information mode
- Created first version of the Coders documentation
Known issues: No example code for an Addon Plugin yet.

22-11-2005 v1.00
Initial release

Upgrades
Upload all files from 'upload' folder.
Install the new product file, choosing an overwrite install.

Notes
Copyright ©2005 MarcoH64
This Modification may not be redistributed in whole or significant part or changed without prior agreement of author.
Please don't forget to click Install.
If you like this work and would like to support the author, donations are always welcome at Paypal: Marcoh64 AT gmail.com

[Oblivion Knight]

Would adding value="$bbuserinfo[username]" to the Change Username fields have any adverse effect?

[Marco van Herwaarden]

Originally Posted by Oblivion Knight

Would adding value="$bbuserinfo[username]" to the Change Username fields have any adverse effect?

How, what, where, why?

[Oblivion Knight]

Well to make the "Change Username" fields in the User CP appear more like the "Change Email Address" fields above it, I added the current username in the text boxes. I've not looked at the code or checked whether to see this hack will ignore updating the Username if it remains the same as the current one.

I guess I should stop being so lazy and actually look..

[Marco van Herwaarden]

It will ignore it if not changed (i think). Since you will most likely not reuse your name, i thought it was useless to prefill with current.

PS Yes take a look, some parts (especially some of the caching in the functions) i am pretty satisfied with.

[WNxWakko]

Why is the max days 255 days? I wanted to only allow members to change once a year max, but seems I cant, I put in 365 and save, but when i go back in, its set ast 255. ?????????

[Marco van Herwaarden]

Hmmm that looks like a design error. To allow higher values, change the 'mh_unm_changelimit' column of the usergroup table in your database from TINYINT to SMALLINT. Will update this in the next release.

This may be useful for my forum..hm...I will test it out none-the-less.

[WNxWakko]

Originally Posted by MarcoH64

Hmmm that looks like a design error. To allow higher values, change the 'mh_unm_changelimit' column of the usergroup table in your database from TINYINT to SMALLINT. Will update this in the next release.

I have no clue how to do that. Is there a query I can just run from the Admincp?

[Oblivion Knight]

[sql]ALTER TABLE usergroup CHANGE mh_unm_changelimit mh_unm_changelimit SMALLINT(3) UNSIGNED NOT NULL DEFAULT '30'[/sql]Yes, [high]mh_unm_changelimit[/high] should be there twice..

[Marco van Herwaarden]

You can run the following 2 queries:
[sql]ALTER TABLE usergroup CHANGE COLUMN mh_unm_changelimit mh_unm_changelimit SMALLINT UNSIGNED DEFAULT 30 NOT NULL;
ALTER TABLE usergroup CHANGE COLUMN mh_unm_viewhistorylimit mh_unm_viewhistorylimit SMALLINT UNSIGNED DEFAULT 1 NOT NULL;[/sql]
If you are using a table prefix, then add it in front of the tablename (ie. prefix_usergroup).

If you run the queries from the AdminCP, you must run 1 line at a time. If you are using something like phpMyAdmin, you can just copy&paste both lines in 1 go.