Fix a bug where the i18n destination table is not correctly named

strapi / migration-scripts

Collection of Strapi Migration scripts

58 stars 58 forks source link

Fix a bug where the i18n destination table is not correctly named #69

Closed meganoob1337 closed 1 year ago

meganoob1337 commented 1 year ago

The destination table was wrongly named, and we had an error when executing the script here is a fix we used the latest strapi v4 version as migration target

martincapek commented 1 year ago

Hi, are you sure? If I open DB in Strapi v4 I have singular name.

derrickmehaffy commented 1 year ago

Agreed here, the table is and should be singular. Closing