Feature #44403
Support setting a target node for Shortcut
Status: | Resolved | Start date: | 2013-01-09 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Robert Lemke | % Done: | 100% |
|
Category: | Frontend | |||
Target version: | Base Distribution - Sprint February 2013 |
Description
Even if there's no user interface which could handle Shortcut nodes (page tree redirects to the actual node, for example), it would be useful to enhance the Shortcut page type so that a specific node can be set programmatically instead of the behavior to redirect to the first sub node.
Associated revisions
[FEATURE] Support manually set target node for Shortcut
This enhances the Shortcut content type to support a specifically set
target node which overrides the default behavior or redirecting to the
first sub node. The property "targetNode" currently needs to be set
manually (through the Node API) as there is no user interface in place
yet.
Change-Id: I77f21446e4b3c11015aab009e3ab0dacfdc6a8b9
Resolves: #44403
History
#1 Updated by Robert Lemke over 2 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset cd80e4ce6c644d0a700b39e7b2593a81d3ddc442.