Skip to content

When creating a new library component, allow non-ascii characters in the URL key #3015

Description

@bradenmacdonald

Currently, when you create a new Unit/Subsection/Section, and you give it a title containing only non-ascii characters:

Image

you get that title reflected in the container's URL:

e.g. http://.../authoring/library/...:unit:αθήνα-587b00

But this doesn't yet work for creating new text/problem/video components: although you can set the title before they are saved, they always get a random UUID in the URL. (Unless you then copy and paste them, which gives you a friendly slug that works with unicode characters).

Change either the backend as required so that new text/problem/video components can use non-ascii letters in their friendly URL codes/slugs, just like containers do, and just like copy-paste does.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedReady to be picked up by anyone in the community

    Type

    Fields

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions