*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.
-
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
Login as user
I would like the abilty as an administrator to login as a user so that I can check their access -
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 -
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 -
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.
-
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.
-
0
Targets and CSS
I am ending up with too many targets – and it’s becoming unwieldy. Most of these are the same, but only differ in the CSS file that is attached. Would it be possible to decouple the CSS from the target – maybe adding it to the template or configuration file – that seems to be where it belongs since it is a design element.
-
3
Site-wide Data Checks before Publishing
We’d like to run a final check before publishing for spelling, accessibility, broken links, and so on.
Performing these checks every time you edit a page slows down site development, so our developers turn them off, but we’d like them to be able to run a final pre-publication check when they think the site is ready. -
1
Dynamically prevent target publishing depending on the asset's content in XSL
Depending on an asset’s content, allow or block the publishing process (as soon as possible for performance reason).
We imagine a special xsl markup like ‘’.
For example : -
-1
Insert xhtml block into WYSIWYG content
Common Scenario: insert reusable block quote anywhere inside of free-form WYSIWYG content.
-
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).
-
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?
-
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
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. -
3
Allow publishing of non-xml pages
Cascade users would like the ability to publish non-xml pages. -
2
Customizable Tidy settings
It would be an excellent addition to Cascade Server if administrators
were able to specify the settings for Tidy to use in Cascade. This
could be implemented at the System Preferences level. -
3
Ability to link to folders
We should be able to tell Cascade the default directory index page for each site, so that published links to those pages go to “/” or “/site/” instead of “/index.html” or “/site/index.php”.
-
3
Improvement of starting publish delay
With Cascade 5.7.3, we observe that we have about a 30 seconds delay before the first asset in the publish queue starts its publication.
We need a parameter to optimize this delay. -
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.
-
1
Display Version Comments
Im working on a policy site which has a revision history page. It would be great If I could grab the version coments through an index block to display on this revision history page. The version comments describe the changes made which is what people need to know when they look at the revision history of recently changed policies.
Please Vote! Thanks!
Nate Tanner
University of Utah Health Care
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
