I've just added to my task list: don't overwrite grid.editors.config.js during upgrades on UaaS. So you won't have to worry about that. Other than that I haven't tested this myself, but from what I know about this package it should work.
I was writing with Dennis about UaaS and he told me that when UaaS upgrades it will be overwritten, but now you guys are already looking to fix it, thanks! :-)
Can't wait for this to go live, because we use LeBlender on our client sites, and we where looking at UaaS :-)
i know this is old...but it appears that the grid.editors.config.js is getting overwritten on cloud... can't we just leave it as is? i don't see it changing from core for any real reason as it is just the stock grid editors from core, right?
LeBlender and Umbraco as a Service
Hi! :-)
Have any of you tried using LeBlender on Umbraco as a Service?..
Because it edit's the grid.editors.config.js file, but as i understand when Umbraco as a Service upgrades, i will overwrite the file :-(
Looking forward to your answers :-)
I've just added to my task list: don't overwrite
grid.editors.config.jsduring upgrades on UaaS. So you won't have to worry about that. Other than that I haven't tested this myself, but from what I know about this package it should work.Sebastiaan that's great man! :-)
I was writing with Dennis about UaaS and he told me that when UaaS upgrades it will be overwritten, but now you guys are already looking to fix it, thanks! :-)
Can't wait for this to go live, because we use LeBlender on our client sites, and we where looking at UaaS :-)
Does LeBlender work on UaaS now? Don't we need this PR released: https://github.com/Lecoati/LeBlender/pull/30
LeBlender seems to be working on UaaS.
However transferring content data from local to live, when using pickers, will not give the expected result.
Read more here.
https://our.umbraco.org/projects/backoffice-extensions/leblender/bug-reports/80025-picker-data-is-not-translated-from-local-to-uaas
I don't know if the same goes for a staging or live environment, that depends if node id's change between those environments.
i know this is old...but it appears that the grid.editors.config.js is getting overwritten on cloud... can't we just leave it as is? i don't see it changing from core for any real reason as it is just the stock grid editors from core, right?
is working on a reply...