Please submit your ideas on how to improve Cascade Server.
-
15
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. -
14
'Apply to Children' checkbox for 'Edit' tab of asset factory containers
Currently, when you edit an asset factory container, you
have the option to set the applicable groups. The problem arises when you want
to apply these permissions changes to the asset factories within the container
as well as child containers. As of now, this field must be set individually for each child asset factory (or child container). -
14
Allow Template sharing across Sites
With the addition of Sites, would be great to be able to keep Templates in a common location and re-use them across multiple Sites.
-
14
Contextual (Site-specific) Roles
With Sites in place, would like the ability to create new custom Roles and assign users/groups Roles on a per-Site basis.
-
14
Display a Message Indicating that an Asset is Being Edited by Another User
Currently it is possible for multiple users to edit the same asset at the same time without being given any notification that somebody else is editing the asset. A message should be displayed on the edit screen informing users when this occurs.
-
14
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?
-
14
Robust Cross-Site Linking
Would like the ability to link to an asset on a different Site that may be published to an entirely different server. In this case, the Site URL of the linked-to asset would be used to determine the published location of that asset.
-
13
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. -
13
Ability for users to easily empty their mailbox/delete all messages in dashboard
Would be nice if users could easily empty their mailbox/delete all messages in Cascade Dashboard via a simple action to remove all.
-
13
Add object/video embedding button to TinyMCE toolbar
It would be great to embrace and extend the TinyMCE media plug-in to support video, flash, and other embedding without having to resort to HTML source editing.
-
13
Better interface for CSS styles
It would be nice to have a better interface for adding CSS classes for the Web
editors to see in the styles menus of the WYSIWYG. Some thoughts:
- Global vs. groups vs. targets: While it’s useful, it would be nice to see it
instead (or in addition) to be associated with templates or configuration sets.
I like the idea of listing the classes in the template because sometimes very
different templates may want to share the same target.
- CSS file: It’s nice to be able to add a CSS file to a target. Personally I
use this so that the Web editor can see the classes from the styles menu in
action (not to see other CSS for the rest of the page). One idea is to have
Cascade parse through the CSS file and automatically make the classes available.
- If the above is not possible, it would be nice to see a better interface for
listing classes than a text field.
- I have to create very explicit/long class names so that it’s clear what they
do to Web editors that don’t know what CSS is. It would be nice I could use
“normal” class names and then associate a display name / label for the Web
editors to see for each class.
http://support.hannonhill.com/browse/CSCD-5169
- Global vs. groups vs. targets: While it’s useful, it would be nice to see it
-
13
Decrease Interval Between Checks for Publish Jobs to Publish
Currently when I add something to the publish queue, I have to wait up to 31 seconds before the publishing process starts. If I edit 50 pages a day in average, and publish each page 3 times in average (making sure it looks good and fixing the way it looks), that is 3 × 50 × 30 seconds = 4500 seconds = 75 minutes of wasted time a day.
I know that a publish queue check slows down other Cascade Server’s processes, meaning in slows down entire Cascade Server and increases the database traffic, but I believe that this check should be done more often anyways. To balance it out, other checks could be done less frequently. Here are the current values:
- publish queue check – every 31 seconds
- workflow expiration check – every 10 seconds
- workflow step escalation check – every 12 seconds
- internal recycle bin cleaner – every 63 seconds
- internal recycle bin processor – every 62 seconds
- login destroyer – every 45 seconds -
13
Structured Data Field Progressive Disclosure
Continuation of the following feature request:
http://support.hannonhill.com/browse/CSNEW-113
This would allow for values chosen in certain data definition fields (in the edit form) to determine whether to show/hide other fields in the same data definition. -
13
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.
-
12
"Apply to children" checkbox on the "Edit" tab of an Asset Factory container.
Duplicate of http://success.hannonhill.com/cascade-server-ideas/apply-children-checkbox-edit-tab-asset-fact
It would be nice to have an "Apply to children" checkbox on the “Edit” tab of an Asset Factory container to ease the application of certain groups to certain or all Asset Factories.
-
12
Ability to publish when modified
When you edit an asset that affects other pages it would be nice to be able to easily publish the pages that are affected by the change. The ideal solution would be to implement this for all asset types. It would be great if you could deselect certain pages to be published and choose the targets/destinations as needed.
Blocks already keep track of pages (and configuration sets) use them. It could be useful to just have a way to publish all pages that use a certain block. -
12
Allow Administrators to customize Help menu
Add a way to change/add links to the Cascade Help menu to point to organizational documentation.
This idea originated as an issue in our JIRA. -
12
Give External Link assets the option to be Referenced
This would allow users to have all of their external links in one location and be able to include them in multiple menus. When they had to update an external link’s URL, they would also be able to do this all in one location.
Currently if a user wants an external link to be included in multiple sections (such as different menus), they have to copy it into the various folders. If that link URL later changes, the user will need to go to each individual folder and change the URL on each external link asset. -
12
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) -
12
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)
* Note - To input code samples, click the pencil icon (this will remove the WYSIWYG) then be sure to start and end code sections with @@@ (three '@' signs). For more information on textile markup, click here.
