vBulletin Mods

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. :)

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

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

Yes, mh_unm_changelimit should be there twice.. :)

You can run the following 2 queries:

Block Disabled:      (Update License Status)
Suspended or Unlicensed Members Cannot View Code.

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.

If you use SMALLINT(3), it will not increase the column size. ;)
SMALLINT defaults to 5 positions.

PS I never understand why people keep quoting numeric default values.

So if someone changes their member name, does it change the member name all all previous posts? Plus I can only assume that the old username will be in quoted posts...correct?

It will be changed everywhere, except quoted posts.
It uses the standard routines in vB to change the name, the same that is used when changing from AdminCP. Everything that would be changed when doing it from the AdminCP, is also changed with this hack.

It merely builds on top of the standard functions by giving Users and moderators also a place to change the name, and to add logging/reporting to it.

Nice update there...

feature request:

having this History of Usernames to be searchable as "registered users" so if someone wants to register with a username that is in this list, he will not be able to, and will be required to contact the admin if this is an error...

the situation come often when someone register, and not remember his password or complete username, and instead of asking for a new access he register twice... that came at least 3 times here this year only... ;)

something like "this username was once used by a user on this site. if you really need this username, please contact the admins. "... and this can be joined with the Ajax Alert...

Well that would be something completly different......and for 3 times a year?

But i have been thinking about not allowing a change if a name have been used before.

For example a popular guy on the board, decide to change his name, and a newbee immediate change his name the the popular guys old name.

A lot of people would get confused. Or maybe just no reuse of names for 3 month.

that's the same situation i guess, just not the same start.. lol

;)

Just installed this on my testboard and I really like it.
Thanks

Just one question:
What's wrong with semi-colons?

They are not allowed i guess. But that has nothing to do with my hack, it is vB itself blocking it.

Oh, ok, thanks for clearing me up.

I've got another problem:
When I allow a usergroup to change names, they can't login into the ModCP anymore.
They click on the "Change name" link, enter username and password in the login window, but instead of logging them in, the login window is displayed again.

Am I doing anything wrong?

edit: I just noticed that the user needs to mod at least one forum to make it work.
Is there a way to change this?