Umbraco Cloud Portal offers a powerful baseline-child relationship between projects, similar to a fork (forked repository) on GitHub. With this feature you can create a clone of an existing project while maintaining a connection between the two projects.
If you at some point want to break this connection, between the baseline and one child project, you can do so now. Users with the role of admin are able to break the connection.
Please be aware that the action cannot be undone.
Break reference between baseline and child project (1)
You are now able to access a simpler project overview page for each of your projects. Initially, you can see basic information such as name, alias, plan and project status. In the future, we will likely add more project-related information that currently is not presented in the portal.
New Project Overview Page
When inviting a new team member to a project it is now possible to specify the project roles directly in the project invite. Often you want the team member to be assigned a different role for each environment. This is now supported from the start of the project invite. A user can now be assigned the Admin role in the development environment while being limited to the Writer role in the Live environment. All helping to make it faster and easier to set up the correct permissions for team members.
We have reworked a couple of the criteria that triggers notifications for an available upgrade. Now you will get a notification on Starter projects without a development environment as seen below.
Another change is that the upgrade banner will no longer be displayed on projects with one or more environments already upgraded.
The Create new Cloud project wizard has in the last weeks undergone some performance improvements. The most significant of these is the loading of potential baselines for users with more than 50 cloud projects. Previously this could be time-consuming, this has now been updated to loading asynchronously.
We have ensured that the potential baselines are loaded much faster to ensure a better user experience. This reduces the time wasted before you can start working on a new cloud project.
The blob storage connection information for a project was previously only displayed in Kudu which was not convenient or easy to find. A developer should spend as much time as possible developing fantastic solutions and less time in Kudu. Therefore this connection informantion is now easy to copy directly from the portal and ready to post into Azure Blob Explorer whenever needed.
The project invitation flow in Umbraco Cloud Portal has until recently suffered from invites ending up in the invitees' spam folder. We have optimized the configuration of the portal email delivery so every invite will now be delivered to the expected receiver - in the correct inbox.
However, there can be exceptions where an email is either bounced or lands in the spam folder. In such cases, a resend of the project invitation might not do the trick. In rare cases, when the email doesn’t show up, we have added the option to copy the project invitation link for active invites.
We added new team members to the Cloud Feature team to support our strategy of making Umbraco Cloud the best way to host Umbraco solutions. We will continue our customer-centric development with an increased focus on input from partners and portal users, improving existing functionality, and creating new exciting features.
In order for agencies and users to keep up with the improvements, we’ve made it easier to find the latest release notes. You can now find the link for the release notes in the profile settings menu. Release notes will be published multiple times each month and list the most relevant fixes and features added to the portal.
During December we have provided a lot of small improvements to the Umbraco Cloud Portal. Too many to mention, you can find a few of the highlights in the list below.
- Alignment and consistent order of product versions on the project page.
- Confirmation box for restarting environment (to avoid accidental restarts)
- Required technical contact details for projects prior to creation (so every project always has at least one technical contact)
- Alerts in the portal when a profile does not have a phone number or when a project does not have a technical contact associated (contact information is important in case there are issues related to a project or a profile).