Ok, I can reproduce this, you can work around this issue by explicitely calling the content in the default language in your config:
'ready' => function () {
return [
'johannschopplich.content-translator' => [
// API key for the DeepL free or pro plan
'DeepL' => [
'apiKey' => site()->content('fr')->DeeplAPISecret()->value()
]
],
'owebstudio.instagram-feed' => [
'accessToken' => site()->content('fr')->InstagramAccessToken()->value(),
'cache' => true,
'store' => true,
'debug' => false,
'expire' => 480, // 3 hours
'limit' => 12 // fetch limit
],
'hcaptcha' => [
'secret' => site()->content('fr')->hCaptchaSecret()->value()
]
];
},
I’d also recommend to set those token/secret fields to translate: false
, you don’t want users to translate them into different languages.