User Search can't find user with unicode top level domain #582

Closed
opened 2019-06-16 23:06:27 +00:00 by nee · 2 comments
Member

What happens:

Neither of these find the user:

This one @payphone@zetsubou.みんな even gives a weird bugged out result screen:
2019-06-17-005332_616x174_scrot

The follow button here does not work.

What is expected:

The profile of https://zetsubou.xn--q9jyb4c/payphone is imported and listed and can be followed.

How to reproduce:

  1. The user does not exist on my instance yet and should be fetched.
  2. Put any of the previously listed URIs into the user search.

Other Notes:

I don't know if it's an encoding error on the front-end or a pleroma-backend error. Edit: importing users with normal tlds works fine btw.

**What happens:** Neither of these find the user: * @payphone@zetsubou.xn--q9jyb4c * @payphone@zetsubou.みんな * payphone@zetsubou.xn--q9jyb4c * payphone@zetsubou.みんな * https://zetsubou.xn--q9jyb4c/payphone This one @payphone@zetsubou.みんな even gives a weird bugged out result screen: ![2019-06-17-005332_616x174_scrot](/attachments/4a3bb114-bc4f-43e3-a79d-470545dbc2a8) The follow button here does not work. **What is expected:** The profile of https://zetsubou.xn--q9jyb4c/payphone is imported and listed and can be followed. **How to reproduce:** 1. The user does not exist on my instance yet and should be fetched. 1. Put any of the previously listed URIs into the user search. **Other Notes:** I don't know if it's an encoding error on the front-end or a pleroma-backend error. **Edit**: importing users with normal tlds works fine btw.
Member

This is a backend error. Backend returns errors: {detail: "Internal server error"} when search user with Unicode with proper encoding at front-end side. (moved to pleroma/pleroma#1005)

Moreover, frontend doesn't handle API error response properly. Fixed at #2111

This is a backend error. Backend returns `errors: {detail: "Internal server error"}` when search user with Unicode with proper encoding at front-end side. (moved to https://git.pleroma.social/pleroma/pleroma/issues/1005) Moreover, frontend doesn't handle API error response properly. Fixed at https://git.pleroma.social/pleroma/pleroma-fe/pulls/2111
Member

fixed

fixed
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-fe#582
No description provided.