-
Notifications
You must be signed in to change notification settings - Fork 641
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
Add slug field to singles entries #3368
Comments
Just added this for the next 3.2 Alpha release. |
@brandonkelly Should there be an option to disable user editable slugs on singles? For instance, a single may be a landing page for a news section, so we'd set this single to Also, there may be existing template structures that don't count on users being able to edit slugs on singles. Because of this, I'd recommend that editable slugs on singles is an opt-in feature. |
@jsunsawyer We can address that at the same time as #3953 for Craft 4, where it will be possible to customize which CMS-defined fields should be visible, and where. |
@brandonkelly Since #3953 already got merged; is the option to disable editing the slug of single entries still planned? we have many cases wehre it shouln't be possible to do so. Thanks! |
Sorry yeah the new field layout changes in 3.5 didn’t go as far as what we’d planned to do in 4.0 so there’s still room for improvement here. Will reopen this and add it to the 4.0 milestone. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Currently only way to set url for single type section is to do this in its settings, using URI field. I propose adding standard slug field to these sections, just like one that exists for structures and channels.
My reasons for this proposal are:
{slug}
variable in URI field. But, without slug field, there is no way to change this initial slug that was created while creating entry (except temporary changing section type to channel or structure maybe).The text was updated successfully, but these errors were encountered: