Please submit your ideas on how to improve Cascade Server.
-
20
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. -
42
Unpublish asset when renamed or moved to another folder upon expiration
This idea is a continuation of the feature request located here: http://support.hannonhill.com/browse/CSNEW-77
Sometimes the asset’s end date will trigger a move to another folder
for “expired” content. The asset should probably be unpublished before
it is moved.
The same can be said for assets that are renamed. Currently, when
an asset is renamed, the old asset remains on the server and does not
get unpublished.
-
46
Asset Recycling Bin
It would be great to have a more robust asset recycling bin to prevent users from accidentally deleting items that can’t be recovered by administrators.
-
15
Allow publishing of non-xml pages
Cascade users would like the ability to publish non-xml pages. -
41
Export from one instance of Cascade/ Import to another
Our developers work in our test instance of Cascade which publishes to our test web servers. We would like an easy way to export assets from one Cascade instance (test) so that we would import them into another Cascade instance (prod). We need 2 Cascade instances in order to OS and software upgrades etc -
28
Login as user
I would like the abilty as an administrator to login as a user so that I can check their access -
17
Sites
A Site is a formal collection assets that includes:
- own set of Page Configuration Sets, Content Types, Metadata Sets, Asset Factories, Data Definitions, Publish Sets, Workflow Definitions- NO targets, but a collection of destinations to which assets publish- users/groups members of the SiteSites will allow for:- Roles that are local to that siteTarget properties that will be moved:- Serialization Type (to the Page Configuration)- Output Extension (to the Page Configuration)- CSS Classes/File (to the Site) -
1
Using Secure (SSL) Links to Assets
I have various sites/folders/pages within the CMS that my customers would like to have secure (obviously, I’ll have to work outside the CMS to actually create these secure areas). This means that pages linking to these secure sites must have “https:” in front of the web address – not “http:”, however, I am not currently seeing this possible. I’ve been creating formats to essentially scan through my navigational blocks to change the protocol when I have the keyword “password” in their metadata, but in the average WYSIWYG, there is no option in the link dialog box to make it “secure”. Is there something that I’m missing?
-
3
Assigning Configurations to Destination (Target Functionality in Sites)
It would seem that with the introduction of Sites, it is no longer possible to publish to more than one destination with configuration sets assigned for each destination. Our particular use case here is that we want to publish our site to two servers, one at pomona.edu, the other at m.pomona.edu, and have different configuration sets for each url. It would seem this is currently impossible. Handling mobile friendly content by altering the file name of the url seems to me a clumsy approach, and also introduces other issues like having to rewrite internal links and such.
-
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.
-
6
Check-in/Check-out by default
I’d like to see an option where users don’t have to lock and unlock files as a separate step – editing would automatically lock files, and submitting would automatically unlock them.
-
25
getting around slow publishing jobs
It would be nice if we could pause a big publish job to let other smaller jobs through, and then resume it later.
Alternatively, we’d like to be able to set a “width” on the publish queue, or have multiple queues, so more than one job could publish at a time. -
2
Index only assets that have been published
Add an option to index blocks to only publish assets that have been published, or, better yet, by default only index items that have been published, and offer an option to index assets that have not been published.
-
10
Preview when editing
Currently, if you want to see your changes you’ve made when editing, you have to Submit or Save as Draft. Maybe we can add a “Preview” button that pops up a window with your edits in the fully rendered page.
-
7
Take System Name out of System tab, put above all tabs
I think the System Name is a required field for all assets, but you have to click the System tab to get to it. It would be great if the Name field were always visible, and I could theoretically do all of my editing without having to click through tabs.
-
-1
Asset Factories: first/last option to folder placement position
In addition to specifying a numeric placement position for a new asset, it’d be great to be able to specify it as being placed more generically in “first” or “last” position in the folder.
-
3
WYSIWYG Option Removals Extended to DD Pages
Many (if not all) the pages my users edit are Data Definition pages. As I have certain users I can trust with more access than others on the options within a WYSIWYG, I thought that my giving the DD full access to the WYSIWYG and restricting it at the group level would work, however, this is not the case for DD pages with WYSIWYG. This should be extended to allow more flexibility in the roles (including user specific abilities).
-
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.
-
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. -
24
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”).
* 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.
