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

Add slug field to singles entries #3368

Closed
piotrpog opened this issue Oct 10, 2018 · 5 comments
Closed

Add slug field to singles entries #3368

piotrpog opened this issue Oct 10, 2018 · 5 comments
Labels
content modeling 📓 features related to content modeling enhancement improvements to existing features

Comments

@piotrpog
Copy link

piotrpog commented Oct 10, 2018

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:

  • Singles still have slug - you can use {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).
  • I dont want my content creators to go into settings to just change url of some entry - multitude of options present there would just confuse them and they might break something.
@brandonkelly brandonkelly added the enhancement improvements to existing features label Oct 11, 2018
@brandonkelly brandonkelly added this to the 3.2 milestone Mar 11, 2019
brandonkelly added a commit that referenced this issue May 24, 2019
@brandonkelly
Copy link
Member

Just added this for the next 3.2 Alpha release.

@jsunsawyer
Copy link

@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 /news. Then, all news posts in our news channel would be news/{slug}.

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.

@brandonkelly
Copy link
Member

@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.

@jorisnoo
Copy link

@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!

@brandonkelly
Copy link
Member

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.

@brandonkelly brandonkelly reopened this Sep 29, 2020
@brandonkelly brandonkelly added the content modeling 📓 features related to content modeling label Sep 29, 2020
@brandonkelly brandonkelly added this to the 4.0 milestone Sep 29, 2020
mattstein pushed a commit to craftcms/docs that referenced this issue Oct 27, 2020
@craftcms craftcms locked and limited conversation to collaborators Jun 22, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
content modeling 📓 features related to content modeling enhancement improvements to existing features
Projects
None yet
Development

No branches or pull requests

4 participants