Have you recently checked out your company’s web presence and thought to yourself that it was in dire need of an update? But then maybe you started imagining the pain of pushing new data there, and resigned at the mountain of work ahead. Or maybe your mind turned to even more pressing problems with the site - maybe it doesn’t render correctly on mobile, or no updates get pushed into social media.
I've been developing webapps pretty much since the start of the web in the second half of the 90s, and in Java ever since the first edition of Java EE. During that time, I've met many people and have seen many different approaches to both the development and the testing of the code.
While parts of the cloud IT that are still being hyped are changing rapidly, the whole segment is not past the hype yet. The cloud report  that Gartner published 9 months ago still holds true today.
Lets start with a small quiz: Can you find 3 differences in the pictures below?
Looking back on a relatively long period of time always makes me nostalgic. I can’t help but turn into a wistful old man, preaching the value of the “good old times”. In Magnolia’s case, fortunately, this is slightly different - there are plenty of things that are still great, and on an even more positive note - they are constantly getting better!
Over the last few years we've been busily writing the latest and greatest version of Magnolia. After all of this focus on new and (we hope) great, it seemed like time to focuse on something old and great.
Atlassian has made some seriously great products, for example the project tracker JIRA. We recently upgraded our rather archaic version of JIRA at Magnolia to the latest and greatest offering. Everyone in the team found something in this upgrade.
Sometimes, life drops a house on your code. Sometimes, it's flying monkeys. Most of the time though, the damn stuff just stops working and it's nothing so obvious as being crushed by a Kansas farmhouse or being carried away by winged primates.
In my last blog post, I explained how to add versioning capability to templates. Being able to create, view and restore different versions of templates is great, but sometimes it's not so easy to see what has actually changed.