Please submit your ideas on how to improve Cascade Server.
-
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.
-
6
eliminate duplicate queued publisher jobs
It would be nice to not have duplicate jobs “stack up” in the Queued Jobs. I believe this would result in a significant reduction in publisher delay. I’ve seen two main cases where this type of backup can occur: (1) if I have a Publish Set (“Hourly”) scheduled to publish every hour and a large publish job takes 3 hours, 3 “Hourly” jobs will be queued up, and (2) if someone is editing several files in a folder with a workflow that publishes a Publish Set, one Publish Set will be scheduled for each file edited.
I would like a check to be added to check the queue for any jobs with the same Publish Set id (same for pages, files, etc.), and if one is already queued, not add it.
I can’t think of any reason why someone would want duplicate jobs queued (maybe someone has extra CPU cycles and bandwidth to burn?), but if there is a reason, a checkbox on the Publish Set definition to limit to only one concurrent scheduled job for that Publish Set would be an improvement. -
5
Option to unpublish when users changes system name or parent folder on an already published asset
When a user wants to delete an asset, the system automatically offers the user to include to unpublish from the web server. There should be the same option showing up when users try to change the system name or parent directory once the asset was published.
This would keep the numbers of old and obsolete files and directories on the web server to a minimum. -
4
Asset Factories: Apply to Children
I’d love to see an “Apply to Children” check box when assigning groups to Asset Factory Containers, like you would when you grant users and/or groups access to asset folders. We create asset factories by department since some of them have unique features or use base assets, and it’s very tedious to apply groups to every single asset factory.
-
2
Simplify process of adding assets to publish sets
One idea that I have for improving the process of creating and editing publish sets would be to provide the ability to add more than one asset (regardless of asset type) at a time during a creation or edit operation. I find it annoying having to submit changes and then starting another edit operation in order to add another asset to a publish set.
-
1
Recycle Bin
I’m not sure if there is currently a way to do this, but I do have users that accidentally delete objects (pages, etc.), and I’m not sure how to recover them except by starting all the way over. Is there some kind of recycle bin that we can dig into for accidental deletions or clean out after a period of time (or manually)?
-
0
Allow for publishing of specific configuration sets to specific destinations
Apparently with the removal of targets in Cascade 6, it is no longer possible to marry configurations to destinations, though this would be a very powerful feature still, so Im not sure why it was removed. Specifically, I want to be able to create mobile site configurations and have those publish separately to our mobile server.
-
0
Create Additional Roles
I love the fact that I can edit roles but I would like to be able to create my own roles to get more granular with permissions
-
0
More Flexible Targets & Destinations
I am using the exact same template, but I am publishing files to different sub domains, which is requiring me to make a copy of that template instead of just referencing it and declaring a new destination. This should be an option available on folders, etc.
* 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.
