You can now set a global prefix and/or suffix. This allows you to change the style of the user-specified name.
For example, I've set the prefix at XF Liam to @, so my profile URL is now https://xf-liam.com/@liam/.
There is now an option to display the vanity name on the profile page next to the username. This will link to the profile (and therefore the member card).
this is great
ideally, the position of the "@liam"-Link should be underneath the "Username" (between "Username" and "Well-Known Member"), but I guess that will be a bit difficult to realise as it will
make the box a bit bigger in height.....
75%;display: block;
Not that difficult, just have to make the link a block display instead of inline.
This can actually be done by using the height option to inject some other CSS into the element:
Code:75%;display: block;
Obviously that isn't ideal, so I think I'm going to change that option to just a general CSS option in the next update (which won't be released immediately because people get annoyed when loads of updates are released in quick succession).
Liam
font-size: 14px;
Cool looking addon. Does the park setting automatically redirect members/profile to the new vanity URI? Purely to avoid losing SEO juice.
- Allow full stops in the vanity names
- Change the font size entry into an inline CSS entry, for full CSS customisation
Can you add a feature to ensure Vanity names NEVER match existing routes? Could you also add a feature to REQUIRE the prefix when accessing a page, to ensure no conflict? I am a purchaser and would love this.
Last I tested, unprefixed URLs routed to prefixed URLs.A user cannot use a route as a vanity name. It doesn't save, and there's no way around this.
If you set a prefix in the options, it is global and is always required to access the page - there aren't any valid names without the prefix...
So, I'm not 100% sure what you're asking...?
Liam
We use essential cookies to make this site work, and optional cookies to enhance your experience.