cannot create new Collection Types

[juliensl]

Hi everybody

Describe the bug
The button "Create new collection type" does not appear on my strapi app :'(

Expected behavior
Can create new collection type

Screenshots

System

• Node.js version: 12.16.1
• NPM version: 6.13.4
• Strapi version: 3.0.0-beta.19.3
• Database: mongo 3.6.12 on mlab
• Operating system: 18.04

Additional context
I deployed strapi manualy, with the strapi CLI, connected to an external mongoDB on mlab, launched in in the production mode with this command : NODE_ENV=production npm start
It does not work on firefox and chromium.
I restarted it but not work.
I searched plugin_content-manager_schema in my db, according with this comment #2213 (comment) but I did not found it.
When I try to directly got to http://myurl:1337/admin/plugins/content-type-builder/content-types/article
it redirects to http://myurl:1337/admin/plugins/content-type-builder/content-types/plugins::users-permissions.permission and it does not work :'(

It looks like I did not use the good command to start the server, but I am lost to know wich one I have to use :/

Thank you !

[benediktgrether]

Hey,
i run in the same issue a few minutes ago.
After i see the image

The autoReload feature is required to use this plugin. Start your server with strapi develop

i decided to start the Server with
strapi develop
and the issue was fixed for me.

I hope it works for you, too.

[juliensl]

Hi @benediktgrether, thank you for your answer.

I does not work with strapi develop, but I found the problem !
That's the NODE_ENV variable, when I set it to "production", it does not work, but it works without :)

I Think it's not a normal behavior :/

[christianguevara]

It's intended, check: a52a2ea for reasons :)

I think you can close this issue now.

[derrickmehaffy]

Closing, waiting for pr to be merged for answer in FAQ.

This is intended see the above linked answer in the pr

[lauriejim]

Here is the FAQ - https://strapi.io/documentation/3.0.0-beta.x/getting-started/troubleshooting.html#why-can-t-i-create-or-update-content-types-in-production-staging

[shrutisahatpure]

hi @benediktgrether i tried to use 'strapi develop' command but i got "'strapi' is not recognized as an internal or external command,
operable program or batch file." Can you please help with this?

[iamakshatjain]

I am facing this same issue with heroku deployment with mongoDB

[lauriejim]

Please try to run yarn Strapi develop or nom run strapi develop

[iamakshatjain]

Resolved the issue, It was existing because I had to deploy after creating content types locally. Don't you think that strapi should read content types directly from the database and not depend on extra files or change in the code, I think it would really enhance the capabilities of the product ? I was confused and involved into this for quite long before I accidentally found about this in a random YouTube video!

[lauriejim]

Ho okay, yes that the way you have to develop with Strapi.
We will have to improve the documentation about that point.
I understand you point, Database to API could be a great feature (as many others) but we have to prioritize with resources we have in the team 🙃 But thank you for your feedback.

[iamakshatjain]

Yeah, Let me know if I can help. Would love to contribute to such a great product 🙂!

[lauriejim]

We need a bite of re-structuration to include these info.
Waiting for our new Tech Writer to work on that :)

[calpa]

Use npm run develop to develop, remember not to set environment as production.

[iksent]

Also I have the similar problem after upgrading strapi packages to the newest version with yarn install and without yarn build.

Maybe we need to add some version mismatch notification to help developers avoid such situations?

[jalal246]

Also I have the similar problem after upgrading strapi packages to the newest version with yarn install and without yarn build.

Maybe we need to add some version mismatch notification to help developers avoid such situations?

I have the same issue as well (in development).

Update: I downgraded to version "3.2.4" and it works again.

[derrickmehaffy]

@iksent @jalal246

Hello!

Can you please create a new GitHub issue by using the GitHub issue template, providing all required information.

Your issue looks related to that topic but it's an old one. Using another thread (GitHub issue) will be able to manage your case.

Thank you and have a good day.

[iksent]

@derrickmehaffy, yes, I'll create a new issue, but please take a look at this problem then ;)

Really important for me:
#7547 (comment)

[rojcyk]

I have the very same problem.

[jalal246]

@rojcyk which version do you use?

[alexleone]

this is happening to me on 3.3.2 and 3.3.3, downgraded to 3.2.4

[derrickmehaffy]

Please create a new issue if you are having this problem and provide steps to reproduce.

The original issue likely has nothing to do with any current one. Locking.

[derrickmehaffy]

Info from @omgMath

Some people (including me) had the problem that the couldn't create new collection types after upgrading to 3.3.3 (see #5631).

This can be resolved by running

strapi build

and I think it would be helpful to add this information within the issue.

Buuut, since the issue is locked, I cannot add it. Not sure if this is the right channel to request that, but could you, @derrickmehaffy add that info?

Thanks!

Please note with regards to updating versions, see this part of our update/migration documents:
https://strapi.io/documentation/v3.x/migration-guide/
https://strapi.io/documentation/v3.x/guides/update-version.html#rebuild-your-administration-panel

Every version update, even minor you should be rebuilding your Admin panel.