Today, we’re releasing Concerto 2.3.3. The main change in this release is a fix for the image rotation issues we’ve had reported to us that were causing images to display much more often than expected. This release also contains a number of bug fixes for how we handle large images, group membership, and the list of screens. Those installing from source should also know that because of updates to Rails and many of our gem dependencies, Ruby 1.9 is no longer supported. Concerto is now tested on Ruby versions 2.0.0 through 2.3.0.
Shortly after releasing 2.3.0, we found a few shortcomings, the biggest being that assets from an upgraded frontend plugin weren’t getting updated (resulting in blank screens) and that some users had their core Concerto version out of step with their content and frontend plugins. After we made a few complex and interdependent changes amongst Concerto and the various core plugins, we decided to go to version 2.3.1 to avoid further issues. In the future we intend to also disallow the installation of plugins not compatible with older versions of core Concerto.
With the release of 2.3.1, we have fixed the asset updating issue, Github API overage errors, some minor security issues, and a variety of other tweaks. We’ll also be making some basic upgrade instructions available to those running older versions of Concerto in the 2.x series to get up and running with the new frontend. For those running into any issues, please remember to stop by our community mailing list for help – firstname.lastname@example.org.
Today’s release of Concerto 2.2.5 will likely be the last in the 2.2 series. It comprises a large contribution to the state of internationalization in Concerto, CSS to remove the cursor from the frontend, and numerous bugfixes. This is thanks primarily to the contribution of code and suggestions from our wonderful user community.
The 2.3 release, which will hopefully be along soon as our team members work to familiarize themselves with the new framework and toolchain we’re using to architect the frontend. Our main priority in this respect will be having a performant frontend that doesn’t leak memory (which has led to crashes on low powered computers) and is feature-equivalent to our previous frontend incarnations.
Hi Everyone! I’m usually excited when we’re announcing a new version of Concerto, but this version has me extra excited. We’ve managed to pack more bug fixes, improvements, and features into our 0.7.0.IndiaIbex release than the previous couple releases we’ve put out. If you’ve been ignoring these updates, or Concerto 2 in general, this is definitely the release to check out. To get started quickly, you should download the latest concerto_server VM here and fire it up to follow along.
This release added some much needed security for screens with the addition of screen authentication. Screen security, something that Concerto 1 lacked, is something we (and by we I mean Mike) spent a lot of time thinking about for Concerto 2. I couldn’t do it justice in this short form, so we’ll dive into the details in a full post after we’ve tidied up the last few bugs.
We also added support for Capistrano-based deployments if you’re into that sorta thing. Our external error-reporting has been fixed in this release so we should get those bug reports automatically streaming in if you’ve check the box during setup. If you’ve tried to visit that settings page and gotten an error, we’ve fixed that as well. The config / settings as a whole should be a lot easier to navigate as well. The VM is properly writing logs now so you can see what’s going on in logs/production.log and the dynamic content updaters are running in the background like they should be. Behind the scenes this release also includes some improvements to our JSON / XML API that we’ll be including in V2, it’s not quite ready for mainstream yet but we’re making progress.
You can find a full diff of the work we did here. Our installation instructions should be up to date, but you should really just download the VM and run it for a fast start. Alternatively, you can check out our instance running this release @ http://nightly.concerto-signage.org. Do let us know what bugs you run into or features you’d like by writing to our Google Group or opening Github Issues.
After a few hiccups along the way (like the mysterious 0.5.0.GolfOtter release), we’re ready to share 0.6.0.HotelHummingbird with you. It’s been over a month since our last release and we’ve been busy at work making the experience a bit snappier and improving the Add Content form. To get started, you can find our installation to get started in our Github wiki.
Since you likely missed out on the 0.5.0.GolfOtter release you also missed a new background processing model which should make Dynamic Content processing much more robust and reliable. Concerto now includes a script to kick off background processing using something like
sudo /etc/init.d/concerto start and manage the background workers just like you would a regular process.
Some notable changes include:
- Textile support in the Ticker Text field.
- Frontend support for subdirectories, like /concerto/frontend/1.
- Slightly better garbage collection in the frontend.
- New background processing model.
- New feed selector, system-wide.
- New templated creation / editing workflow.
- New content creation experience with preview support.
You can find the full list of changes between our last announced release and this one here. Please get in touch with us via our group or issue tracker if you come across a bug or have a feature suggestion for us!