so, i am guessing this doesn't work on the Cloud, but i was just wondering, why? not in an overly technical way, but when you clone the site, the config files look to live in same place, etc. So was just curious as for the most part with the small, one-environment sites this is the only reason why i need to copy down and use source tree, etc. Thanks for any insights.
I've used this package for viewing the configs on a 7.5.8 site on the cloud with no issues. I can't say that I tried editing anything, however but I think you might struggle to edit web.config but the others should be fine.
Although I haven't used it on Umbraco Cloud myself, I would expect that every config file edit would result in a new commit to the Git repository... and any updates to the Web.config would create a backup copy it, thus committing new files to the root of the website.
It's not a huge problem, unless if you have OCD (like me) and want to keep commits/files to a minimum. Otherwise should be all good! :-)
We use Config Tree on all our Umbraco Cloud sites and we love it! However I can confirm that while this works for us in both Live+Stage+Dev enviroments, but as Bob mentions, it doesn't work when you clone the site locally. See image (this happens no matter which .config file you click):
It works locally however if you install the package locally and then push it to Dev/Live. However when you or any of your collueges clone down the project, this same error occurs.
This has however never been a big problem for us since the reason we use this package is to be able to do quick fixes (bumping CDF version etc.) from within our Cloud projects whitout having to go to Kudu. When we actuall have our project cloned locally, there is not reason for us to go through the backoffice to do .config file fixes, when we can do them directly in Visual Studio.
(Btw, if it helps, this was tested on a 7.5.9 site.)
Hope this information helps. And thank you for a great package!
I also got a HTTP 404 error when clicking any .config file.
In my case I had renamed the /Umbraco folder (for additional security)prior to installing the Config Tree package. The package installation did not respect my change.
Once I moved the Config folder to the appropriate location under my newly named /Umbraco location, all worked as anticipated.
umbraco cloud?
so, i am guessing this doesn't work on the Cloud, but i was just wondering, why? not in an overly technical way, but when you clone the site, the config files look to live in same place, etc. So was just curious as for the most part with the small, one-environment sites this is the only reason why i need to copy down and use source tree, etc. Thanks for any insights.
Hi Bob,
It's been a couple of years since I used Config Tree, I don't see any reason why it shouldn't be working on Umbraco Cloud sites.
Are there are any errors visible? (YSoDs or in the browser dev tools console)
Unless if the package doesn't work in latest Umbraco (v7.5.9)? Hopefully someone else could verify that too.
Cheers,
- Lee
I've used this package for viewing the configs on a 7.5.8 site on the cloud with no issues. I can't say that I tried editing anything, however but I think you might struggle to edit web.config but the others should be fine.
Nik
Although I haven't used it on Umbraco Cloud myself, I would expect that every config file edit would result in a new commit to the Git repository... and any updates to the Web.config would create a backup copy it, thus committing new files to the root of the website.
It's not a huge problem, unless if you have OCD (like me) and want to keep commits/files to a minimum. Otherwise should be all good! :-)
We use Config Tree on all our Umbraco Cloud sites and we love it! However I can confirm that while this works for us in both Live+Stage+Dev enviroments, but as Bob mentions, it doesn't work when you clone the site locally. See image (this happens no matter which .config file you click):
It works locally however if you install the package locally and then push it to Dev/Live. However when you or any of your collueges clone down the project, this same error occurs.
This has however never been a big problem for us since the reason we use this package is to be able to do quick fixes (bumping CDF version etc.) from within our Cloud projects whitout having to go to Kudu. When we actuall have our project cloned locally, there is not reason for us to go through the backoffice to do .config file fixes, when we can do them directly in Visual Studio.
(Btw, if it helps, this was tested on a 7.5.9 site.)
Hope this information helps. And thank you for a great package!
Dennis,
I also got a HTTP 404 error when clicking any .config file.
In my case I had renamed the /Umbraco folder (for additional security)prior to installing the Config Tree package. The package installation did not respect my change.
Once I moved the Config folder to the appropriate location under my newly named /Umbraco location, all worked as anticipated.
Heath
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.