https://discord.umbraco.com logo
Join Discord
Powered by
v14.0.0-RC2 released!
# package-development
r
Thought I'd start a thread to capture thoughts
k
Oh.. i have thoughts ....
I've just created every datatype and added it to a document type so you don't have to 🙂 and collected 'niggles' along the way
Data Types. > General - You should be able to click anywhere on the propert editor to open the 'change' dialog (not just the 'change' thing that appears at the end). > Individual types - Radion Buttons, Checklists,Dropdowns - when adding items tab/return should move to next item - Color Picker - The swatch picker should stay open when you attempt to pick a colour (it disapears on click, you can't drag the pointer around. - Tab order (can't tab from hex to label) - Return should open a new colour (e.g add) - Image cropper - on v13 the alias autofills when you enter a label. - hitting return does create but it should put the focus back on label (it stays on last one) - Icon Picker - 🐛 ? throws an error when you save - Upload Field - Accepted file extensions should add on return Document Types - Properties on tabs ? - On v13 (and below) you can add properties directly to a tab, in v14 you have to add them to a group in a tab? - Create Name isn't in focus when new doc type shows up. - Create Folder, box isn't focus (when you select create -> folder, the name box isn't in focus, you have to click on it) - Add Property - Its possible to add a property and click "Add" without giving it a name or alias. - when you then update the label on the main document page it doesn't update the alias. - Re-order - Can't change the number value for a tab ? *Content * - A Failure of one property shouldn't cause the whole page not to load ? currently the checkboxes causea javascript error when they are parsed, but this means you get a complete failure of the page you can't load or edit any of your properties (you effectively loose the page).
---- I don't know if these should be issues, or if they can be classed as general feedback @Jacob Overgaard
l
@Kevin Jump Not to create a bunch of more work for you. I'd say they should all be issues, (prefixing the title with the version number). Thanks for testing all these things out so quickly too! 🙏
r
Every release get's better indeed but with all these errors and just a month before release I would suggest HQ makes it clear to people that things will break in V14. Had chats with a few Dutch companies that would jump on the V14 wagon with projects that have tight deadlines. They think it's just as stable as previous upgrades.
w
I am no commercial package author, but do we think as package dev community that you will be ready with release? Or is this gonna be like V8 where it was released but the supporting package dev community just wasn't ready. Thoughts... ?
k
I think if we are all honest, these aren't 'release canidates' (there are still things to be implemented?). and based on that i would exepect v14 is likely to not be "rock solid" on release.
uSync will be 'ready' day 0. uSync.Complete also aiming for Day 0, Translation manager "release +N " where N is how long it will take to do 🙂
r
I am all with you and we know it, but people outside our bubble don't know
Same here with my products... AIminng for late summer
u
No Preview option when V14 is released is a blocker for us looking at it.
w
Do we think there will be a gap of other packages in the ecosphere? Great that such a popular one as yourself Kev for uSync aims to be Day 0 release
k
i agree there are even post on this discord server where people are considering building sites on v14rc and i don;t thin thats wise.
r
I would treat V14 as a RC for V15 😉 and that is not negative but realistic
w
I know the team is working super hard on this (you can see from the PRs & commits going on), but yeh with about 6 weeks out be interesting to see what gets prioritised
k
Would you coun't most of these as 'bugs' (even when its like the tab order isn't right?)
yes, its not a development thing now, its a marketing thing
r
Not saying the team isn't working hard but people that rely on functionality need a stable Umbraco otherwise deadlines from thier projects won't be met etc...
indeed
l
General stance is that if the feature is the 14 RC, and it doesn't work, then it's a bug. Otherwise it's a missing feature, (so 14.1+), that said, Preview is on our to-do list.
k
back to the release cycle - is there an ETA for permissions - that's my biggest blocker just now.
(or are there in there the UI just isn't?)
w
@Kevin Jump can you see an API endpoint in the main mgmt API from Umbraco ?
k
yeah there does look like there is something there, and the docs has user -> user-permission so there is probibly code.
just have to look at all the core stuff and work it out i guess. cause i need to create and assign permissions in the backend also. and i know the letters have gone
w
Yeh perhaps no UI for it yet
k
usr groups has some UI, just clicking on a node and selecting permissions has none
w
Check to see if the API has been generated or any network requests are made to the MGMT API endpoint that you expect ?
k
yeah it looks like its all managed with.........
manifests !
w
So permissions are manifest and clientside as well?
k
i think so, i am still digging 🙂
I suspect there is something backofficy somewhere
w
Yeh surely the API endpoints must be restircted by the current logged in user making the request to the API and thus need to check its permissions
k
yep - will need to blog when i get my head around it. there are two parts . 1) front end uses manifests to define them :
Copy code
ts
{
  type: 'entityUserPermission',
  alias: UMB_USER_PERMISSION_DOCUMENT_DELETE,
  name: 'Delete Document User Permission',
  forEntityTypes: [UMB_DOCUMENT_ENTITY_TYPE],
  meta: {
    verbs: ['Umb.Document.Delete'],
    label: '#actions_delete',
    description: '#actionDescriptions_delete',
  },
},
backoffice uses constants to check em.
Copy code
csharp
AuthorizationResult authorizationResult = await _authorizationService.AuthorizeResourceAsync(
    User,
    ContentPermissionResource.WithKeys(ActionDelete.ActionLetter, id),
    AuthorizationPolicies.ContentPermissionByResource);

if (!authorizationResult.Succeeded)
{
    return Forbidden();
}
w
So yeh decorate an API with a policy
But good sleuthing & digging Kevin !
3 Views
PreviousNext
Powered by