-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Table of Contents: Preventing Editing Rest of Post #56283
Comments
Do you mean the Table of Contents block? A few additional questions:
|
Version 17.0.2 Usually 8-15 headings |
Help us move this issue forward. This issue is being marked stale since it has no activity after 15 days of requesting more information. Please add info requested so we can help move the issue forward. Note: The triage policy is to close stale issues that need more info and no response after 2 weeks. |
Hi, |
I tried to reproduce this on v18.7.1 but was unable. I tested up to ~5000 words and 70 headings, with headings maximally nested. I am able to add the Table of Contents block, publish, and return to edit the post with no errors. |
Description
I have put the list of contents block in all of the blog posts. However, when I click on the blog post to go back and edit, the editor never loads and I can't access the post. I received a RangeError: Maximum call stack size exceeded on one of the attempts of trying to load the blog page and listed the gutenberg plugin. I uninstalled the gutenberg plugin and only then was I able to access the blog post again. I also removed the list of contents block from the blog post and reactivated gutenberg and I could also then access the blog post editor again. The list of contents block seems to be working fine on the published website itself.
Full error message
RangeError: Maximum call stack size exceeded
at J (https://philosopheradabsurdum.com/wp-content/plugins/gutenberg/build/editor/index.min.js?ver=8e21285a2dad98a45044:1:30902)
at ke (https://philosopheradabsurdum.com/wp-content/plugins/gutenberg/build/editor/index.min.js?ver=8e21285a2dad98a45044:1:34659)
at we (https://philosopheradabsurdum.com/wp-content/plugins/gutenberg/build/editor/index.min.js?ver=8e21285a2dad98a45044:1:34479)
at Object.r [as getPermalink] (https://philosopheradabsurdum.com/wp-content/plugins/gutenberg/build/data/index.min.js?ver=0f51809e66c3f62da1c5:1:17222)
at https://philosopheradabsurdum.com/wp-content/plugins/gutenberg/build/block-library/index.min.js?ver=ff0fcb5dc4a5b8505419:123:40562
at https://philosopheradabsurdum.com/wp-content/plugins/gutenberg/build/block-library/index.min.js?ver=ff0fcb5dc4a5b8505419:123:41313
at https://philosopheradabsurdum.com/wp-content/plugins/gutenberg/build/block-library/index.min.js?ver=ff0fcb5dc4a5b8505419:123:41363
at https://philosopheradabsurdum.com/wp-content/plugins/gutenberg/build/data/index.min.js?ver=0f51809e66c3f62da1c5:1:20272
at Array.forEach ()
at n (https://philosopheradabsurdum.com/wp-content/plugins/gutenberg/build/data/index.min.js?ver=0f51809e66c3f62da1c5:1:20260)
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: