When creating content types, people need to also go to the buried path alias patterns page under config/search/path. It would make more sense if those settings also appeared on the content type edit screen, enabling path patterns where people expect to find them.

Comments

Bojhan’s picture

Bojhan commented

Participant 7, usability test at google - 3-2-2012

xjm’s picture

xjm
she/her
Primary language English
commented
Issue tags: +Usability

Tagging.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Issue tags: +GoogleUX2012
dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

The problem becomes what kind of UI do we expose for translated content since there could be X number of patterns for a content type based on the number of enabled languages.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (duplicate)

This is a duplicate of #750632: Add pattern edit to admin/structure/types/manage/[node-type] and admin/structure/taxonomy/[vocabulary-machine-name]/edit pages

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Issue summary: View changes

typo