-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve README #14
Comments
Hi, thanks for trusting my extension and sorry for the trouble. Yes, I already noticed the extension problem. I already add the warning message on the instance, should I make the field creation automatically? |
Hi, |
Ok then, thanks for the input |
Hi @lbraits, I fixed this issue on v1.4.5. Kindly check |
Hi,
First of all, thank you for this extension! We use it in a self-hosted Directus instance for the export/import feature flow, and it works pretty well for us.
In the last few weeks, we have noticed a recurring warning in our logs that seems to have appeared after an update of the extension:
After reading through some of the extension's code, we have figured out that these missing columns must be created manually via the Configure button on the extension's main page. I think it would be helpful to have this documented in the README as a required step when installing or updating the extension. Additionally, I am wondering if it would be possible to automate this process of migrating the database, for example, via a hook on one of Directus's init events, like the 'app.before' event?
Thank you!
The text was updated successfully, but these errors were encountered: