Umbraco 17 Beta Umbraco Flavoured Markup

Questions
,
1

I’ve already seen the same question in extending Umbraco 16 with Umbraco Flavoured Markup, however, I’m not up to speed with web components and the solution used in the threads. I also have a ‘isBlockVisible’ toggle in all my block settings which I used to display in Umbraco 13 to the user in the label using:

{{$index}}. {{title}} {{$settings.isBlockVisible ==‘0’ ? ‘[HIDDEN]’ : ‘’}}

My question is can you do this in UFM now in Umbraco 17 BETA directly in the label? If not will it be in the final release?

I’m currently using:

{umbValue: title | fallback : N/A}

but really need to display to the user that the block has been hidden in a simple straightforward solution.

Thanks

2

Without having your setup locally, it isn’t easy to test, but you could try something like this:

${ $index + 1 }. {=title} ${ $settings.isBlockVisible == "0" ? "[HIDDEN]" : "" }

That’s a mix of UFM ({ expression }) and UFMJS (${ expression })

{= property }: UFM, shorthand for {umbValue}

${ property }: UFMJS, javascript-like expressions such as math and booleans

3

Thank you so much Jacob, the settings expression works . The index I get not a number, NaN, but the main thing is being able to show to the user that the block has been hidden. ATB A

4

Oh yeah, my bad around $index. It is a feature targeting 16.4, which is out soon:

5

I using Umbraco 17 Beta, so hopefully by the RC1 or release it will be added? A

6

Yes, should be available in the first RC.

7

The index property works now in Umb 17.0.2 so my blocks have the following code to show the index, title or fallback as well as if in the settings the block is set to visible or not.

${ $index + 1 }. {umbValue: paragraphTitle| fallback: Paragraph} ${ $settings.isBlockVisible == “0” ? “[HIDDEN]” : “[VISIBLE]” }

Many thanks for helping me to find this solution. :smiley:

8

This works for me using ${ $index + 1 } which is great…however:

image
image216×149 2.69 KB

I now get:

image

when I edit the block. I therefore can only assume $index is an empty or null string when it is being populated in the slide out panel.

Is there something I haven’t added?

9

I’m seeing this too, I guess it might be tricky in the edit panel to know the index number of itself in the block list / grid, have been using this sort of setup:

${ $index >= 0 ? ($index + 1) + ' - ' : '' }Text Two Column

To at least lose the NaN

10

To note, the $index in the modal workspace headline has been fixed for the next minor (17.6, 18.1, RC 23rd July, final 6th Aug).