-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
v2: NOT NULL constraint failed: links.visibility #843
Comments
@vfrex Could you share a file which causes this error? Couldn't find any obvious problem with the import process. |
Sure, just need to strip it down a bit when I have a few minutes later this week. |
File is pretty messy from a Chrome->Firefox export/import seemingly duplicating everything a couple of times. I should have all personal stuff removed, but can I send it by e-mail to be safe? Haven't had time to experiment with the other databases. Side note: I retried the import removing sections/lines that seem to trip up the process. That works to an extent, but the process gets caught elsewhere in the list pretty quickly. The import will also separately error out without php8-iconv (or however it is packaged). |
You can send it to contact@linkace.org. Thanks! |
Unfortunately, Microsoft's mail servers are just not having it! 554: 5.7.1 REJECT - BAD content found Thinking about a next best way. |
You could also upload the file to wetransfer.com and send the link via mail. |
Thanks for sending the file. I have restructured the import to run in the background, executed by the cron. Each link is a separate background job now. You might want to try this with the new beta which will be released in the following days. After leaving LinkAce running for almost half an hour, 1/3 of the links were imported without issues. As the import seems to be fine, it's probably the visibility setting. Could you have a look at the
|
From CLI:
and
This same html file imports successfully in Linkace V1 Docker with MySQL. I believe it is the first link in the file. I will test with another backend on Beta 2 later.
Originally posted by @vfrex in #836 (comment)
The text was updated successfully, but these errors were encountered: