Strapi loses the Admin Menu and Auth logo on transfer #20278
Labels
issue: bug
Issue reporting a bug
severity: low
If the issue only affects a very niche base of users and an easily implemented workaround can solve
source: core:data-transfer
Source is core/data-transfer package
status: pending reproduction
Waiting for free time to reproduce the issue, or more information
Bug report
Required System information
Describe the bug
Using
npm run strapi transfer to=...
causes the remote Strapi to lose any configured custom logo for the Admin menu and Auth. I also noticed this behaviour earlier today when I usedstrapi export
and thenstrapi import
to migrate from sqllite to posgtres. I put it down at the time to some difference between sqllite and postgres. However, the same behaviour occured on the transfer between two postgres backed strapi instances as well.Steps to reproduce the behavior
npm run strapi transfer to=..
from the local strapi to the freshly created remote with a custom logo.Expected behavior
I expect one of the two to happen :
to
target gets the logo from thefrom
source.to
target retains whatever logo was originally configured on it, making its behaviour similar to what happens with admin accounts.What actually happens
The
to
target loses the logo. It does not seem to revert to the default logo, instead showing the empty box of a missing image src.Additional context
This is something of a pain when it comes to moving data around. It isn't a serious issue as such, I'm sure we can live with the Strapi logo and avoid the problem entirely. That said, I would still characterise this as a rather annoying quality of life bug.
The text was updated successfully, but these errors were encountered: