0

We are having a Sitecore 10.3 XM NextJS docker instance. Sometimes Our Experience editor not loading properly in editing mode(loading like a regular page). This is intermittent though.

This is an issue with fields other than "Single line text" and "Rich text" fields. Please check below 2 screenshots. Sometimes when we reload the page this issue occurs.

enter image description hereenter image description here

The difference I found between 2 rendered HTMLs is, an additional input element is getting added in the non working one. PFB screenshot, enter image description here

I am also getting these hydration errors in console, enter image description here

Improve this question
6
  • Have you checked any errors logged in the console?
    – Sumit Helaiya
    Commented Mar 19, 2023 at 3:17
  • @SumitHelaiya - I am getting the react hydration errors in console. updated the screenshot above.
    – Rashmi936
    Commented Mar 20, 2023 at 16:28
  • See if this works - stackoverflow.com/questions/73162551/…
    – Sumit Helaiya
    Commented Mar 20, 2023 at 17:05
  • Okay, I will check this. But as per my understanding this console error is harmless. It is always there in both working and non working conditions.
    – Rashmi936
    Commented Mar 20, 2023 at 18:46
  • 1
    quick update on this - I noticed that a sitecore cache clear resolves this issue but It is not a full proof solution.
    – Rashmi936
    Commented Mar 24, 2023 at 5:31

1 Answer 1

Reset to default
0

We are facing the same issue, but for us behavior is, it works fine on our DEV server and does not work on local somehow

My observation and debugging shows that, if you have used <Link of JSS and if you are using {editable:true} that is causing the issue for us

if I make it {editable:false} my experience editor loads and I am able to edit other parts

Currently with {editable:true} I am not even able to see Add Here button but with {editable:false} I am able to.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.