error with strapi 4.7.1

Question

error with strapi 4.7.1

jhackr opened this issue 2 years ago · 8 comments

if you have a new version of strapi and install comment you will got a blank page with role
/admin/settings/users-permissions/roles
if delete plugin then you can access to that page.
hope you gonna fix it soon

Answer 1 · 2023-03-03T05:15:52.000Z

Thanks for reporting @jhackr . May I ask you to provide details like:

node version
comments plugin version
console error stack trace

It will be easier to investigate.

Answer 2 · 2023-03-03T07:49:37.000Z

Just tested it on 4.7.1 and works as expected.

Please provide more details, mentioned above + dependencies from package.json

If Strapi is running, you're able to use it but some of the internal stuff does not work because of as you said installing our plugin that might not be the case of plugin itself but some of your other customizations, in here roles maybe? Comments plugin uses Roles as a dependency not the opposite.

Fresh install, no additional roles added. Works.

Answer 3 · 2023-03-03T20:49:41.000Z

I just tested today it work as well on strapi 4.6.1.
But when upgrade to 4.7.1 the role dosen't work.
I just update strapi now again.

my package.json
{ "name": "", "private": true, "version": "0.1.0", "description": "A Strapi application", "scripts": { "develop": "strapi develop", "start": "strapi start", "build": "strapi build", "strapi": "strapi" }, "dependencies": { "@ckeditor/strapi-plugin-ckeditor": "^0.0.7", "@strapi/plugin-i18n": "4.7.1", "@strapi/plugin-users-permissions": "4.7.1", "@strapi/strapi": "4.7.1", "mysql": "2.18.1", "strapi-plugin-comments": "^2.2.6" }, "author": { "name": "A Strapi developer" }, "strapi": { "uuid": "" }, "engines": { "node": ">=14.19.1 <=18.x.x", "npm": ">=6.0.0" }, "license": "MIT" }

node -v v18.14.0
yarn -v 1.22.19
strapi 4.7.1 typescript
mysql db
ubunto 22

I didn't make a fresh install I just upgrade and migrate from strapi 4.6.1 to 4.7.1
I follow https://docs.strapi.io/dev-docs/migration/v4/migration-guide-4.6.1-to-4.7.0

Answer 4 · 2023-03-03T21:55:57.000Z

additional info
If I delete comment plugin on strapi 4.7.1 role path will work.

Answer 5 · 2023-03-04T07:03:42.000Z

Thanks for all the details @jhackr , I'm trying to reproduce it then based on flow you described.

Additionally as I'm seeing server console healthy can you provide the browser console stack of this white page?

Answer 6 · 2023-03-04T13:48:14.000Z

sure @cyp3rius

`

Answer 7 · 2023-03-05T14:22:10.000Z

Possibly bug found in Strapi itself.

The User Permissions uses match-sorter: ^4.0.2 and with updating Strapi it gets version 6.x where are significant changes how the versions are imported. If you check your node_modules you'll see that you probably use 6.x which requires to by imported like:

import {matchSorter} from 'match-sorter'

but in UserPermissions plugin it is imported as:

import matchSorter from 'match-sorter'

That causes errors, I'm about to post issue on strapi/strapi.

Answer 8 · 2023-03-05T18:17:06.000Z

@jhackr I've spent a bit more time on investigation. Indeed my founding was correct. I've solved it by forcing the same match-sorter version as in User Permission plugin. Intermediate issue was caused by react-query dependency which requires match-sorter: ^6.0.2.

Hopefully it will work for your config. Version with fix is v2.2.8. I've tested it with different configurations and run types.