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

Existing content saved and published in block grid inline mode not saving #17634

Open
jbrisnehan-AMG opened this issue Nov 25, 2024 · 5 comments
Labels
release/15.1.0 state/needs-reproduction Check if this can be reproduced in the latest released version state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug

Comments

@jbrisnehan-AMG
Copy link

jbrisnehan-AMG commented Nov 25, 2024

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

15.0.0

Bug summary

Existing content saved and published in block grid inline mode not saving

Switching "Inline Mode" off on the Block Editor, solves the issue and the new content is saved.

Creating new content/areas also works fine. Just editing existing content is an issue.

Specifics

Umbraco Cloud. Checked/tested in multiple environments.

Steps to reproduce

Upgraded to v15.

  1. Opening and edit an existing page/node that has a Block Grid editor.
  2. Edit a content area of the Block Grid editor on the page (i.e. RTE or Header)
  3. Add new text (i.e. "test")
  4. Click Save and Publish.
  5. Save and Publish is successful.
  6. However the frontend does not reflect the change
  7. If you click away from the node and come back, the change is gone.

Expected result / actual result

I would expect content to save properly in the Block Grid whether in "Inline Mode" or not.


This item has been added to our backlog AB#46333

Copy link

Hi there @jbrisnehan-AMG!

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

@nielslyngsoe nielslyngsoe reopened this Nov 26, 2024
@nielslyngsoe nielslyngsoe added the state/needs-reproduction Check if this can be reproduced in the latest released version label Nov 26, 2024
@nielslyngsoe
Copy link
Member

Hi @jbrisnehan-AMG

Thanks for reporting this, we will be looking into wether we are able to replicate this migration problem.

@nielslyngsoe nielslyngsoe added the state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks label Nov 26, 2024
@nielslyngsoe
Copy link
Member

Note for future, see comment regarding possible problem regarding rendering here:
#17604 (comment)

@nielslyngsoe
Copy link
Member

nielslyngsoe commented Nov 26, 2024

Hi @jbrisnehan-AMG may I ask if this is solved with the outcomes of the conversation in this issue?
#17604 (comment)

If so I will not spend time replicating this, and then close this issue, are you okay with that?

@jbrisnehan-AMG
Copy link
Author

jbrisnehan-AMG commented Nov 26, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release/15.1.0 state/needs-reproduction Check if this can be reproduced in the latest released version state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks type/bug
Projects
None yet
Development

No branches or pull requests

2 participants