*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.
-
3
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. -
2
Create event listener framework within Cascade for all pluggable events
Cascade would see benefit in having a generic EventListener interface
that could be implemented and registered. When events are generated,
the listener itself would determine what it would want to do based on
the type of event. This would go a long way towards having a single way
to provide trigger-like capabilities without having specific, separate,
and numerous configuration frameworks for each of the different type of
listener type plugin interfaces already available (e.g. workflow
triggers, publish triggers, etc). -
0
Ability to modify look, feel, and text of workflow-generated emails
It would be nice if Cascade could allow administrators to modify the emails that are generated by workflows. -
1
Apply data definitions to blocks
It would be useful to be able to apply data definitions to blocks in
addition to pages. This would help in scenarios where there is
structured content which isn’t tied to any one page. -
1
Allow publishing of non-xml pages
Cascade users would like the ability to publish non-xml pages. -
1
A method to send administrative messages to active users
It would be nice if you could somehow send a message (a noticable
message, not to the users’ inboxes) to the active users so that they
can be notified that, for example, the system is going down for
maintenance at a specified time. This would smooth out the process of
doing all of these upgrades by helping to eliminate the need for admins
to contact each user individually, or just kick them out of the system
and risk lost work. -
0
System option for removing empty folders on unpublish request
Currently, unpublish will remove assets from various destinations.
However, if it removes the last file in a particular folder, it will
not try to remove the folder. Either a system option or an accompanying
option on the publish screen to remove empty folders on unpublish,
would be in order. -
0
Publish at Start Date Checkbox
I t would be nice to have a new wired field that when checked the asset will be published at the date and time.
-
0
Ability to require comments in workflows
It would be helpful if the Cascade had the ability to require comments
within a workflow. Similarly, if comments are not required, it would be
nice to bypass the page completely. -
0
Interface to the dictionary
Cascade should have a simple interface to the spell-checking dictionary
such that administrators can add words (or edit words if a user has
accidentally added a mispelled word) -
0
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. -
0
Obtain listing of all groups defined on HannonHill server via SOAP
Looking for a way to get a listing of all groups(EntityTypeString=‘GROUP’) that have been defined in HannonHill. I originally posted question in ‘How do I’(http://success.hannonhill.com/cascade-server-forum/how-do-i…/get-list-hannonhill-groups-via) and was told this functionality does not currently exist and to add as a request here.
-
4
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. -
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. -
2
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”.
-
2
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
-
2
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.
Top / Up / Table of Contents
© 2001-2008 Hannon Hill Corporation. All rights reserved.
Accessibility | Legal | Technical Support | Knowledge Base | Site Map | Index
Accessibility | Legal | Technical Support | Knowledge Base | Site Map | Index
