nested content AngularJS template issue after 13.3 upgrade

[shearer3000]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.3.0

Bug summary

We have a CMS upgraded to Umbraco 13, so it has preexisting content based on the nested content editor (appreciate this is now marked as legacy, and to be removed in Umbraco 14).

After upgrading to 13.3.0, we've noticed that when editing content, the AngularJS template property of the nested content definition no longer works i.e. a template of "{{section[0].name}}" no longer displays what the syntax prescribes, but just "Item x" instead e.g. "Item 1".

This wasn't an issue in 13.1, 13.2.

Specifics

No response

Steps to reproduce

Edit content that uses a nested content property editor by modifying any existing content or adding new content, observe whether the AngularJS template syntax reflects the underlying content

In the following screenshot, the green box represents existing content (added in prior Umbraco 13 minor version), item 1 was existing content that was changed, and item 6 was newly added (after the Umbraco 13.3 upgrade)

Edit: in this case, the syntax is to target content authored with a Umbraco.MultiUrlPicker editor

Expected result / actual result

Expected: the syntax defined by the AngularJS template works
Actual: syntax not working and editor show default index value instead eg. "Item 1", "Item 6"

[github-actions]

Hi there @shearer3000!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[sandhuravinder]

@shearer3000 Are you using Umbraco's default nested content picker? Or do you have your custom implementation of nested content?

[shearer3000]

Using the default nested content picker @ravindersinghsandhu, correct :)