The Visual Editor's "Link" feature and the Code Editor's "Insert | ... URL" features enable users to browse for pages and media and have a link to these automatically generated. Links to other elements, like a link to a page with some data item id post fixed (ex. /products/ID-of-prodict) is not available.
It would be desirable if the "Link to" trees could easily be expanded so they could include more trees exposing other data and associated URLs.
It would be desirable that C1 Data Types could have a URL generator associated with them, able to produce a URL (typically relative) for a given data item. And that this would enable these items to show up in the "Link to" dialog.
It would be desirable that (linkable) data items in Page Data Folders are shown below their respective pages. Example is blog posts - linking to a such should happen by browsing to the blog page, then the post.
It would be desirable that links returned by a "URL generator" and persisted in content could be of an internal nature and a filter could expand them to a human/SEO friendly format at page render time (see feature request http://compositec1.codeplex.com/workitem/1075 - Feature request: Make url transformation pluggable)
It would be desirable if TreeDefinitions could sport a "LinkTo" attribute, serving as a URL generator and that such TreeDefinitions could be easily included in the "Link to" trees.
Use cases:
- Linking to a blog post or news item
- Linking to a rendering of a custom data item
- Linking to an external resource
Comments: Implemented
It would be desirable if the "Link to" trees could easily be expanded so they could include more trees exposing other data and associated URLs.
It would be desirable that C1 Data Types could have a URL generator associated with them, able to produce a URL (typically relative) for a given data item. And that this would enable these items to show up in the "Link to" dialog.
It would be desirable that (linkable) data items in Page Data Folders are shown below their respective pages. Example is blog posts - linking to a such should happen by browsing to the blog page, then the post.
It would be desirable that links returned by a "URL generator" and persisted in content could be of an internal nature and a filter could expand them to a human/SEO friendly format at page render time (see feature request http://compositec1.codeplex.com/workitem/1075 - Feature request: Make url transformation pluggable)
It would be desirable if TreeDefinitions could sport a "LinkTo" attribute, serving as a URL generator and that such TreeDefinitions could be easily included in the "Link to" trees.
Use cases:
- Linking to a blog post or news item
- Linking to a rendering of a custom data item
- Linking to an external resource
Comments: Implemented