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

Underscore in Alias leads to 404 #743

Open
honze-net opened this issue Aug 14, 2023 · 1 comment
Open

Underscore in Alias leads to 404 #743

honze-net opened this issue Aug 14, 2023 · 1 comment
Labels

Comments

@honze-net
Copy link

honze-net commented Aug 14, 2023

Description

When trying to edit a blog with an underscore in its name it results in a 404.

Steps to reproduce

  1. I created a blog (https://infosec.press/honze_net/) and it assigned my handle.
  2. Clicking on customize will let me add a description for example.
  3. Clicking on "Save changes" will result in a 404. (https://infosec.press/api/collections/honze_net)

Other blogs created manually without an underscore are not affected and are working.
Creating a new blog with an underscore will lead to an error message, that says: Collection alias isn't valid.
This is a perfectly fine choice. But the first blog was created automatically and I had no idea this would happen. (I suspect that a validity check is missing while creating the user and the first blog.)

Expected behavior

Blogs with an underscore should be editable or not created at all. I guess all valid characters from fediverse handles should be valid blog name characters, but it has not to be that way.

Application configuration

  • Single mode or Multi-user mode? multi
  • Database? [mysql/sqlite] no idea
  • Open registration? [yes/no] yes
  • Federation enabled? [yes/no] i guess

Version or last commit:
v0.13.2

Thank you for your time!

@thebaer thebaer added the bug label Sep 7, 2023
@thebaer
Copy link
Member

thebaer commented Sep 7, 2023

Thanks for reporting this! Yes, it sounds like an issue with whatever method you used to create that first user. I assume it was done with the writefreely config start command? Or was it something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants