Talmyric Profile Vanity URLs

Talmyric Profile Vanity URLs 1.23.1

No permission to buy ($29.95)

Frequently Asked Questions​

It gives members readable profile addresses and provides controls for choosing, changing, approving and managing them.

A username is the member’s forum name. A slug is the address component used in a URL such as /members/example-name/. A custom slug can differ from the username.

Yes, when custom editing is enabled and they have permission. Eligibility requirements, reserved names, edit limits, cooldowns and approval rules still apply.

Yes. Set the member edit allowance to one. Larger allowances and group-specific limits are also available.

Yes. Group permissions can adjust edit allowances and reduce cooldowns. Separate bypass permissions are available.

Yes. Custom-to-automatic resets are supported, subject to the applicable permissions, editing rules and approval requirements.

Stored previous aliases remain owned and resolve to the member’s current profile. Those aliases are retained when the current address changes.

An address retained as an owned alias remains reserved for its owner.

The stored reservation remains attached to the deleted member’s ID. The ownership inspector identifies these records.

Yes. Enable moderator approval and grant the review permission to the appropriate staff. Requests can be handled through the native approval queue or the staff dashboard.

Yes. Members can cancel a pending request or submit a replacement, subject to request-waiting rules.

Yes. Configure the pending-request expiry period. Processing follows XenForo’s scheduled and background job activity.

No. Private notes are stored separately. Members receive the applicable decision information and rejection reason.

Yes. The staff dashboard supports previews for approving or rejecting up to 25 pending requests at a time. Requests are checked again when confirmed.

No. Administrator address edits do not consume a member edit. Resetting the member’s count and cooldown is a separate control.

It shows the current and proposed canonical, member and username URLs, along with the edit-count and cooldown reset effects. Availability is checked again when saving.

No. It reads ownership, current records, reservations and pending requests. It does not release or reassign aliases.

No. Reserved-name rules, validation, current records and other checks can still prevent its use.

A pending request is displayed separately from stored ownership. It is not an ownership claim.

Yes. ACP bulk tools support up to 50 member IDs per preview for initialization, repair, allowance resets or restoration of automatic addresses.

Changed or conflicting records are skipped during confirmation. Results are recorded individually.

Yes. CSV export uses the same filters as the activity log. Each batch contains up to 1,000 matching rows; use the last exported entry ID to continue.

UTC. Both the selected start day and end day are included.

Older free-text log entries may not contain a structured affected-member ID. The filter avoids guessing IDs from unrelated text.

Some older aliases were stored only as hashes. Their original text cannot always be recovered, although exact-value ownership inspection still uses the stored hash.

Yes, through XenForo’s phrase system. Saved preset text, private notes and historical audit text are stored data and are not retroactively translated.

Upgrade to 1.23.1, complete pending phrase rebuild jobs and reload the page. This version supplies the four missing option explanations reported in 1.23.0.

Check that the add-on and custom editor are enabled and that the member has the change permission. Other editing restrictions may still prevent a change.

The declared minimum is XenForo 2.3.0, with PHP 8.0+. Source and component verification used XenForo 2.3.13, PHP 8.3.28 and MariaDB 10.4.32. Earlier versions and a complete live acceptance pass for 1.23.1 remain unverified.

Back up the database and files, test on staging, upgrade the existing add-on through ACP, and finish pending setup and rebuild jobs. Do not uninstall before upgrading.

Include the add-on, XenForo, PHP and database versions; reproduction steps; exact error or phrase-key text; affected language/style; and relevant server errors. Remove passwords, tokens and private member information.
Back
Top Bottom