*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.
-
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.
-
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.” -
1
Application should more intelligently determine if a tab is currently selected
This is in reference to an already existing feature request, although I think it’s more of a bug. In the 4.x we didn’t have a problem using the URL webedit.brandeis.edu for Cascade, but in 5.x (at least 5.5.2) the page highlights the Edit tab when viewing the page.
People can still view and can still edit so it’s not the most critical bug, but it is fairly confusing for the UI and should be fixed. -
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
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
Support for Database Transport WSDL
We created a table of site names and id numbers for each of our 150+ sites for use when creating database transports. It would be great if we could set up a database transport for each from this table, but it appears that database transports are not included in the family of entity types Web Services can touch. All read calls get this: "Entity type com.hannonhill.cascade.model.dom.DatabaseTransport does not have corresponding Schema object type
-
1
Add a parameter to clean up the publish queue when cascade is restarted
The publish queue is now persistant when we restart Cascade 5.7.3
But in some cases, it might be interresting to ‘reset’ the system upon a restart. -
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. -
0
Publish an offline asset = Unpublish
If an asset is offline and not yet published, then the publication is forbidden (current behavior)
If an asset is offline and previously being published, then it must be unpublished
This behavior should be useful when a whole directory is published. -
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
Knowledge Base Plugin
We have a need to create a knowledge base for our cascade site, but need to control categories, type and the ability to import different types of media resources.
we can create a pile of folders and put pages in them but it doesn’t standardize the process into something that can become constant (i.e. locked/controlled category pulldowns – standard form for submitting ideas, etc)TIA, -
3
More information in the Publisher list
Things to include:
- Target/Destination being published to- Checkboxes to delete more than one job at once- Ability to see if publish or unpublishfor starters…. -
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.
-
0
Allow data definition fields to be "grayed" out
Allow for data definition field to be grayed out as additional option for restricting field-level edit access in data definitions.
-
-1
Insert xhtml block into WYSIWYG content
Common Scenario: insert reusable block quote anywhere inside of free-form WYSIWYG content.
-
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.
-
-6
Include option to search for CSS class usage
Add the ability to search for usage of particular css classes on pages. As an example, a quick find to see where across the site a particular class is being used in order to check the impact of a change to that class.
-
-1
Granular custom Metadata security
Allow for the same type of security assignment for custom Metadata fields that data definition fields have.
-
-1
Allow connection to multiple LDAPs
Allow connection to multiple LDAP servers to facilitate pulling in users from different systems.
-
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
