This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/error-field-query-products-can-only-be-defined-once/2393/1

I found the reason. There were no fields in the child components. Maybe in this case you should to output some other error.

Thank you @alexandrebodin, option 2 worked for me, you the best 😎

Hi @derrickmehaffy, thanks a lot for all your efforts. It looks like the issue, that the values are no longer displayer in the frontend after saving (they are still present in the database) is still persisting in v3.4.3.

Would be great as well to be able to add a specific media path based on the content type

Bug report

Component in collection "No permissions to see this field" for super admin

Describe the bug

When creating a collection item, I see an error for the component field. I'm logged in as a super admin

A clear and concise description of what the bug is.

Steps to reproduce the behavior

1. Go to 'edit collection and add field (some component)'
2. Open collection item
3. I see "No permissions to see this field" for added component

Expected behavior

Screenshots

Code snippets

If applicable, add code samples to help explain your problem.

System

• Node.js version: 12.18.3
• NPM version: 6.14.6
• Strapi version: 3.4.1
• Database: sqlite3
• Operating system: windows 10

Hi, just to confirm that this bug is not entirely fixed. I can't give exact steps to reproduce but basically my setup was :

• 2 single type that have the same component with text and repeatable images
• I modified the component and removed the image field
• I now have this error in the log: Error: The target polymorphic type "components_home_supported_bies" is not one of the defined target types. My single type is home and my component is called supportedBy. It seems to match with the error.

Good luck and thanks :)

Looks like your CLOUDINARY_NAME environment variable isn't being set? Are you able to confirm?

it is looks like that but i added Cloudinary_name to .env file and plugins.js . İ had to create new project and now everything's working fine. I couldnt fine any other solution.

Bug report

Describe the bug

Creating a has-and-belongs-to-many relationship between two entities with long-enough names breaks Strapi and prevents it from starting up.

Steps to reproduce the behavior

1. Please clone this repository, read the README.md file and see it for yourself
2. After the last commit Strapi does not start anymore.

Expected behavior

it should run without any issue or the documentation should specify the limitation of maximum characters a user can have with PostgreSQL (the joint table name should not exceed 64 characters)

System

• Node.js version: v10.17.0
• NPM version: 6.11.3
• Strapi version: 3.4.4
• Database: postgres
• Operating system: Linux 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux

Additional context

Maybe the bugfix applied at #3409 leads to a trimmed joint table name (64 characters)

Sorry, I didn't realize that I was supposed to do anything. I Have made the adjustments, to make the tests succeed!

However I'm not quite sure about the codecov tests that are failing, should I do anything about this? It shouldn't really concern the feature that I'm commiting.

This is a bit confusing at the start, but I figured out the way to overcome this.

1. you need to create the User from the Content Manager not from the "settings > Anmistriation Panel > User"

2. Make a POST request from the postman with identifier and password, make sure you use the x-www-form-urlencoded.

Hope this helps! :)

<!-- Hello 👋 Thank you for submitting an issue.

Before you start, please make sure your issue is understandable and reproducible. To make your issue readable make sure you use valid Markdown syntax.

https://guides.github.com/features/mastering-markdown/

Please ensure you have also read and understand the contributing guide.

https://github.com/strapi/strapi/blob/master/CONTRIBUTING.md#reporting-an-issue -->

Bug report

Describe the bug

I get this error in the terminal:

(node:44216) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor. (Use node --trace-deprecation ... to show where the warning was created)

Steps to reproduce the behavior

1. Run: npx create-strapi-app freestylestats-api --use-npm
2. Fill the fields
3. See the error

Expected behavior

Not warning

System

• Node.js version: v14
• NPM version: v6
• Strapi version: v3.4.4
• Database: MongoDB
• Operating system: macOS

<!-- Hello 👋 Thank you for submitting a feature request.

We are using ProductBoard to manage our roadmap and feature requests.

Can you please submit your feature request here: https://portal.productboard.com/strapi -->

Feature request

Please describe your feature request

• [ ] I have created my request on the Product Board before I submitted this issue
• [x] I have looked at all the other requests on the Product Board before I submitted this issue

Summary

ECMAScript modules are the official standard format to package JavaScript code.

And now that Node.js supports it, it would be great to leave CJS behind.

I often get stuck in resolving conflicts process... It should be good now.

Maybe it's worth mentioning that I tried to connect with Instagram before migrating 3.4.4 and I was the one reporting the new Instagram API.

Thank you for those suggestions!

