-
Notifications
You must be signed in to change notification settings - Fork 19
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
LOAD DATA LOAD FILE on webserver #20
Comments
Hello, Sorry for the delay, I won't be able to contribute much during the next couple of weeks. Your problem seems to be related to a simple permission issue. Here are my suggestions, ideas 1 and 2 are for records only (as they do not apply to you) :
Generally speaking, it seems that your server configuration does not allow you to use the I hope that will help you! |
Hello, After an extensive study of your problem, I don't think it can be "solved" on my side, Here are the conclusions:
In a nutshell, I cannot bring a "fix". As I am aware that many users will face the same issue, I may use a workaround to avoid this statement. In the meantime, the issue will unfortunately persist. Of course, I am open to any pull request from anyone wanting to solve this problem! |
Hi! This issue have been fixed with the release 2.5.1. It still remains on terms import, I may take care of this part later. |
I removed the use of LOCAL INFILE in most parts of the code, except the "Import terms" feature ( To allow "LOCAL INFILE":
|
Describe the bug
After uploading lwt to webhoster the save/save and open/check text functionalities return an error.
Expected behavior
Page with added text available, ready to read.
Desktop:
Additional context
It worked with original lwt version (same hoster, same setting up proces). After opening text after this error, text doesn't appear (blank space in place of text/dictionaries).
After installing the LWT demo database there's an error as well
*** Error: Demo Database NOT restored - 418 queries - 23 successful (17/0 tables dropped/created, 0 records added), 395 failed. ***
Again it seems like texts don't upload. Languages and audio files do.
The text was updated successfully, but these errors were encountered: