-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Error: Cannot find a descendant at path [6,9,2] in node: {"children":[{"type":"paragraph","childr... #7393
Comments
Hi @gvcalligraphy, please fill out all the fields in the issue template. The information you provided is not enough to debug the problem. I'm closing the issue for now. Once you add the missing information, I can open it again. |
There is no place to click in the issue template; reporting issues here. Another problem with the Content manager - Inspect Console shows errors like these when I open any page on the site for editing: |
@gvcalligraphy are you the developer working on this website? |
I am not, I'll let the developer know. Thanks.
…On Tue, Feb 4, 2025 at 9:14 AM Martin Jagodic ***@***.***> wrote:
@gvcalligraphy <https://github.com/gvcalligraphy> are you the developer
working on this website? Sent invalid data to remark error usually means
there's a problem with your frontmatter.
—
Reply to this email directly, view it on GitHub
<#7393 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK3JXNKGFAKKVQRA6DYNEO32ODDM5AVCNFSM6AAAAABWMPKGBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZUGA4TGNJRGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
That error also shows up on the main Content Manager page, before I open any webpages, even though there are no images on that page. And this error: I'm letting the developer know. |
Describe the bug
To Reproduce
Expected behavior
Screenshots
Applicable Versions:
[email protected]
github
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:134.0) Gecko/20100101 Firefox/134.0
CMS configuration
Additional context
The text was updated successfully, but these errors were encountered: