*Note - Please use textile markup to input code examples in the comments box (e.g. start and end the code sections with @ signs). Click the pencil icon in the word processor to remove the WYSIWYG.
Cascade Server Ideas
Please submit your ideas on how to improve Cascade Server.
-
18
Export from one instance of Cascade/ Import to another
Our developers work in our test instance of Cascade which publishes to our test web servers. We would like an easy way to export assets from one Cascade instance (test) so that we would import them into another Cascade instance (prod). We need 2 Cascade instances in order to OS and software upgrades etc -
16
Asset Recycling Bin
It would be great to have a more robust asset recycling bin to prevent users from accidentally deleting items that can’t be recovered by administrators.
-
14
Sites as Formal Objects
A Site is a formal collection assets that includes:
- roles that are local to that site- own set of Page Configuration Sets, Content Types- NO targets, but a collection of destinations to which assets publish -
10
Data Definitions in Blocks
I would like to attach data definitions to blocks. The metadata sets are usually limited with fields such as no WYSIWYG editor and no date chooser.
-
10
Ajaxify Publisher Status
Instead of refreshing the entire page, use ajax to update publisher status. In addition, possibly include a publisher status for each user at the top right to allow them to keep working while still knowing the status of their last publish.
-
9
Visually indicate when an asset becomes "dirty"
When an asset that is marked as “should be published” is modified, it should be displayed differently in the left nav until it is published again. This way it is easier to keep track of which assets are “dirty”; and by “dirty” i mean that the last modified time > last published time.
-
6
Login as user
I would like the abilty as an administrator to login as a user so that I can check their access -
8
Folder Order for Asset Factories
I’ve gotten feedback that it would be very useful to manually order asset factories in the New menu. It also would be great to be able to add separators between groups of items. Maybe have a container be configurable to be a group with a separator or a menu level that must be expanded?
-
7
Menu Blocks
I’d like to see a Menu Block that would provide an easy way to create the most commonly used Menus:
- Breadcrumbs
- Context Navigation
- Next/Previous
- Global Top Nav (Arbitrary Selected Objects)
-
6
New Custom Roles
I’d like to see the ability to create arbitrary roles with whatever collection of abilities you want.
-
7
Unpublish asset when renamed or moved to another folder upon expiration
This idea is a continuation of the feature request located here: http://support.hannonhill.com/browse/CSNEW-77
Sometimes the asset’s end date will trigger a move to another folder
for “expired” content. The asset should probably be unpublished before
it is moved.
The same can be said for assets that are renamed. Currently, when
an asset is renamed, the old asset remains on the server and does not
get unpublished.
-
5
Sort logs by date
In the Administrator area of Cascade there is a place to view/download logs. It would be great if we could sort them by date. This would make it easier to find the appropriate logs for support
-
6
Don't Allow Publish Dupes
Although I continue to tell my Web editors not to keep clicking publish and to view the queue, some of them repeatedly publish the same assets because they don’t see the change on their website. I suggest showing the user an error message that says something like: This asset was just published by you and is still in the publish queue.
I’m not sure if it should allow them to publish it again or make them wait. Or maybe they’ll need to cancel the previous publish job.
All I know is that I hate seeing a dozen publish jobs for the same folder, slowing down publishing for everyone. -
6
Restore Data by Site
It would be great to be able to restore data on a site-by-site basis.
For installations in which there are several sites in one installation,
if one site’s data is somehow corrupted, or they have data that needs
to be restored, you have to restore the entire database, which rolls all
sites back to the condition in the restored data. Restoring site-by-site would be ideal. -
4
Dates in Dynamic Metadata
Having a special date/time/date-time chooser in dynamic metadata would make it a lot easier for users to add things like “Original Publication Date” or add more finely granular expiration dates like “Home Page Expiration” and “Section Expiration”.
See CSNEW-253 -
5
Publish sets and targets
It could be nice to enable publish sets to have control over what target(s) they publish to.
-
5
Height and width attributes of image type files in index blocks and data definitions
It would be nice to have the CMS display the height and width of file
assets with particular extensions within system index blocks. This
would allow users to easily size their images in XSL stylesheets. -
5
Publish Full/Absolute URLs
Cascade Server currently allows for root-relative URLs to be published out when “Maintain absolute links” is checked. It would be very helpful at times if a page could have fully qualified absolute URLs. Currently this is almost possible by applying an XSLT to the page at the template level but will not work if there are External Link assets that are generated in region(s) of the page.
This may tie to feature requests regarding having Cascade gain a concept of a “site.” -
5
Create editing plugin framework
Like the current Asset Factory plugins, it would be great to attach plugins to edit events. This would allow developers to do things like verify certain file extensions for edited file or naming conventions, etc. Currently, this can only be done on the initial asset creation.
-
5
DTD links for Workflows, Data Definitions, etc...
When creating dynamic fields in Metadata Sets, there is a DTD link under the Configuration box that users can reference when writing an XML configuration. It would be nice if a link like this would appear next to ANY box that requires XML input (like Workflows, Data Definitions, index blocks, etc).
Top / Up / Table of Contents
© 2001-2009 Hannon Hill Corporation. All rights reserved.
Accessibility | Legal | Technical Support | Knowledge Base | Site Map | Index
Accessibility | Legal | Technical Support | Knowledge Base | Site Map | Index
