Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[4.x]: Need warning for duplicate slug when editing #13017

Closed
wbdzynr opened this issue Mar 30, 2023 · 0 comments
Closed

[4.x]: Need warning for duplicate slug when editing #13017

wbdzynr opened this issue Mar 30, 2023 · 0 comments

Comments

@wbdzynr
Copy link

wbdzynr commented Mar 30, 2023

What happened?

Description

If you are editing an entry, and you make changes to the slug (for a desired result), it doesn't warn you if there is already an entry with that slug. It just appends a number to the end again.

Steps to reproduce

  1. Duplicate an entry and try to remove the "-2" from the end, then save. If you check entry Validation isn't performed when enabling entries from entry index page. #2, it will have a "-2" at the end of the slug again.

Expected behavior

When creating a new entry, appending a number to the end of the slug is fine. However, if you are editing and you expect a slug to be a certain way (ie you edited it) and that slug already exists, it would be nice if a warning would appear (ie "An entry with that slug already exists. (Entry ID: 111).") giving you a heads up that your desired changes won't happen.

Actual behavior

Currently, it just appends a number to the end of the slug again.

Craft CMS version

4.4.5

PHP version

No response

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions

@craftcms craftcms locked and limited conversation to collaborators Apr 3, 2023
@brandonkelly brandonkelly converted this issue into discussion #13027 Apr 3, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

1 participant