You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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?
Description
When trying to edit a blog with an underscore in its name it results in a 404.
Steps to reproduce
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
Version or last commit:
v0.13.2
Thank you for your time!
The text was updated successfully, but these errors were encountered: