We have moved to GitHub Issues
Created by Dennis Aaen 20 May 2016, 14:09:45 Updated by Rune Strand 07 Jun 2016, 14:45:48
If you are configure a MultiNode TreePicker and add a xPath expression, then the xPath will not be transferred to the next environment.
New findings if you are using MNTP at the moment, then it´s required that you add a start node or a Xpath expression
NOTE: Assign the correct Due in version!
I'll do some tests of this along with the other tasks currently in review (probably tomorrow), as it seems no one else is reviewing these (Courier) tasks?
Is this change live yet, I have an urgent need?
@Craig.Stevens the fix is included in Courier 2.52.5 so if your Courier version is newer than this, it should work.
Thanks, but how do you tell what version of Courier is on your particular UaaS?
@craig that's easy, it's called 'you have to guess' - Uaas notifications and news is rather adhoc, and doesn't really give us much room/Time to prepare when updates are deployed. Would be helpful if the update slots were predefined, with a list of what is being updated and changed.
In general There's far too much cloak and dagger, and very little in communication with UAAS as a whole - please don't let me rant about the support service, which is essentially just an 'instant messenger chat', which ironically is rarely instant and has you waiting for 15 mins. Fair play to the guys on the chat, but most seem to need to 'go and ask a dev' to actually answer anything you may ask of them.
I love umbraco - but the 'service' part definitely needs some attention :)
@suedeapple It really requires no guessing at all. You'll get a notification in the portal telling you when your projects have been upgraded. Unfortunately it takes time to go through them all so it might take a while from when you see the first announcements until your project is actually upgraded. You should however not need "time to prepare", as the upgrades done automatically, are only the smaller upgrades with no breaking changes (mainly stability and bugfixes for the Courier bits).
In regards to the support team: They do a pretty good job and resolve a lot of issues every day with high feedback ratings, but unfortunately there's questions you just can't expect a supporter to answer. These have to be escalated to developers to get more insight (or maybe even debugging an issue). There's not much we can do about this, but we do our best to make the process as smooth as possible for you guys. We are however always open for ideas and suggestions on how to improve our processes if you have something specific in mind :)
@Craig.Stevens If you happen to miss the portal notification telling you an upgrade has been done (or you just want to make sure what version you are on) you can always check the version number of the DLL's in the bin folder of your site. That's essentially the easiest way to check, if you aren't sure what version you are on :)
@claus Well, the UaaS upgrade did its automagical patch release, and broke the LIVE site - WHOOP! :D
re:Umbraco Form I don't think a complete change of UX/UI, constitutes as "patch". Our web editors are now confused by the new/look feel, and I'm now having to fire fight emails on where things have moved to e.t.c The company will also need to re-write internal documentation and training guides, as these are using screenshots from the old version of Umbraco Forms. This has proved to be a costly venture to put right.
Sorry for hijacking this thread, but I cant see/find any official means to report frustrations about using UAAS.
@Paul, there's always the forum on OUR, just select "Umbraco as a Service" in the "Categories" drop down and whinge away ;) I just tried the XPath change and it worked between environments. Commits still failed though, had to set a deploy marker in Kudu each time, but didn't have to restart the environments, so that's a small step forward. Just hoping it's because it's the first commit. Hopefully subsequent ones won't fail first time like they always used to.
@suedeapple Regarding support: Sorry to hear this is you're experience with UaaS. We do try to get to the support cases as fast as possible. Sometimes the issues are beyond what we, in 1st level support, can handle and that's why we escalate to the dev team. We are in the process of staffing up, to get our response time even further down. (We are at 40min median including weekends for standard customers, which is pretty good). We are also constantly iterating on the process of gathering information on the support requests we get. Sometimes it can be quite mundane things that are easily solved but actually getting to the understanding of the issue can take up quite some time. I hope you'll see that we are improving in the future.
Regarding Umbraco Forms Update: I agree with you. While there aren't breaking changes in 4.3, the massive UI overhaul should be considered a breaking change because it effects editors in such a huge way. Once they get used to it I'm sure they'll recognise that the experience is vastly improved but that doesn't help with the jarring experience of logging in to your work tool and seeing a completely different UI. One thing we are looking in to is actually letting you choose when these large upgrades are applied (just as with minor version upgrades to Umbraco) See: http://issues.umbraco.org/issue/UAASSCRUM-413
Any and all feedback you are willing to give is much appreciated, be it here, in the chat or on the forum.
All the best Rune
Backwards Compatible: True
Affected versions: 2.52.4
Due in version: 2.52.5
Sprint: Sprint 34
Story Points: 1