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
Currently, it is only possible to map to file choosers. For added flexibility, it would be nice to be able to map to all of the possible chooser types, or those deemed most appropriate (ie do we need a symlink chooser).
Use case: migrated content contains links to SSI's and those includes are created in Cascade as XHTML Blocks. The Data Definition for the pages contains a block chooser for these include blocks.
The text was updated successfully, but these errors were encountered:
Currently, it is only possible to map to file choosers. For added flexibility, it would be nice to be able to map to all of the possible chooser types, or those deemed most appropriate (ie do we need a symlink chooser).
Use case: migrated content contains links to SSI's and those includes are created in Cascade as XHTML Blocks. The Data Definition for the pages contains a block chooser for these include blocks.
The text was updated successfully, but these errors were encountered: