Blocklist label in V15

Questions
1

I’m upgrading our website to V15 and I run into some minor things.
One of them being the blocklist label.

We have a system with global blocks and we show in the label if a global block is selected.
In AngularJs we did this: {{$settings.globalFAQ? "[GLOBAL] - " : "" }}FAQ - {{blockname}}

In V15 we make use of a UFM component.

The issue is that I can’t find out how to access the settings- or content-model in a UFM component.

The only thing I can work with is the token that is the input.
Can someone point me in the direction of the solution?

Thanks!!

1 Like
2

Hey there Frans

Afraid I don’t have a solution for you - but I have seen someone else want to be able to access Settings values.

Issued raised here: [15.1] UFM umbValue to support values from Settings on a block · Issue #17619 · umbraco/Umbraco-CMS · GitHub

That issue hasn’t been updated in a while though so I’ll see what I can find out

3

So I asked around … UFM Block Settings is on the list to fix in an upcoming sprint but until then you’d have to “roll your own”. We don’t have any solid plans for ternary logic yet either.

There isn’t formal guidance on how to roll your own UFM component at the moment. The docs hint towards how to make a custom one.

And this is location of the core ones if you want to see how the CMS does it.

That’s all I can offer you at this point Frans.

4

When I am back at my other client tomorrow, I can see what I done as I think I rolled my own whilst waiting for it to be supported officially.

Please Hold

1 Like
5

For using content from the block @FransdeJong you can do this

Getting a value on the block called ‘header’

{umbValue: header}

Getting a value on the block called ‘header’ and making it UPPERCASE with a filter

{umbValue: header | uppercase }

More filters :point_down:

That should sort you out for now for the content on the block, until I can properly look at some code tomorrow.

2 Likes
6

Unfortunately, the umbValue component only supports the values and not the settings, @warren. We are going to add support for settings-as-values soon.

1 Like
7

OK I will have to check to see what on earth I have done with a custom UFM component.

@jacob perhaps its worth updating the issue on GitHub so it doesn’t look forgotten about as last update was back in December so that anyone following along there can be assured that its going to be worked on soon with a rough timeframe and minor version to expect it in.

8

Wow, this forum works like a charm!!

@jacob Is there a list of features that are still missing in V15 compared to V13?

1 Like
9

@FransdeJong, we have most of the UI features, but we need Tiptap to reach feature parity with TinyMce, we need tours, some more copy/paste features, and keyboard shortcuts.

As for the backend, the biggest pain point is the sending content/media notifications. There is a discussion going on when people are sharing what they would expect to use. Please contribute here if you have anything relevant:

10

OK checked my code, it was a UFM (umbraco flavoured markup) extension for dealing with dictionary items, where the syntax is {umbDictionary:My.DictionaryKey.Alias}

image
image2172×1281 131 KB

I am not sure if this is useful to you @FransdeJong as I don’t think I could do a UFM component for settings and thus I raised the GitHub issue.

Happy to share the dictionary UFM I wrote and put it here, if its of use.