Tomorrow, June 4th we will be updating Cascade to the newest version, 7.2.2. We plan on getting Cascade updated at 8:00am and the downtime shouldn’t be any longer than half an hour. This release introduces some new functionality as well as tons of bug fixes that have affected Cascade’s editor.
- When editing, Cascade now autosaves drafts to prevent you from losing work. You can also discard unwanted drafts at the top of every view or edit screen.
- The site dropdown is now a type-ahead search field, a welcome change for those of you who have access to a lot of sites.
- The editor has been updated, which should alleviate frustration when pages stop behaving as you intended.
- You can now drag and drop assets in the Navigation Page. On our CMS help site, you can see it in action.
If you would like to read the patch notes for the new version, you can see them here: http://www.hannonhill.com/kb/Release-Notes/7.2/index.html#release-summary
We have taken great strides to get Cascade to run faster as of late, and this new version should run a little more smoothly as well.
We will be rolling out version 7.0.7 of Cascade this evening, starting at 5:00pm. Downtime is expected to be an hour. There’s a bunch of new features, including massive speed increases which should help the slowness we have been experiencing.
- Index block caching: The navigation and other ‘automatically generating’ assets in Cascade use ‘Index Blocks’ to accomplish what they need to do. Now this operation will be much quicker, meaning that pages being viewed in Cascade, publishing and other tasks should be anywhere from twice to eight times faster, depending on what Cascade has to do in the backend.
- Type ahead search when linking to assets: Now when you’re trying to link to a page you can do a search for that asset without having to manually browse for it.
- Asset browser is no longer a pop up window: The asset chooser window will no longer get lost behind other windows on your computer, and will work more reliably in older versions of Internet Explorer.
- Unpublishing assets more easily: When moving or renaming an asset, Cascade will now ask if you want to unpublish the asset so what’s on the server isn’t out of sync with what’s in your CMS site.
There are also number of new features that are less forward facing that you can read about here: http://www.hannonhill.com/kb/Release-Notes/7.0/index.html
– 1/22/13 edit – Cascade performance seems to be stable.
For the past week (January 14th until January 18th) Cascade has been running very slow, and I’d like to give some background on why it is happening and let you, the users, know what we’re doing to fix the situation.
First, I apologize for the glacial pace that Cascade has been moving for the past few days. We pride ourselves with keeping the CMS running smooth and as stable as we can get it, and the last week has not lived up to the expectations that we set for ourselves.
We were attempting to get basic analytics, provided by Google Analytics, onto all the sites hosted by us (sites that publish to the umt.edu servers.) This would have allowed users to see analytical data from inside Cascade. Some sites already have this functionality, but it was limited to set of people who requested it.
Since we had a number of sites using this feature and it was working great, we started rolling it out to all sites under our jurisdiction. Once we had it all configured, Cascade began having intermittent issues with its performance. Since then, we’ve removed the analytics connectors from the sites we put then on earlier this week. It is still on our to-do list to get this data into Cascade, but not until a deployment of this scale is thoroughly tested and we are satisfied with the performance of the application.
Our current plan is to let Cascade work through what it’s trying to execute over the long weekend, and see if performance goes back to acceptable levels and then go from there.
Thanks for your continued patience.
Application Support Specialist
Web Technology Services/Information Technology
On the morning of Wednesday, May the 23rd, we will be going live with our new server environment. For sites that are currently publishing to our production destination (www.umt.edu/SITE_NAME), all of the content in your site(s) will be automatically published to production at this time.
Please make sure that on May the 23rd, all of your content is ready to go live.
The http://staging.umt.edu server is configured the same as our new production environment. You should publish your site to the staging destination and then take a look at your site on staging. To access your site on staging visit http://staging.umt.edu/SITE_NAME, for instance if your site is http://www.umt.edu/my_site your staging location would be http://staging.umt.edu/my_site.
If you have direct file system access to your site and have been manually placing files on the webserver (without using Cascade), please contact us at email@example.com. We are discontinuing this practice for our main webserver and on May 23rd you will no longer have this access.
Please let us know if you have any questions or concerns at firstname.lastname@example.org..
We will be performing a server migration for Cascade on Wednesday, May 2nd from 5:00pm until 7:00pm. Cascade will be unavailable during this time.
Firefox 12 fixes this issue. Please update your Firefox if it hasn’t already.
For users using Firefox 11 (newest version,) there is a bug on the edit screen where the first editor on a page with multiple editors shows no content. Do not worry, that content is still in the system, but there’s a bug with displaying it.
If this bug is affecting you, please use another web browser for the time being. Because of the widespread nature of this bug, it’s possible that Mozilla will patch Firefox to fix this bug. We’ll send out an update when this issue is resolved.
For more information on this bug, please see:
Cascade will be updated to version 6.10.7 on Saturday, January 28th at 10:00am. Because there are significant changes to the Velocity Engine, we will have to fix most scripts in the system. Because of this, Cascade will be down longer than normal. We estimate that it will take 5 hours to fix all the scripts.
We ask that during the hours of 10:00am until 3:00pm on Saturday, January 28th users remain outside of Cascade to minimize the amount of pages that get published in a broken state. We will put an “all clear” message out on this blog when we are finished updating the scripts.