https://discord.umbraco.com
Join Discord
j
If you haven't seen it already, v14.0.0-beta002 dropped yesterday. There are a few breaking changes on both server and client. We are going to summarise them on the Our releases page, but feel free to dive in to the Github release notes: https://github.com/umbraco/Umbraco.CMS.Backoffice/releases/tag/v14.0.0-beta002
w
Thats todays lunchtime then...
@Jacob Overgaard is this only NPM of the backoffice release or is there the C# nuget side of things coming as well ?
j
both are out
w
Does the server side gang have a nice release notes page to read whats changed ?
j
It's coming
but here's the preliminary list: These PRs are marked as breaking for the management api since Beta 1 https://github.com/umbraco/Umbraco-CMS/pull/15892 - Revoke previous sessions when AllowConcurrentLogins is false https://github.com/umbraco/Umbraco-CMS/pull/15890 - Extend IContentEntitySlim https://github.com/umbraco/Umbraco-CMS/pull/15891 - Remove Keep Alive Job https://github.com/umbraco/Umbraco-CMS/pull/15887 - Workaround for failing entity tree children https://github.com/umbraco/Umbraco-CMS/pull/15862 - Removed "type" from tree item response models https://github.com/umbraco/Umbraco-CMS/pull/15856 - Remove duplicate pagination helper
w
Thx - nothing of concern for me at first glance
j
I think (hope) this release can be summed up as: Now even more stuff is working
r
SHould media save work on this release since I still get errors?
j
More or less, but would be interested in hearing what you experience. Feel free to create an issue on the tracker as well: https://github.com/umbraco/Umbraco.CMS.Backoffice/issues
r
Maybe it was because I didn't add the media filename https://github.com/umbraco/Umbraco.CMS.Backoffice/issues/1459
added 2 more
j
thank you so much, @Richard Soeteman ! I know how hard it is to know what is supposed to work and what is still being built, but you running into these issues shows us what we should focus on asap
w
Upgrading the test/sample site to beta002 from Nuget and getting this error
Copy code
Could not find a part of the path 'C:\Users\warren.buckley\.nuget\packages\umbraco.cms.staticassets\14.0.0-beta002\staticwebassets\umbraco\backoffice\packages\core\property-editor\uis\collection-view\config\bulk-action-permissions\property-editor-ui-collection-view-bulk-action-permissions.element.d.ts'.
Just me ?! https://cdn.discordapp.com/attachments/1219937745124855869/1220362776476782642/image.png?ex=660eaa67&is=65fc3567&hm=7694b40da90cd9203550e3398fe75ff9020977d4c22aba7c38de9e0ec9b97686&
@Kevin Jump you encoutner this at all ?
So a dotnet new is fine, only an upgrade of the exsiting site/project does it fail and refuse to. FYI @Jacob Overgaard
j
that's already on the tracker
w
For both things on not being able to upgrade the site too @Jacob Overgaard ?
j
No, but the site upgrade worked fine on my test site, so couldn't tell you what it was
but safe to say upgrades between betas could be funky due to the changes in migrations, that will only run from V13 -> V14 as well
This path 
C:\Users\warren.buckley\.nuget\packages\umbraco.cms.staticassets\14.0.0-beta002\staticwebassets\umbraco\backoffice\packages\core\property-editor\uis\collection-view\config\bulk-action-permissions\property-editor-ui-collection-view-bulk-action-permissions.element.d.ts
is longer than the infamous 260 characters (limit for Windows), so most likely you were running into a process having trouble indexing the files, but you installing fresh from Nuget ensured your system didn't have to touch that file...?
If that is the case, then that's also on the tracker
r
Updated to beta2 fewe days ago and now my project can't find references anymore? Could not find a declaration file for module '@Umbraco-cms/backoffice/external/lit'. my goto npm-install/update doesn't work 😦
j
Check that you installed the package from MyGet and it didn't fall back to npm, @Richard Soeteman
Unfortunately npmjs.org has some old versions of the backoffice package and we can't remove them
r
Ok will check that
j
if in doubt, always append the 
--registry
option even when updating a package, or alternatively place a file called 
.npmrc
next to your package.json file and put in the following content:
Copy code
@umbraco-cms:registry=https://www.myget.org/F/umbracoprereleases/npm/
that will ensure any package installed from the @Umbraco-cms namespace comes from myget
r
Thanks that worked little combo with Kevin his snippet npm install --force --registry https://www.myget.org/F/umbracoprereleases/npm/ -D @umbraco-cms/backoffice@14.0.0--beta002
w
@Jacob Overgaard do you know the issue number/link thats on the tracker so I can read/follow along. I can't seem to find it
Bloody hate computers at times - done nothing different and this morning it works
j
w
Ah OK don't think thats the issue @Jacob Overgaard as I have already set the max length thing previously. But weird how it has resolved it for me this monring 🤷
j
We have seen the issue occur even though you have set the registry correct
w
I think it was fine in the end for me, but thanks for the update
j
cool 🙂
w
As we are in the Beta002 thread. Any news of next beta ?
j
Now, now, you already asked this question for the packages time later today 😄
w
hahaha 😛
Well you never know may have got a sneaky answer early
j
We aim to get one out before RC, so probably mid next week
w
OK thanks will keep my eyes peeeled
PreviousNext
Powered by

Umbraco

A hub and casual space for you to interact with fellow community members and learn more about Umbraco!

Powered by