Strapi v5.0.6, 5.1

System Information
  • Strapi Version: v5.0.6, 5.1 …ts
  • Operating System: windows 11 local development, debian production
  • Database: mariadb 10.6
  • Node Version: 20.4.0
  • NPM Version:
  • Yarn Version: 1.22.22

hi,
for backend, i made recomendation middleware with his route
const compte=await strapi.documents(‘api::compte.compte’).findMany(
{
populate:{
profile:{
populate:{
interests: {
populate: “",
},
avatar: "
”,

                            photos: "*",
                            receptions:{
                                populate:{
                                    envoyeur:{populate:'avatar'}
                                }
                            },
                            envoyers:{
                                populate:{
                                    recepteurs:{populate:'avatar'}
                                }
                            },
                            aimes:{populate:"*"},
                              
                            stories:{
                                populate: "*",
                              }
                          }
                    },
                    store:{
                        fields:"*",
                        populate:"*"
                    },
                    position:{
                        fields:"*"
                    },
                 },
              filters: {
                  email: {
                      $eq: user?.email,
                  },
              },
          }
      )

where i made some request like this
fact is in development
all work fine,
all populate give me relation

but in production
have no error give me
his profile but
give me empty array for all relation inside
profile

otherwise, when i pass by rest
give me all nice
and just
for production

so i try pass to 5.1…
give me

inside phpstorm ide
error on first populate
so i try pass it in comment
and give nothing!!!

frontend is gatsby capacitor web and apk

so i try on linux local
wsl and
same error at production

it’s on linux
cannot have access to relation of relation

but on windows is good

sorry, not this
i have all message relation, receptions and envoyers
but no stories and receptions
so catch thing for production
and work fine with linux local, but not online!!
only difference is
sate user is not recognised online!!
but access be allow only by jwt
for his middleware

final is
work fine on localhost linux; windows
but on production…
give me user connected by jwt
relation of relation of compte have profile relation and message relation
but not interests and or stories…
and just in production online with
pm2
same process mariadb
and that proove all be good inside is
request rest like
return strapi.findOne(‘comptes’,id,{
populate:{profile:{
populate: {
receptions:{
populate:{
envoyeur:{
populate:‘avatar’
}
},
sort:{ createdAt: ‘desc’ }
},
avatar:‘‘,
photos:’
’,
interests:{
populate:‘icon’
},
stories:{
populate:{
media:‘‘,
aimes:’

}
},
compte:‘*’
},

									}}
					})

with strapi sdk this and work
same as with strapi v4
but work with v5

test production on local server and all is fine,
maybe it’s supplier
infomaniak…

the only fact with have no right with is
yarn run v1.22.22
$ strapi build
Failed to load command [Error: EACCES: permission denied, mkdir ‘/home/clients/ae030eb51d2046a6e051a5772be71f9c/.config/com.strapi’] {
errno: -13,
code: ‘EACCES’,
syscall: ‘mkdir’,
path: ‘/home/clients/ae030eb51d2046a6e051a5772be71f9c/.config/com.strapi’
}

infomaniak serveur cloud manager

maybe it’s this
but i don’t know what the
utility of

in road of,
take production shema in local, and same bug!!
so clean it, his mariadb and recreate from strapi schema…
and keep invisble link with interest and storie!
maybe it’s this
strapi give invisble link with fake old bdd entity