[Bug]: Issue in retrieving content-type with components along with locale

[santoshbmath]

Link to the documentation page or resource

https://docs.strapi.io/cms/api/rest#get-all

Describe the bug

We have created a content-type with one component and one text field. Both text field and components are localized.

When tried to get the documents for content-type for particular locale ("fr"), component's locale is not returned instead recent records are returned.

URL: http://:443/api/site-sections?locale=fr&populate=*

Additional context

Version: 5.12.4

Suggested improvements or fixes

No response

Related issue(s)/PR(s)

No response

[github-actions]

🤖 I've analyzed your question and here's what I found:

Hi there! Thank you so much for taking the time to report this issue and for providing clear details and a screenshot—your effort really helps us improve Strapi for everyone. 😊

Understanding the Issue

You've created a content-type with both a text field and a component, both localized. When you query your content-type for a specific locale (e.g., locale=fr) and use populate=*, you expect to receive the localized version of both the main fields and the component. However, it seems the component's locale is not being respected, and you’re seeing unexpected results.

What the Documentation Says

• The locale parameter is designed to return documents in a specific locale. When you use GET /api/site-sections?locale=fr&populate=*, Strapi should return all entries in the French locale, including populated components, but only 1 level deep by default [REST API: locale].
• Components and their fields must also be explicitly populated, and their localized content should be returned if it exists for the requested locale [Populate components].
• If a component or its fields are not localized, or if the localized version does not exist, Strapi may fall back to the default locale or return empty data for that component [REST API: locale].

Possible Causes & Workarounds

1. Component Localization Setup:
   Please double-check that your component is set to be localized in the Strapi admin panel. If the component itself is not marked as localized, it will not return locale-specific data.

2. Data Availability:
   Ensure that the French (fr) version of the component data actually exists. If the localized data for the component hasn't been created, Strapi will not return it for that locale.

3. Query Syntax:
   Your query syntax is correct for populating all first-level relations and components:

   GET /api/site-sections?locale=fr&populate=*
   

   This should return all localized fields and components, 1 level deep [Populate all relations and fields, 1 level deep].

4. Known Limitation:
   In Strapi v5, it is not possible to fetch all locales at once using locale=all. You must query each locale individually [locale=all breaking change].

Next Steps

• If your component is correctly localized and the data exists, but you’re still seeing this issue, it may be a bug.
  In that case, I recommend transferring this issue to the main Strapi repository for further investigation by the core team. Tagging @pwizla for visibility.

• If you need more help troubleshooting:

  • Double-check your component and field localization settings in the admin panel.
  • Try creating or editing the French version of your component data to ensure it exists.
  • You can also reach out to the Strapi community on Discord for real-time support.

• For feature requests or improvements:
  Please submit your ideas at Strapi Feedback.

Thank you again for your detailed report and for being an active part of the Strapi community! If you have any more details or updates, please share them here so we can assist further.

---

References:

• REST API: locale
• Populate components
• Populate all relations and fields, 1 level deep
• locale=all breaking change

📚 Relevant documentation:

• locale=all can not be used to get all entries in all locales
• 🧠 Understanding the populate parameter for the REST API - Example: With populate=*
• 🧠 Understanding the populate parameter for the REST API - Populate all relations and fields, 1 level deep
• 🧠 Understanding the populate parameter for the REST API - Populate components
• Document Service API: Using the locale parameter
• GraphQL API - locale
• Internationalization (i18n) - Usage
• Requests and Responses - ctx.request.query
• REST API parameters
• REST API: locale
• REST API: locale - GET Get a document in a specific locale
• REST API: locale - GET Get all documents in a specific locale
• REST API: Population & Field Selection - Population
• Use locale with the GraphQL API

---

ℹ️ This response was generated automatically. If this doesn't fully answer your question or if you need further assistance, please mention @pwizla in a comment and a human maintainer will help you.

You can also try our interactive AI chat for more detailed assistance.

💡 For feature requests or product feedback, visit feedback.strapi.io.