Open bjarnef opened 5 months ago
Hi there @bjarnef!
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 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 :robot: :slightly_smiling_face:
It seems to be related to this issue here https://github.com/umbraco/Umbraco-CMS/issues/15647 reported by @marcemarc
@bjarnef it's probably this:
https://github.com/umbraco/Umbraco-CMS/pull/16121
Basically the RTE got changed and fangled so that it no longer just stores a string, it's more complex, has 'blocks' ... and so when that property hits the XPath it's not a string anymore, @nul800sebastiaan has fixed it for the 404 page, wonder if it is the same kinda thing for the picker?
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
13.3.0
Bug summary
After upgrading from Umbraco v12.3.9 to v13.3.0 most seems to work correct. However on content pages in backoffice I get the following error, which seems to be related to XPath of pickers.
Stacktrace
Specifics
No response
Steps to reproduce
Access content page with pickers using XPath using
//
.Example:
If I replace e.g.
//employeeArchive
with$site/employeeArchive
the error doesn't occur.Expected result / actual result
No response