Please submit your ideas on how to improve Cascade Server.
-
0
Send email notifications from a valid domain
Hi Folks, Please be aware that your sign-up & password notifications are going out with the invalid return-path-email-addresses – anonymous@compute-1.internal & root@compute-1.internal . As “compute-1.internal” is NOT a valid domain within DNS many, many anti-spam systems will automatically reject your notification messages. If you wish to improve your deliverability rates, please use a valid domain name to send out your notices… And/or monitor your delivery bounces… ;)
Regards,
Steve Phifer
University of Missouri Email Administration -
0
System File Name Settings
We’ve realized that our CMS has been crashing / not publishing pages due to the fact that our users are accidentally using trailing spaces in their system names. We know that we can’t stop human error from occurring. We also realize there is a File Limit plugin for assets, however, we have 100s of assets that we’d have to set up individually for these parameters which seems like a monotonous waste since they’d all have the same settings. Could settings like this be included in Preferences under Content? Has this already been done in a newer version?
-
0
Targets and CSS
I am ending up with too many targets – and it’s becoming unwieldy. Most of these are the same, but only differ in the CSS file that is attached. Would it be possible to decouple the CSS from the target – maybe adding it to the template or configuration file – that seems to be where it belongs since it is a design element.
-
0
Update asset (image) via WYSIWYG
It’s not unusual to suddenly realize how many dependencies may need updating until being hip-deep in the middle of an edit on a page. Of course, I can upload a new image asset without leaving the page I’m editing, but I could see the value of being able to actually select an image and then have the option to “upload to” the asset a new file — essentially editing the file without leaving the page I’m working on.
-
0
Workflow by asset types
It’d be nice if Cascade can kick off workflow based on asset types and file types.
Use case: you only want to review .html pages via workflow, but not images, xls, pdf files etc.
-
0
WYSIWYG Links to other asset types
Can there be a way to do internal links to other assets other than pages? We have a client that needs to link to other assets that are in the WCMS such as PDFs, Word Documents, etc. Possibility a “document type” chooser for the asset browser?
Example: -
-1
Add ability to assign/unassign page-level Data Definitions to Roles
Currently any user than can edit a page can also modify whether or not its using a Data Definition (assuming it does not use a Content Type). This ability should be restricted via the Roles.
This idea originated from an issue in our JIRA. -
-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.
-
-1
Create a Cassandra interface for Cascade
As you know, scalability is a huge issue for content management applications. Providing interfaces to lightweight, scalable DB solutions (like Cassandra and other noSQL solutions) would allow a broader, more automated deployment of Cascade in cases where scale is a limiting factor.
-
-1
Inline Metadata Indexing Option
When creating an index block, it would help to have the option to index Inline Metadata as a checkbox under “Indexed Asset Content”.
Having to retrieve “Regular Content” to get at metadata seems counter-intuitive and it seems like a lot of overhead to get at what should be small bits of information. -
-1
Knowledge Base Plugin
We have a need to create a knowledge base for our cascade site, but need to control categories, type and the ability to import different types of media resources.
we can create a pile of folders and put pages in them but it doesn’t standardize the process into something that can become constant (i.e. locked/controlled category pulldowns – standard form for submitting ideas, etc)TIA, -
-1
Permanent Page URL
It would be nice to have permanent URLs for pages in Cascade so when the pages are moved to different folders, the URLs will remain the same. <br /> </p> <p><span style=“font-size:12pt;font-family:”TimesNewRoman",“serif”;color:gray;">
-
-1
Preview Site? Not Just Page?
Is there no way to just browse the site before publishing? There’s no way to see all the publishable assets at once?
You have to go to each and every page and then click preview, then you have to go to edit > system to find out if the page is publishable or not.
It is imperative to be able to preview the site before publishing!
-
-2
Administrators need to be able to search by file size
To keep the databases to a minimum, administrators should be able to search the system by file size. This would help the administrator to identify users that need additional training.
-
-2
Allow for attribute ordering in "meta" tags
This is a common request with clients.
This idea originated as an issue in our JIRA. -
-2
Providing more support for .Net users in CAST
I’m very impressed with all the items in CAST but am very disappointed that the majority of them are for PHP only. It’s too bad that .Net is not as highly supported in this area. I would love to implement some of the things in the CAST library but can’t.
-
-3
Web-based chat with other users logged into Cascade
Add a chat functionality similar to Google Docs where you can chat with other editing the same asset, or just logged into the system at the same time.
Jabber/XMPP is the first protocol that comes to mind. I haven’t looked into it too closely, but there are a few open source Java options that could be used:
http://www.tigase.org/
http://www.igniterealtime.org/projects/openfire/ -
-4
Get "Published Size"
I would like the ability to get the size of a folder before it is published. to a web server -
-4
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.
-
-5
Add LaTeX support for TinyMCE
There is a LaTeX plugin available for TinyMCE that would be quite beneficial to have within Cascade Server.
* 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.
