-
Notifications
You must be signed in to change notification settings - Fork 2.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
Autosave closed early and infinite loading of the component #11145
Comments
Update 2: I figured out that you need to put a UI component in RenderBlocks, not a scheme. Okay. I deleted my block from there. But the miracle didn't happen. It still renders in 1 step / f5, and is not displayed on the screen. |
I have the same error message all the time, although the block components are loading normally. |
I've been getting this error as well, even on 3.18. I tried increasing the interval time of my autosave, but that's not helping. |
I too am getting this same issue, "autosave closed early" it seems to happen when i have alot of blocks or a media field that takes a bit longer to load and then this error occurs. |
I also get this error. When it happens, some fields in custom blocks also disappear until the page is refreshed. |
Same issue for me -- seems to be a regular occurance, and happens across a variety of blocks, not a single-specific block. Payload v3.23.0 |
I have this
which seems to have subsided the autosave error for now. I think the I've only ever noticed this error come up ONLY after making a change, never before. Try the |
Describe the Bug
Hi! I was experimenting with blocks and immediately got an error
Link to the code that reproduces this issue
https://github.com/NeilRiver/payload_issues
Reproduction Steps
EXTRA:

and there is also an eternal loading of the component. You add it and it is like loading and will never load
(in order for it to load you need to press f5)
Which area(s) are affected? (Select all that apply)
area: core, area: templates, area: ui
Environment Info
The text was updated successfully, but these errors were encountered: