Umbraco CMS version 7.1.7 (unexpectedly) released
Umbraco HQ has just released a new maintenance patch for its gem of a CMS. As of this new version 7.1.7 (and 6.2.3 if you refuse to take the leap to v7) two issues have been addressed.
A big bad memory hog
One of the things I had just accepted in working with the Umbraco CMS these past many years, is that it’s just a bit of a hoover when it comes to memory usage. We’ve banged our heads together over here trying to identify the issue(s) that cause this to happen, going back many versions, but never really discovered much. The CMS has always been a bit of a black box, though it’s much better as of late.
Luckily, the Umbraco team have identified an issue with their usage of PetaPoco, a lightweight .Net ORM. Shannon Deminick has written up an explanation of the issue PetaPoco can cause high memory usage with certain queries and how they’ve addressed it in this latest release.
I’m keeping my fingers crossed on this one. We’ve just upgraded a couple of our client sites and are monitoring.
Issue documented here: Update PetaPoco to expire it's unused mappings in memory.
My start node is playing hard to get
This is the smaller of the two issues, but it’s good to see it resolved.
When a user’s start node is set further down the content tree, they weren’t able to actually see and edit the starting node, only the descendent nodes. It wasn’t really a deal breaker, but it was very annoying. I have sub trees on a few of my projects that I restrict certain user types to, and when those nodes went missing during an update (7.1.6 I believe), a bit of scrambling was done to work around it. Now, undo the workarounds o_O.
Issue documented here: User with start content set won't see the selected node.
Alright, get out there and be sure to update your Umbraco CMS instances, totally worth it.
