-
Notifications
You must be signed in to change notification settings - Fork 0
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
Uploader upload route containing UTF-8 characters #44
Comments
@ercanozkaya I've got this support ticket assigned to me. The customer says it got fixed on 3.7.4 but I've just upgraded and still have the same issue. The problem is when json encoding the URL available in the uploader options. The URL contains the menu item alias and when this one contains special characters these get encoded (not URL encoded) by the json_encode function invalidating the URL. A solution is to force json_encode not to encode via the JSON_UNESCAPED_UNICODE flag. Thoughts? |
We have multiple other people reporting similar issues. |
@ercanozkaya @amazeika This one is still hanging, what shall we do with it? |
@ercanozkaya we haven't yet fixed this have we? |
@amazeika nope we haven't
…On Friday, February 9, 2018, Arunas Mazeika ***@***.***> wrote:
@ercanozkaya <https://github.com/ercanozkaya> we haven't yet fixed this
have we?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFhDsr_hRB4Bco0L6jMEUZaWRRU3jf_ks5tTB2QgaJpZM4Oc8L9>
.
--
Ercan Özkaya
|
@amazeika @ercanozkaya Is this something we can resolve? Or is it too hard? |
The uploader options contain the URL as provided by the router route object. If the path contains non encoded characters the json_encode call will encode these if the JSON_UNESCAPED_UNICODE is not set.
See:
The text was updated successfully, but these errors were encountered: