Open mukesh-thakur-dy opened 10 months ago
This is a templated message
Hello @mukesh-thakur-dy,
We ask that you please follow the issue template. A proper issue submission let's us better understand the origin of your bug and therefore help you. We will reopen your issue when we receive the issue following the template guidelines and properly fill out the template. You can see the template guidelines for bug reports here.
Please update the issue with the template and we can reopen this report.
Thank you.
@joshuaellis @derrickmehaffy Issue Format updated Please open the issue, and provide solution.
Your missing the versions in the system information for everything. Single type is not a version
Your missing the versions in the system information for everything. Single type is not a version
@derrickmehaffy version updated
@derrickmehaffy @joshuaellis I am facing same issue in latest version(4.19.0) anyone find a solution for that issue?
Opening content manager on 4.19.1
with node 20.11.0
, fresh project without any types causes the error.
main.fa982fef.js:635 TypeError: Cannot destructure property 'params' of '(0 , fe.SU)(...)' as it is null.
@fyllepo I can confirm that. running 4.19.1
with node 20.11.0
edit: reverting to strapi v4.15.5 solved the issue
@fyllepo I can confirm that. running
4.19.1
with node20.11.0
edit: reverting to strapi v4.15.5 solved the issue
Thanks for posting a working version, I have reverted for now and as you say it solves the issue for now. 👍🏻
@fyllepo I can confirm that. running
4.19.1
with node20.11.0
edit: reverting to strapi v4.15.5 solved the issueThanks for posting a working version, I have reverted for now and as you say it solves the issue for now. 👍🏻 How do I revert to 4.15.5?
@divofred npm strapi@4.15.5 -g
Thanks, this worked
Is there any update on this problem? In 4.20.0 the issue is still there
@derrickmehaffy @joshuaellis @Eventyret I am currently stuck on version 4.17.0. When I attempt to upgrade to 4.17.1, I encounter this error. Therefore, I believe the issue may be caused by a change introduced in version 4.17.1 (I noticed that the ContentTypeFormWrapper file changed in this version).
In my case, when I open a single-type page using plugins such as strapi-plugin-paper-trail, strapi-plugin-preview-button, etc., the page turns blank and all calls to these plugins are cancelled by the browser. I receive the error message 'Rendered more hooks than during the previous render.'"
Same issue here, we're using Strapi 4.19.1. Updating to 4.20.2 doesn't solve the issue.
same issue here, I'm upgrading to 4.20.3 from 4.15.2
In my case, when I open a single-type page using plugins such as strapi-plugin-paper-trail, strapi-plugin-preview-button, etc., the page turns blank and all calls to these plugins are cancelled by the browser. I receive the error message 'Rendered more hooks than during the previous render.'"
Does the issue persist without your plugins? because if not, it's probably an issue with the plugins, not Strapi.
I'm experiencing the same issue. For me, it occurs when I'm in the Content Manager and change the locale of the entry I'm editing. This happens both in Single Types and Collections. Here are the dependencies I'm using and their respective versions:
Dependency | Version | Dependency | Version |
---|---|---|---|
@editorjs/editorjs | 2.25.0 | @strapi-community/strapi-provider-upload-google-cloud-storage | ^4.10.5 |
@strapi/strapi | ^4.13.1 | @strapi/plugin-i18n | ^4.11.7 |
react-router-dom | ^5.2.0 | react | ^18.2.0 |
react-dom | ^18.2.0 | react-editor-js | 1.10.0 |
react-router-dom | ^5.2.0 | strapi-plugin-preview-button | ^1.1.1 |
Engines:
@diozenio have you tried it without your plugins?
@joshuaellis Not yet, as these plugins are essential for editing the content I'm working on
Using Strapi version 4.21.0 now, node v16 with graphql plugin. Cant access the content manager at all - seriously it's been 2 months now!
I've managed to fix this via this process:
node_modules
package-lock.json
npm install
Seems like some dependency issues caused this.
I worked on this issue for quite a long time: I updated packages, tried different old versions. I came to the issue in the @strapi/design-system package
in the Dialog
component. I removed this dialog from my custom plugins, replaced it with a standard one, and everything worked.
Then I tried to update different @strapi/*
packages - everything works every time. So, in my case, the Dialog
component was the problem. It was used one-to-one like in docs: https://design-system.strapi.io/?path=/docs/components-dialog--docs
Using Strapi version 4.21.0 now, node v16 with graphql plugin. Cant access the content manager at all - seriously it's been 2 months now!
@progech i got the same error and solved the issue by upgrading the @strapi/plugin-i18n
into the same version with @strapi/strapi
.
eg.
before
"@strapi/plugin-i18n": "4.12.1",
"@strapi/strapi": "4.12.1",
after
"@strapi/plugin-i18n": "4.21.0",
"@strapi/strapi": "4.21.0",
Ahora uso Strapi versión 4.21.0, Node v16 con el complemento GraphQL. No puedo acceder al administrador de contenido en absoluto. ¡En serio, ya pasaron 2 meses!
@progechObtuve el mismo error y resolví el problema actualizando
@strapi/plugin-i18n
a la misma versión con@strapi/strapi
. por ejemplo, antes"@strapi/plugin-i18n": "4.12.1", "@strapi/strapi": "4.12.1",
después
"@strapi/plugin-i18n": "4.21.0", "@strapi/strapi": "4.21.0",
Thanks !
Required System information
Describe the bug
Strapi admin page crash if i use latest version. I see the below error in console when i open Strapi Admin in live server.
Error: Minified React error #310; visit https://reactjs.org/docs/error-decoder.html?invariant=310 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
if I use Strapi version 4.16.2, then all works fine, but if I use the upper version from 4.16.2 then facing the issue for single collection types.
Steps to reproduce the behavior
Expected behavior
Open Admin "Content Manager" with single type properly
Screenshots