-
-
Notifications
You must be signed in to change notification settings - Fork 834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
utf8-url encoded username url support (simple solve) #1949
Comments
|
Note: Using space in username breaks post cross referencing. Allowing space is more tricky here. |
It seems that this post mentions a rather good solution to the username with |
related #1356 |
More cross-reference: #557 and flarum/issue-archive#254 |
I'm not a huge fan of allowing space, but I did discover that |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We do this to keep the amount of open issues to a manageable minimum. |
We are closing this issue as it seems to have grown stale. If you still encounter this problem with the latest version, feel free to re-open it. |
Feature Request
Is your feature request related to a problem? Please describe.
I am having problem if I manually allow usernames to contain spaces and non-ASCII characters and use a link to go to the user page, it would trigger a 404 error (url encoded strings are not converted).
Describe the solution you'd like
A detailed description of your proposed solution. Include:
Modify the following kines in function
protected function data(ServerRequestInterface $request, Document $document)
insrc/Api//Controller/ShowUserController.php
to
Tested on my forum at this site. As shown here in Firefox:
Justify why this feature belongs in Flarum's core, rather than in a third-party extension
This changes the behavior of core api. Also the overhead involved with a decode on strings that are not percent-encoded may not be too high (not metered). This would allow removing the restriction on username characters (spaces allowed as encoded
%20
in url request) at least on the user display side.Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Probably implement this somewhere in a extension.
The text was updated successfully, but these errors were encountered: