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
I have two pages with the same parent page but their automatic aliases are very different. You can see in the attached screenshots the pages are set to the same parent and both are using the automatic alias.
Here's the current URL patterns:
Issue Archive => /[site:name]/issue/archive
Issue => /[node:menu-link:parent:url:path]/[node:title]
Alias is set like this as the intent is to have 1 Issue Archive per site, if Issues exist. D7 did this with a custom module.
The URL here is set the way it is to facilitate linking to other blocks such as Latest Issues Block and Current Issue Block where if more than 4 Issues exist on a site, it should add a button linking to the Issue Archive default which will show all of a site's Issues.
So the real issue here is: How should we handle the Issue Archive if the intent is to create one and be done?
Problems with making this a block:
If this is made a block with customizeable URLS, linking to the Issue Archive from the other Issue blocks will not work without a module
Making this a block will not limit the Issue Archive, so content editors can still make more than 1.
I have two pages with the same parent page but their automatic aliases are very different. You can see in the attached screenshots the pages are set to the same parent and both are using the automatic alias.
https://www.colorado.edu/demos/documentation/articles-and-issues/spring-issue

https://www.colorado.edu/demos/documentation/web-express-documentation/issue/archive

The text was updated successfully, but these errors were encountered: