Closed rainydesignstudio closed 1 year ago
rainydesignstudio
commented
1 year ago Okay i'm kinda silly🤣, Strapi just updated to 4.14.0 with bug fixed: https://github.com/strapi/strapi/releases
So i just updated my Strapi to lastest version, Warnings are gone, and it can be run now, but it still throws up ValidationError and there's still no config folder.
ComfortablyCoding
commented
1 year ago Can you share a repo with a reproducible example for the validation issue?
What config folder are you referring to?
P.S. Regarding this plugin not working on earlier version than 4.14.0 as mentioned in the readme only the latest version is supported. The reason for this is to many (breaking) things change for all 4.x versions to be supported.
P.P.S. The warnings about unmet peer does are not from this plugin as you can see from the DEP path in the warning.
rainydesignstudio
commented
1 year ago Can you share a repo with a reproducible example for the validation issue?
What config folder are you referring to?
P.S. Regarding this plugin not working on earlier version than 4.14.0 as mentioned in the readme only the latest version is supported. The reason for this is to many (breaking) things change for all 4.x versions to be supported.
P.P.S. The warnings about unmet peer does are not from this plugin as you can see from the DEP path in the warning.
Thanks for the reply😉 Indeed, i just update my Strapi to 4.14.0, but just as i said, without warning but ValidationError throws up still. As we both know plugin.js should be located in config folder, but there's only one folder named server.
here's the repo: https://github.com/GoldenCoffee/Slugify-2.3.5---Strapi-4.14.0.git
ComfortablyCoding
commented
1 year ago Thanks!
The plugins.js file does not exist by default in the config folder. It needs to be created if it does not exist already. Looks like I did not mention that on this repos readme (I will do so).
P.S. Please note it is plugins.js not plugin.js
P.P.S. Their is a plan to auto create these files by default moving forward but does not look like this will happen before v5. Ref: https://github.com/strapi/strapi/issues/17868#issuecomment-1708765070
rainydesignstudio
commented
1 year ago Thanks!
The
plugins.jsfile does not exist by default in theconfigfolder. It needs to be created if it does not exist already. Looks like I did not mention that on this repos readme (I will do so).P.S. Please note it is plugins.js not plugin.js
P.P.S. Their is a plan to auto create these files by default moving forward but does not look like this will happen before v5. Ref: strapi/strapi#17868 (comment)
Awesome, also thanks for the note! should i just follow the guide to create content such as this?
module.exports = ({ env }) => ({
slugify: {
enabled: true,
config: {
contentTypes: {
film: {
field: 'slug',
references: 'title',
},
},
},
},
})I manually create file before, actually I tried in last night. Yes, before the Strapi@4.14.0 released, I using Strapi@4.13.7 as the latest version and added Slugify@2.3.4, same problems. 😥
Now I repeat the process and restart server again, but env looks declared and its value is never read. And still, I only get ValidationError again.
I just follow the guide such as unpublish content, change slug, save, publish again, nothing happend. I wonder is this problem only show up on Windows system?
ComfortablyCoding
commented
1 year ago I cannot say for sure but it looks to me like you have the plugin config in the wrong place.
The path to it should be ./config/plugins.js where the starting point is the root of your strapi project.
Based on your project name (tutorial-strapi-with-nextjs) the path in your case would be tutorial-strapi-with-nextjs/config/plugins.js
See https://docs.strapi.io/dev-docs/configurations/plugins for further info.
rainydesignstudio
commented
1 year ago I cannot say for sure but it looks to me like you have the plugin config in the wrong place.
The path to it should be
./config/plugins.jswhere the starting point is the root of your strapi project.Based on your project name (
tutorial-strapi-with-nextjs) the path in your case would betutorial-strapi-with-nextjs/config/plugins.jsSee https://docs.strapi.io/dev-docs/configurations/plugins for further info.
Thanks, now it's actually available😄
Before this moment, I searched plugins.js in local folders, No matching results, so i wonder where is it? And then I back to here to find a solution, I got [this](https://github.com/ComfortablyCoding/strapi-plugin-slugify/issues/35#issuecomment-1061150578). I also pull this repo at yesterday try to fix up the problem, So I got a misunderstanding from an old version (./strapi-slug-main/config/plugins.js in this repo). Anyway, it's been over a year, so I should check official Dev Docs before.
Thank you again for your patience and enthusiasm😘! This is a great opportunity to get started with Strapi and plugins, Especially for a newbie like me.
ComfortablyCoding
commented
1 year ago Your welcome!
Hi, I've provided some informations to see if that helps:
Here's some error report from console:
And that's not all. I just saw our dev update to the latest version, but before that, my Strapi can't run slugify 2.3.4 as well either. So let's see what happened last night: I set up roles and tested json and they all working good, but when i enable slugify and try to get json, it throw the error:
I immediately checked this error from github and it seemed to come from a long time ago: This error seem the same as #75.
I also get lots of warning print in my console:
I wonder why there are so many unmet peer dependencies, cuz i just created a new Strapi project at yesterday by using customzied settings: JS, Mysql, without eslint, And only one plugin slugify has been added.
And one of weird thing is, there are no plugins.js in the config folder, actually there's even no config folder.
Please check the files to get more informations:
strapi-plugin-slugify-2.3.4.zip strapi-plugin-slugify-2.3.5(cant run develop).zip