*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
Offline Editing
It would be interesting to support offline editing of Drafts through something like Google Gears. The support could be limited to Drafts, Locks, and/or assets in workflows on which the user has ownership of the current step. Starting with drafts probably is the simplest, because there’s a much lower chance of other users interfering while the asset is being edited offline.
-
0
Custom Authentication Authorization
We are using the custom authentication api to redirect users to our single sign-on service and then redirect them back to Cascade. What I would like to also do is check that each user is an authorized user of the service. If the username that authenticates is not in the cascade database they receive an ugly tomcat error. We want to be able to redirect them to a clean error page. Ideally it would be great to have another interface in the api that allows us to use the method that Cascade currently uses when a user tries to log in and is or is not in the database. At least a meaningful error instead generated from the exception instead of the tomcat error.
-
1
Audit trail for access-change events
We’ve run into a few situations where, as best we can tell, someone stumbled into the access tab for one of the folders in their site (or the site folder itself) and inadvertently set it to be world-writable. Unfortunately, we can’t really go back and verify that this is in fact what happened, let alone figure out who did it and when.
It would be neat if any access changes made to assets were audited, that way we can verify that this is user error and follow up with that user to make sure they understand how to use the access screen.
-
1
Additional auth methods for SFTP
We have a site that needs to publish to a server which, for security reasons, does not enable the “password” SSH auth method. For situations like these, it would be great if Cascade could support other common auth methods such as publickey and keyboard-interactive.
-
1
Users Screen Addition
We have upwards of 400 users in our system. It would be nice in the Users Screen to show the last successful login date of the users with the option to sort by this date to help us weed out inactive users. By “us” i mean at least administrators, but maybe for managers too?
-
2
Role Permission request related to "Cancel publish jobs"
I have a have a feature request for the “Cancel publish jobs” permission.
Right now, if a user has permission to cancel a job, he/she can do so for any job in the queue. I would like to request that there at least be an option set for “Cancel publish jobs belonging to groups user is a member of.”
The second option would be a possible split to enable “Cancel publish jobs belonging to user” so that a user can cancel their own publish, but not necessarily others in their group or all at large.
Thank you.
-
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. -
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. -
3
Allow publishing of non-xml pages
Cascade users would like the ability to publish non-xml pages. -
2
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. -
1
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. -
2
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) -
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. -
1
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.
-
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.
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
