Skip to content
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

Event creation looks somewhat broken #907

Closed
nekr0z opened this issue May 22, 2015 · 10 comments

Comments

Projects
None yet
4 participants
@nekr0z
Copy link
Contributor

commented May 22, 2015

�I have been trying to create an event on my Known site (hosted account, no idea what version is running there), but every time I try I get a white page with the following rather cryptic message (copied verbatim):

������n�0��_e�R8H�����J�(��������d61��X��!<=c���T�Ef&�����zz�|����>����ݡ7H=���y�,������5���Մ �d�pzD�4@����4H@�P���&���D���� ��������l-�ˡVNN��\� U��g�u�^i�T��G �f V-{T_cw��O��bW�����oa��V[��E��s������Њ(�s�9lu���vk���9H^���s� ���L_�V뺖x���S�A��>��G��$���D���V7G�8�5'��Q� j ����n����&���'t����y~��|�U^��^Z_�!1����"ٔ�A�#���:+K^�=�x�~��X�W�$����+x���,QB,.A��7fi��ҿ�3��^Q�$K�{��<��q�E���Ҵ\���\� /��!��⿗�5�`CL���YV�C��:I��nʟ�#����

I don't speak the language this message is in (whatever that might be), and I'm not really sure how the message of the successful event creation should look like, but seeing as how no event is added to my page I guess something is wrong here.

@mapkyca

This comment has been minimized.

Copy link
Member

commented May 22, 2015

Anything in the logs?

Also, might be worth pasting headers on the requests (use chrome dev tools or firefox with firebug installed)

Basically looks like something is corrupting the character encoding. I had something similar happen with an audio post which caused problems with modsecurity.

@benwerd

This comment has been minimized.

Copy link
Member

commented May 22, 2015

We're aware of an issue on the hosted service this morning with exactly
this result. Looking into it as a priority.

On Friday, May 22, 2015, Marcus Povey notifications@github.com wrote:

https://github.com/idno/Known/issues/907Anything in the logs?

Also, might be worth pasting headers on the requests (use chrome dev tools
or firefox with firebug installed)

Basically looks like something is corrupting the character encoding. I had
something similar happen with an audio post which caused problems with
modsecurity.


Reply to this email directly or view it on GitHub
#907 (comment).

Ben Werdmuller
http://goog_1933028737
benwerd.com | werd.io

+1 (312) 488-9373

@erinjo

This comment has been minimized.

Copy link
Member

commented May 23, 2015

Thanks for sharing this @nekr0z. We've reproduced the issue, and we're working on a fix.

@benwerd

This comment has been minimized.

Copy link
Member

commented May 23, 2015

@nekr0z I just pushed a fix. Let us know if it worked for you!

@nekr0z

This comment has been minimized.

Copy link
Contributor Author

commented May 23, 2015

Allright, I got it now: it seems to work as it is supposed to, but only as long as there is at least one ASCII character in the event name (the rest of the fields don't seem to matter). In case there are no ASCII characters in the event name (for example, the event is called "Ужин" - "Dinner" in Russian) the same (or sligtly different) cryptic message appears.

So this is i18n issue. Unicode.

@mapkyca

This comment has been minimized.

Copy link
Member

commented May 23, 2015

For the record, self hosted appears to be fine. So this may be a hosted issue...

@mapkyca

This comment has been minimized.

Copy link
Member

commented May 23, 2015

Interestingly there's nothing special about how titles are saved in events... I wonder if it occurs anywhere else...

@mapkyca

This comment has been minimized.

Copy link
Member

commented May 23, 2015

Not able to replicate on hosted with procedure described (posting entirely in Russian)

@nekr0z

This comment has been minimized.

Copy link
Contributor Author

commented May 23, 2015

I can no longer reproduce it either, although I could an hour ago. Fix took time to propagate?

@mapkyca

This comment has been minimized.

Copy link
Member

commented May 23, 2015

Very likely

@nekr0z nekr0z closed this May 23, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.