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
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.
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: