Skip to content

/ strapi

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

Jump to bottom

(Russian cyrillic) ERROR on save - Content Type name cannot be pluralized #7098

Open
reslear opened this issue Jul 21, 2020 · 3 comments
Open

(Russian cyrillic) ERROR on save - Content Type name cannot be pluralized #7098

reslear opened this issue Jul 21, 2020 · 3 comments
Labels
good first issue priority: low source: plugin:content-type-builder status: confirmed type: bug

Comments

@reslear
Copy link

@reslear reslear commented Jul 21, 2020 •
edited

Describe the bug
A clear and concise description of what the bug is.

Steps to reproduce the behavior

  1. Go to 'http://localhost:1337/admin/plugins/content-type-builder/'
  2. Click on 'content-type edit'
  3. change name in cyr symbols "Заказы"
  4. Click on 'Save'
  5. See error in console

Expected behavior
payload: error: contentType.name
Content Type name "Заказы" cannot be pluralized. Suggestion: add Item after the name (e.g News -> NewsItem).

Screenshots
Снимок экрана 2020-07-21 в 15 14 00

System

  • Node.js version: v12.16.3
  • NPM version: latest
  • Strapi version: 3.0.6
  • Database: postgres
  • Operating system: macos
@reslear reslear changed the title Content Type name cannot be pluralized (Russian cyrillic) ERROR on save - Content Type name cannot be pluralized Jul 22, 2020
@reslear reslear mentioned this issue Jul 22, 2020
Merged
@lacoste-sochi

This comment was marked as off-topic.

Sign in to view
@lauriejim
Copy link
Member

@lauriejim lauriejim commented Jul 31, 2020

Hello! It's not planned to support this.
In fact, we should avoid the possibility to have other that Latin characters as Content-Type name (for now)
@petersg83 @alexandrebodin probably something easy to fix.
@reslear
Copy link
Author

@reslear reslear commented Aug 2, 2020 •
edited

Hello! It's not planned to support this.
In fact, we should avoid the possibility to have other that Latin characters as Content-Type name (for now)
@petersg83 @alexandrebodin probably something easy to fix.

thx for answer
unstable, but worked on previous versions (last beta), maybe need to make another text field label without pluralization and regexp check, for good visualization in the sidebar post types multi-language.

Снимок экрана 2020-08-03 в 00 29 44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue priority: low source: plugin:content-type-builder status: confirmed type: bug
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@lauriejim @reslear @lacoste-sochi
You can’t perform that action at this time.