Difference between revisions of "Extensions:User Username Changes"

From Lorekeeper Wiki
Jump to navigation Jump to search
(Created page with "{{subst:Extension Page}}")
Tag: 2017 source edit
 
m (Update Contact Information)
Tag: 2017 source edit
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Extensioninfobox|title=the extension's name|desc=A short description|auth=Author(s)|status=status (such as WIP, testing, stable)|github={{Github|user=username|branch=branch}}|LKVer=What Lorekeeper version the ext is built on|migration=yes/no|package=yes/no}}
+
{{Extensioninfobox|title=User Username Changes|desc=Allows users to change their usernames without staff assistance.|auth=AnimatedCritter|status=stable|github={{Github|user=AnimatedCritter|branch=extension/user-username-changes}}|LKVer=2.1.0|migration=yes|package=no}}
<!-- Put a short summary of your extension here! -->
+
This extension allows users to change their usernames. It also introduces a username log to keep track of all name changes, as well as a username cooldown. Staff can bypass the cooldown via the user index panel (/admin/users), if need-be.
 
== Installation ==
 
== Installation ==
<!-- Describe installation. Include any requirements (such as packages), necessary commands, etc. -->
+
Pull and merge the branch, making sure to address any merge issues.
 +
 
 +
Afterwards, run the following commands in your console:
 +
 
 +
<code>php artisan migrate</code>
 +
 
 +
<code>php artisan add-site-settings</code>
 +
 
 +
<code>php artisan update-extension-tracker</code>
 
== Configuration ==
 
== Configuration ==
<!-- Is any configuration necessary? Describe it here! -->
+
<code>username_change_cooldown</code>
== Usage ==
+
* Determines how many days a user must wait before being able to change their username again.
<!-- Is there anything users should know about using your extension? -->
+
* By default, this is set to 30 days.
 +
* To set no cooldown, change this value to 0.
 +
 
 
== Troubleshooting ==
 
== Troubleshooting ==
<!-- Are there known issues or errors that require user action? Who should they contact, and where, for support? -->
+
I am no longer on Discord. Instead, please contact me through CritterCodes (https://crittercodes.neocities.org/). Thank you!
 +
 
 +
'''Potential Issues & Solutions:'''
 +
 
 +
<code>Attempt to read property "updated_at" on null</code> when changing a username for the first time.
 +
* If you last pulled the branch before May 24<sup>th</sup>, you need to repull the branch. Afterwards, push the updates and the issue should be resolved!
 
== Images ==
 
== Images ==
<!-- Do you have any images to show what it looks like in action? -->
 
== See Also ==
 
<!-- Any relevant other pages. You may consider linking to related extensions, for instance. -->
 
  
 +
[[File:Screenshot 2023-05-02 120009.png|none|thumb]]

Latest revision as of 17:03, 28 January 2024

User Username Changes
Description Allows users to change their usernames without staff assistance.
Author(s) AnimatedCritter
Status stable
Github extension/user-username-changes
LK Version 2.1.0
Contains a Migration






This extension allows users to change their usernames. It also introduces a username log to keep track of all name changes, as well as a username cooldown. Staff can bypass the cooldown via the user index panel (/admin/users), if need-be.

Installation

Pull and merge the branch, making sure to address any merge issues.

Afterwards, run the following commands in your console:

php artisan migrate

php artisan add-site-settings

php artisan update-extension-tracker

Configuration

username_change_cooldown

  • Determines how many days a user must wait before being able to change their username again.
  • By default, this is set to 30 days.
  • To set no cooldown, change this value to 0.

Troubleshooting

I am no longer on Discord. Instead, please contact me through CritterCodes (https://crittercodes.neocities.org/). Thank you!

Potential Issues & Solutions:

Attempt to read property "updated_at" on null when changing a username for the first time.

  • If you last pulled the branch before May 24th, you need to repull the branch. Afterwards, push the updates and the issue should be resolved!

Images

Screenshot 2023-05-02 120009.png