Updating older Umbraco packages

— 4 minute read

In a recent post, I outlined some of the reasons for upgrading Umbraco and how best to approach the challenge. In that post, I mentioned that you are likely to have a number of issues with custom packages or custom data types. Below is a rundown of some of the examples I have encountered. If you have found others, it'd be great if you could add to the comments section and I'll look to edit this post with extra details in the hope that it can become a valuable resource.

Packages permalink

This is basically a list of packages which I have come across via a previous upgrade to Umbraco 7+. Quite a few will have a version that works with Umbraco 7+, others will simply not work. Where possible, I have included a suitable upgrade path.

PackageDescriptionv7 support?Alternative
AttackMonkey Custom Menusused to disable delete/copy/move etc on some content nodes, to idiot proof the CMS (e.g. Stop users deleting the home page)Yes (v2+)
AttackMonkey Tab Hiderused to hide some of the tabs on content types from certain users (e.g. Only admins can edit the SEO tabs)No
AttackMonkey Securitysecurity helper, password strength validationNoMembership provider regex
AutoFoldersused to automatically organise news type content into Year/Month foldersNoDateFolders / uDateFoldersy
CMSImportused to import content from an old CMSYes
Config Treeallows you to view all the site config files in the back officeYes
Contourused to provide formsYes (use latest)
Contour Contribadds some additional functionality to Contour, e.g. RecaptchaYes
DAMPused as a replacement for the built in media picker, as it offers more functionalityNoBuilt in
DocType Mixinsplugin to allow DocType composition in earlier versions of UmbracoSort ofDoc Type Compositions
Embedded Contentallows for repeating content structures within a single pageNoArchetype / Nested Content
FamFamFam iconsadds additional icons for use in the content tree to represent Document TypesNoBuilt in / packages
Google Maps for UmbracoData Type that allows the selection and rendering of Google MapsNoAlternative packages available
ImageGenallows image resizing and compressionYesImage Processor
Mass Replacerbulk find and replace actions for Umbraco back office, occasionally used when site wide brand names need standardising etcMaybe
Media Iconsdisplays file type icon rather than the built in ones in the Umbraco media libraryNo
Open Calais Autotagcan be used as a replacement for the tags data type in earlier versions of UmbracoNo
Path FixupThis is a developer dashboard control to fix database issuesN/aFixed
Repeatable Custom ContentA datatype which allows adding repeatable custom contents/child nodes.NoArchetype / Nested Content
Robots.txtallows you to view the robots.txt file for the site in the back officeYes
Structure Extensionsallows you to set default Document Types for child pagesMaybeBuilt in
uComponentsused for various additional Data TypesNoBuilt in
Yoyo CMS Tag Managera plugin that adds an additional section to the CMS allowing you to visually view and manage all of the tags used on the siteYes (v3+)

Data Types permalink

Ok, so this one is more of an extension to the packages section above, but I figured it'd be useful to separate the two.

Property Editorv7 support?AlternativeConversion
DAMPNoBuilt-in media picker
Embedded ContentNoNested ContentManual
Form PickerYes
Google MapNoPackage
Short URL FieldNoTextbox?
uComponents: Multiple DatesNoPackageManual
uComponents: Multi-URL PickerNoRelated LinksManual
uComponents: URL PickerNoURL PickerXML to JSON
XPath DropDownListNoMNTP

As mentioned before, this is by no means a complete list but should offer some guidance for others who come across a similar task. You might have an existing site or customer who uses some of these packages and been holding off an upgrade. It's easy enough to figure out what the outcome of such an upgrade will be, so I'd say give it a go and figure out what breaks (if anything).