Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block list bug in contentblock #18630

Open
Andres073 opened this issue Mar 10, 2025 · 6 comments
Open

Block list bug in contentblock #18630

Andres073 opened this issue Mar 10, 2025 · 6 comments
Labels
affected/v15 area/frontend state/needs-reproduction Check if this can be reproduced in the latest released version type/bug

Comments

@Andres073
Copy link

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

15.2.1

Bug summary

When using a Block List Property Editor in a contentblock, and adding a title or any other field to that contentblock, the save & publish will fail with the following error message:

'test title' is an invalid JSON literal. Expected the literal 'true'. Path: $ | LineNumber: 0 | BytePositionInLine: 1.
A fatal server error occurred. If this continues, please reach out to your administrator.

I added printscreens of the block setup I made.

Image
Image

Specifics

No response

Steps to reproduce

  1. Create a contentblock with a blocklist property.
  2. Add a title field or something else to the block.
  3. Fill the content, save & publish it. The first time it will work
  4. Change the title field and save & publish. It will give the error this time.

Expected result / actual result

No response

Copy link

Hi there @Andres073!

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 🤖 🙂

@AndyButland
Copy link
Contributor

Thanks for reporting @Andres073. There have been some fixes in this area since the version you are on (in 15.2.2, and in 15.3, which we'd welcome feedback on as it's out in release candidate). Would you be up for upgrading in a development environment to 15.3.0-rc and confirming if it resolves your issue please?

@nielslyngsoe nielslyngsoe added affected/v15 area/frontend state/needs-reproduction Check if this can be reproduced in the latest released version labels Mar 10, 2025
@Andres073
Copy link
Author

Hi @AndyButland , I just tested this on 15.2.3 and 15.3.0-rc2. This issue is still present on those versions, I hope you can reproduce it to see it for yourself.

@Andres073 Andres073 closed this as not planned Won't fix, can't repro, duplicate, stale Mar 11, 2025
@Andres073 Andres073 reopened this Mar 11, 2025
@AndyButland
Copy link
Contributor

I've not been able to I'm afraid, at least when running 15.3.0-rc2. I've tried to follow from your screenshots and description and am pretty sure I've got the same setup you are describing, but could be I'm missing something.

@Andres073
Copy link
Author

Hi @AndyButland, that's unfortunate. If necessary, I could share a backup of the database we are working with, or we could plan a video call. We have tried everything we can think of to resolve the issue.

@AndyButland
Copy link
Contributor

Would be happy to have a look if you could share a database back up with me, thanks. I'm at abl AT umbraco DOT dk if you'd like to send a link for me to download it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affected/v15 area/frontend state/needs-reproduction Check if this can be reproduced in the latest released version type/bug
Projects
None yet
Development

No branches or pull requests

3 participants