i discovered a problem with custom fields. I installed the multi select plugin (https://www.npmjs.com/package/strapi-plugin-multi-select) and its showing up in the admin dashboard via general -> plugins.
In the content type builder when i want to create a new field and i click on "custom" the multi select field is not showing up for selection. I tried it with different other custom field plugins and none is working.
I sadly don't get any error, maybe someone here experienced the same issue 🙂
my dependencies looks like this:
"dependencies": {
"#strapi/plugin-graphql": "4.5.0",
"#strapi/plugin-i18n": "4.5.0",
"#strapi/plugin-users-permissions": "4.5.0",
"#strapi/strapi": "4.5.0",
"better-sqlite3": "7.4.6",
"dayjs": "^1.11.6",
"deep-rename-keys": "^0.2.1",
"deep-rename-keys-ts": "^1.0.1",
"geographiclib": "^1.52.2",
"geographiclib-geodesic": "^2.0.0",
"graphql-type-json": "^0.3.2",
"nexus": "^1.3.0",
"pg": "^8.8.0",
"strapi-plugin-country-select": "^1.0.0",
"strapi-plugin-multi-select": "^1.1.0",
"strapi-utils": "^3.6.11"
}
Thanks in advance for any help!
So i found a solution to solve the symptoms of the problem, not the root cause.
It somehow has to to with a webpack error i'm experiencing when building the project:
No inputs were found in config file 'tsconfig.json'
Well there were inputs, which is kinda strange.
After trying to fix the upper bug and deleting different directories .cache .tmp .dist .node_modules, package-lock.json, and even the project folder itself. I tried to re-clone, re-install and re-build.
Nothing seemed to help EXCEPT to clone it into another directory than i usually store my repos.
My webpack error was gone and i could install and use the plugins without hassle!
I don't know if someone ever will experience the same error, but this solved the symptoms and i could get back to work ;)
You need to rebuild your strapi after plugin installation. This is the same for all plugins in Strapi CMS please go to your strapi folder and run
yarn build then yarn develop
Related
Update 2:
This probably has to do with the this PR where assets have been removed as dependency.
Update 1:
Managed to get a reverse shell into the serverless function and it really would appear that there is no public folder anymore:
Provide environment information
"next": "12.2.5", // Also tested on 12.2.6-canary.7 and 12.1.6
"next-i18next": "12.0.0", // Also tested on 10.5.0
"react": "18.2.0", // Also tested on 17.0.2
"react-dom": "18.2.0" // Also tested on 17.0.2
How are you deploying your application?
Vercel
Bug Description
Context
We encountered a bug around next-i18next that resulted in serverless crashes for catch-all routes. We noticed this bug for the first time Monday around 14:00 CET and think it is potentially related with a change in the serverless runtime/filestructure as older deployments that used to work stoped working when redeploying.
Some other people also seemed to have encountered the same bug. See also here:
This discod thread
This next-i18next bug report
Stackoverflow same problem
What we tried
So we upgraded our versions of next and next-i18next (like some of the other people did).
With the most recent next.js and next-i18next versions translations seem to work only in very specific cases.
We created a minimal replicable deployment (Repo) where we prebuild two pages via putting them in getStaticPaths:
https://ed-i18n-bug.vercel.app/en/test/prebuild
https://ed-i18n-bug.vercel.app/de/test/prebuild
Both pages do not use translations when opening them directly.
However, when first navigating to the index.js and then clicking on of the links the two pages use proper translation.
Note: The translations will break upon refresh.
Setup Description
catch all route in pages folder
page set to static site generation
default locale is set
incremental static regeneration is on
Expected Behavior
working Translations
Links to Reproduce
Example repo here: https://github.com/everdropde/ed-i18n-bug
Example Vercel Deployment: https://ed-i18n-bug.vercel.app/de
Steps To Reproduce
Clone the Repo and deploy it to Vercel
Click any link on page
if you have outputFileTracing enabled and using latest version of Next.js then this should work with latest CLI version
https://github.com/vercel/next.js/issues/40130
Setting env variable VERCEL_CLI_VERSION=vercel#28.1.4 fix the issue
Also if you set outputFileTracing: true in next.config.js it works with latest CLI version
Hi there everyone!
I'm trying to build my internet files into a format that is optimized for the internet, but when I tried to build it using npm run build, it gave me the above error message even though I have mainly jpegs and png files that were processed and built correctly on other project files.
May I know how to fix this and/or understand the error code so I can resolve future errors of this nature? Below is the package.json file details in case you need it to help resolve the error.
Thank you so much
As mentioned in the comments, this looks like a bug in #parcel/image-optimizer, and if you could share a more specific repro, that would be helpful.
In the meantime, you could probably work around this by disabling image optimization - just create a .parcelrc file at the root of your project that looks like this:
{
"extends": "#parcel/config-default",
"optimizers": {
"*.{jpg,jpeg,png}": []
}
}
Recently the SPM has started to give me errors. Was working before.
I'm trying to use the AlamofireImage library but xcode fails to resolve de dependency and doesn't give any good explanation.
Does anybody know why and how to make it work?
this was once happened to me, maybe you can try to go ahead to File > Swift Packages > Update to Latest Package Versions. Let's see if that works
I ran into a similar issue when I was trying to arrange the files inside the project folder, and when I put them back to their old position the problem was resolved and the app run successfully.
I found something that's not ideal, but works for now. In your main xCode project file, go under Project not Target and find Package Dependencies. After finding it, remove the SDK, and then right click on the name of your project and add a package. This time when adding Firebase, use Minor version. It should hopefully resolve and install.
I'm trying to learn more about package development by using Laravel Nova as a bit of a guide. I'm confused as to how Nova's assets are compiled, and part of that confusion stems from Nova not having a webpack.mix.js but instead a webpack.mix.js.dist.
I'm trying to model this within my package in order to compile and publish my assets for use in my project, but I get npm errors when trying to run any command
Cannot find module 'dir/dir/dir/package/webpack.mix'
I'm unsure as to why it is looking for this file in the first place, but it still seems to be an issue. To get to the root of why this is an issue and how I can fix this, I'd like to know what the difference between webpack.mix.js and webpack.mix.js.dist is.
Any feedback on this would be greatly appreciated. Thank you.
Files that end in '.dist' are generally the default distribution files that come from the package and should not be edited. They will be overwritten on package updates.
You can use them as a reference to add or replace configuration in your primary file(s).
From what I can gather, Laravel Nova creates it's real webpack.mix.js from this file when you activate a certain feature. (It's a paid product, I do not have a license to see it, I can only skim the documents.)
I have an Ember-CLI application that is very form heavy.
I started using Ember Forms to help with layout and templating, which is nice and seems to be working fine.
Apparently for validation, it requires Dockyard's Ember-Validation as well... This particular dependency seems to be installed differently and I am lost as how to do this.
I am used to using something simple like bower install ... and then just adding the dependency in brocfile, but in this case, Dockyard provides a huge list of builds to choose from and I have no idea which one to use?
Does anyone have experience installing ember-validation in an ember-cli project and getting to play nicely with ember-forms? Or perhaps it is actually more simple than I think, and I am just getting thrown off by all the builds to choose from?
To install it you can add manually the url to the build in bower.json
"ember-validations": "http://builds.dockyard.com.s3.amazonaws.com/ember-validations/ember-validations-latest.js",
And after that run bower install it should work fine.
Hope it helps.