I'm currently running a trial of Uno for a new project we're looking at doing for our website. If we purchase the Pro package which has the option for custom code, does anyone know if you still retain the pre-built components?
How is this custom code handled as part of Uno?
We want to retain the drag/drop capability of building pages for our content teams but need to be able to use custom code for certain features and functionality of the website that isn't standard? e.g. Name/Location lookup via API.
Also, has anyone ever run Uno for core site pages and then used Angular built pages alongside and run in to any issues?
Happy to see you want to upgrade your Uno project :)
If you upgrade and enable to custom code you will retain the pre-built components. Everything you have in your project, content, doc types & media will stay with you as it currently is.
Once you enable custom code, your Uno project will act as a regular CMS site in any other ways, so you should be able to expand as you otherwise would within the CMS.
Just on the point of using the custom code and the project will then act as a normal CMS, does that mean that we then need to maintain Umbraco updates etc as we would if we used Umbraco CMS on its own?
Just trying to understand almost where Uno ends and the use of Umbraco CMS as a product begins. If we went for Umbraco CMS, we'd have to build a content interface for users which we're wanting to avoid.
The point of Uno is that you should only be thinking about building content. This means that the CMS, Forms, Deploy versions are not yours to manage, they are handled by us and wrapped into what we call Uno.
Uno does not end for you by enabling custom code. You will be able to upgrade your version of Uno on your project to get latest features and changes. Although I have to emphazise that that functionality is currently not done.
"Please be aware that by enabling custom code you also agree to the following changes in your project and subscription:
You will no longer be entitled to Umbraco Uno support but Umbraco Cloud support according to the subscription plan instead
The project will no longer receive Umbraco Uno related updates
The Sendgrid implementation will be removed, meaning that you will have to manually set up your own mail integration"
If we try out the Custom code options and decide we don’t need them can the subscription be reverted to an Umbraco Uno subscription or would we need to cancel the subscription and create a new Umbraco Uno subscription? If we have to cancel and recreate the subscription how does this work if a payment has been made for the subscription?
If you change to Custom Code, you can not revert it, meaning there is no going back.
When it comes to payment, you will always pay for your project for the rest of the month. So if you created your project on 15 of July, you will pay from 15-31. And then if you create your new project again on 28, you will pay for this project for 28-31 and then again on August 1 for entiry August.
Umbraco Uno - Upgrade to pro
I'm currently running a trial of Uno for a new project we're looking at doing for our website. If we purchase the Pro package which has the option for custom code, does anyone know if you still retain the pre-built components?
How is this custom code handled as part of Uno?
We want to retain the drag/drop capability of building pages for our content teams but need to be able to use custom code for certain features and functionality of the website that isn't standard? e.g. Name/Location lookup via API.
Also, has anyone ever run Uno for core site pages and then used Angular built pages alongside and run in to any issues?
Hi Carolyne.
Happy to see you want to upgrade your Uno project :)
If you upgrade and enable to custom code you will retain the pre-built components. Everything you have in your project, content, doc types & media will stay with you as it currently is.
Once you enable custom code, your Uno project will act as a regular CMS site in any other ways, so you should be able to expand as you otherwise would within the CMS.
Hope this helps. Best, Kristian
Thanks Kirstian.
Just on the point of using the custom code and the project will then act as a normal CMS, does that mean that we then need to maintain Umbraco updates etc as we would if we used Umbraco CMS on its own?
Just trying to understand almost where Uno ends and the use of Umbraco CMS as a product begins. If we went for Umbraco CMS, we'd have to build a content interface for users which we're wanting to avoid.
That is correctly understood.
The point of Uno is that you should only be thinking about building content. This means that the CMS, Forms, Deploy versions are not yours to manage, they are handled by us and wrapped into what we call Uno.
Uno does not end for you by enabling custom code. You will be able to upgrade your version of Uno on your project to get latest features and changes. Although I have to emphazise that that functionality is currently not done.
Sorry for all the questions...one more
The Umbraco Uno Documentation found @ https://our.umbraco.com/documentation/Umbraco-Uno/Custom-Code/ states..
"Please be aware that by enabling custom code you also agree to the following changes in your project and subscription:
You will no longer be entitled to Umbraco Uno support but Umbraco Cloud support according to the subscription plan instead The project will no longer receive Umbraco Uno related updates
The Sendgrid implementation will be removed, meaning that you will have to manually set up your own mail integration"
If we try out the Custom code options and decide we don’t need them can the subscription be reverted to an Umbraco Uno subscription or would we need to cancel the subscription and create a new Umbraco Uno subscription? If we have to cancel and recreate the subscription how does this work if a payment has been made for the subscription?
If you change to Custom Code, you can not revert it, meaning there is no going back.
When it comes to payment, you will always pay for your project for the rest of the month. So if you created your project on 15 of July, you will pay from 15-31. And then if you create your new project again on 28, you will pay for this project for 28-31 and then again on August 1 for entiry August.
Hopes this makes sense :)
is working on a reply...