Please submit your ideas on how to improve Cascade Server.
-
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. -
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.
-
15
"Save as Draft" for new assets
Add “save as draft” button for assets that are in the process of being created.
Currently, this functionality only exists during edits of existing assets. -
2
"Super" Index Block
It would be nice to have another type of index block (or an option within the current index block) that would ignore the “Include when Indexing” checkbox. This could be useful for administrators.
Use Case:
I use an index block on the root of a site to generate an RSS feed of all pages updated in that site. However, for one reason or another, some areas have indexing turned off. If I was able to override that, I could see all changes made anywhere in the site.
I think there would be other uses, but that’s the one I can think of. -
7
"Tags" Dynamic Metadata Field
It would be really cool to have a “tagging” metadata field type or a dropdown that also had a text box to add items. That way, users could add categories as needed, but would still receive a list of all existing categories. The interface could be like the search autocomplete or more like a traditional drop-down menu.
-
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). -
4
1 free user designated for Cascade Tech Support
We have a limited number of licenses and it would be nice to have 1 free user designated for Cascade Tech Support.
-
3
@definition-path attribute in structured data
When using the render-content-depth feature of a data definition, it would be really useful for the @definition-path attribute to be returned for included pages. See this message for an example:
I have a data definition containing other assets that I call “related-content”. The referenced assets may use various other data definitions. I would like to present the assets as a list of links with different icons depending of the associated data definitions.
With index blocks, I get the definition-path attribute on the system-data-structure element which I can use to determine which data definition a page uses.
Pages referenced inside a data definition appear as related-content elements with a system-data-structure element however that element does not have the definition path attribute as it would via an index block.
Any idea if it’s possible to get the information I need or some other way to determine what data definitions are associated assets referenced in a data definition? -
16
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. -
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.
-
7
Ability to Add metadata to References
It would be nice to have a feature that allows you to add metadata
to a Reference. The metadata set will still be inherited, but the
values could be editable.
An example of where we would use this is when generating a dynamic left nav via xsl. Each item in the nav uses the ‘Display Name’. Sometimes it is desired to use a Reference to have a navigation entry that links to a page in another part of the site. It would be nice if that Reference could have a different ‘Display Name’ than the page it is referencing. -
1
Ability to limit file extensions allowed in the system.
One idea I feel would be beneficial is the ability for site-level and system-level administrators to define the file extensions that can be uploaded. The extensions could be entered into a text input field as a comma separated list. The field can be left empty to signify allowing any type of file extension to be uploaded.
-
8
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”.
-
8
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. -
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. -
5
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. -
21
Ability to Supply Different TinyMCE Configurations
This is a continuation of the feature request located here.
Would like the ability to have control over:
* buttons
* content validation (allowed/disallowed content)
* plugins
Buttons
Allow control over which buttons can be used in the WYSIWYG editor.
Content Validation
TinyMCE has a right language for disallowing/allowing certain types of contents that could be used, for example, to enforce XHTML strict content in the WYSIWYG if the user so desired or even a smaller subset of a just a few tags/attributes.
Plugins
Allow arbitrary plugins to be included.
This one is a really tough call, because there are tons and tons of plugins out there. The support implications are the main concern.
Solutions
The easiest mechanism for doing this would be to allow CMS administrators to supply their own JSON object containing the configuration of TinyMCE that is passed when TinyMCE is initialized. However, Hannon Hill would need to figure out its support policy with respect to various configurations as there is a high risk of crippling the WYSIWYG or causing significant behavior changes -
1
Abstain votes in idea Exchange
Simple example: An idea has a score of 4 votes. I vote for it, so now it has a score of 5. After further reflection, I decide I don’t want to vote for it (it doesn’t meet a need for me). My only option (besides leaving my positive vote in place) is to vote against it, which not only removes my positive vote, but adds a negative vote in its place – resulting in a score of 3 in this example.
I suggest having a 3rd option between thumbs-up and thumbs-down that basically un-votes for me on this idea (just as if I have not yet voted).
This new icon might also indicate that I have voted already, which would be useful as I tend to “discover” ideas again, only to notice the score is unaffected by my new (repeat) vote. -
25
Add "date" version of "datetime" field, add both to Dynamic Metadata
I love using the “datetime” type on Data Definitions, but I find myself using it a lot when I just want the date part of it, and not the time part. Add a “date” type that just has the date function.
Also, give the ability to add “datetime” and “date” to Dynamic Metadata so we can have a differently-named date/datetime field in the dynamic metadata (without having to use “Start Date”, “End Date”, or “Review Date”).
-
7
Add 'Date' option to publish sets
This is a continuation of the following feature request:
http://support.hannonhill.com/browse/CSNEW-83
Currently, publish sets provide the option for assets to be
published at a certain time each day. It would be nice if users had the ability to set a certain date in
addition to the time. For example – publishing a publish set on the 15th of every month.
* 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.