• I don't have a user in DB with the same email or username
• The user is well registered as a test user (otherwise I wouldn't be able to go this far in the OAuth flow)

The input field is disabled in the admin panel:

We don't really maintain the strapi-examples repo anymore & it is largely outdated. The doc is more than enough :)

Your config looks good to me at first sight so? some hypothesis to verify:

• You already have a user in the DB with the same email / username ?
• Your instagram app doesn't allow to get the right info & grant is complaining about it ? (verify the instagram app is configure with the right scope or that you have your account registered as a test user until the instagram app is "active"

The only diff I have with my config is the callback which I left by default /auth/instagram/callback so you might want to try it to eliminate this as an issue.

Let me know if any of this helps you

Hello @alexandrebodin! Yes, I followed the guide. See my config from core_store:

{
  "instagram": {
    "enabled": true,
    "icon": "instagram",
    "key": "<MY_KEY>",
    "secret": "<MY_SECRET>",
    "callback": "https://localhost:3000/connect/instagram/redirect",
    "scope": ["user_profile"],
    "redirectUri": "https://45b9e6cb7ea2.ngrok.io/connect/instagram/callback"
  }
}

Hey @Heziode your PR now contains 400+ commits :) I think there was a small issue in the update process ;) Let me know when ready ;)

Hi @baptisteArno Have you followed the migration guide on when updating to 3.4.4 ? https://strapi.io/documentation/developer-docs/latest/migration-guide/migration-guide-3.4.x-to-3.4.4.html#_2-migrate-instagram-login-config

@alexandrebodin is done.

Conflict solved. PR on doc: https://github.com/strapi/documentation/pull/81

My bad, it's /admin/forgot-password, not /auth/forgot-password.

Bug report

When logging in with Instagram, it redirects to the backend URL with the error code: Grant: missing session or misconfigured provider

Describe the bug

I'm testing Instagram login on my localhost using ngrok.

It succesfully calls the /connect/instagram/callback route but then redirects with the error Grant: missing session or misconfigured provider

[2021-01-23T08:11:48.074Z] debug GET /connect/instagram (16 ms) 302
[2021-01-23T08:12:22.352Z] debug GET /connect/instagram/callback?code=AQAfssCJ9EA2jZk0zLKgxCJc_Ov77OjoeIhyn8CvMjcii1Mes61qxRrADHOkrjdbmnfrT9EmhTQNOVIHdb0WdzHr38BoZ3paoP1JGAzqjWVUjCxHeNlMCDlnpaQ3ERrD3G6EdYjq3V_St-rVW4f6vayV4AODziFY8JDevAxXsJAWb5Ov11JIe3145-mYUHhrKF6v-i_V20iKtHQEzdAyw9qUS7kBPp1oFBmQ-ekKIvkkgw (19 ms) 302
[2021-01-23T08:12:22.573Z] debug GET index.html (10 ms) 200
[2021-01-23T08:12:22.853Z] debug GET /assets/images/logo_login.png (2 ms) 200

Here is my grant confing from core_store:

{
  "instagram": {
    "enabled": true,
    "icon": "instagram",
    "key": "<MY_KEY>",
    "secret": "<MY_SECRET>",
    "callback": "https://localhost:3000/connect/instagram/redirect",
    "scope": ["user_profile"],
    "redirectUri": "https://45b9e6cb7ea2.ngrok.io/connect/instagram/callback"
  }
}

I checked all this:

• Make sure you have set the backend url in config/server.js
• A session/cookie/cache problem: You can try again in a private tab.
• The incorrect use of a domain with ngrok: Check your urls and make sure that you use the ngrok url instead of http://localhost:1337. Don't forget to check the backend url set in the example app at src/config.js.

System

• Node.js version: 14.9
• NPM version: 6.14.7
• Strapi version: 3.4.4
• Database: PostgreSQL
• Operating system: MacOS 11.2

Too bad this isn't an option. I suppose one could order by some field (EG id DESC), and instead of using _start, use id_lt= using the last value of the sort column.

...that works, right? 🤔

This is a good workaround, it works well in my current project! It even improves performance for large offsets because it uses the power of indexes.

@alexandrebodin Thank you.

Thanks for implementing that fix, guys! 💚

@Jbmanllr any example on how to upload from node?

@tombunn in your example where do you get refId from? bodyFormData.append('refId', refId); You have it is a variable so wondering where it's coming from

with npx it says sqlite is not installed. try again