Unable to create/ignore a term longer than the parsed by MeCab #34

Activity

1. HugoFara

   added

   bugSomething isn't workingSomething isn't working

   uiAny problem related to the User InterfaceAny problem related to the User Interface

   uxUser Experience could be betterUser Experience could be better

   and removed

   uiAny problem related to the User InterfaceAny problem related to the User Interface

   on May 31, 2022
2. HugoFara commented on May 31, 2022

   

   HugoFara

   on May 31, 2022

   Owner

   More actions

   After some tests, I think that the problem may be a bit different. Clicking "I KNOW ALL" should work, but to see it you have to manually reload the page. This is a UX problem as things may be better, but hopefully not something really annoying.

   For the sidebar and the "Read in browser" button, I think that your JavaScript is disabled for local files. A lot of functionalities won't work then so try enabling it in your browser settings (Settings → Privacy and Security → Site Settings → JavaScript). Hope it solves your problem ;)
3. rc-ops commented on May 31, 2022

   

   rc-ops

   on May 31, 2022

   Author

   More actions

   Hi!
   So after removing everything related to LWT, truncating the database (which I did before upgrading) and restarting EasyPHP in the process, I checked my browser console log, turns out it wasn't a javascript problem, which didn't make sense since I had been developing some JS stuff this week. Apparently ublock was blocking some 3rd party website, in this case jisho.org and google's tracking triggered by it. That's strange, because I hadn't problems with it before.
   Apparently it also closes #32
   Sorry. I should've tested it with a clean browser! :P
4. rc-ops

   closed this as completedon May 31, 2022
5. rc-ops commented on May 31, 2022

   

   rc-ops

   on May 31, 2022

   Last edited by rc-ops

   Author

   More actions

   Ok... I'm still having problems saving/ignoring some terms

   New Term: さかまきいざよい
   Fatal Error in SQL Query: SELECT WoID, WoTextLC FROM words WHERE WoLgID in(@m) AND WoWordCount = 0 into outfile 'C:\\Users\\USER\\AppData\\Local\\Temp\\db_440E.tmp'
   
   Error Code & Message: [1290] The MySQL server is running with the --secure-file-priv option so it cannot execute this statement
   
   Backtrace:
   
   #0  do_mysqli_query(SELECT WoID, WoTextLC FROM words 
               WHERE WoLgID in(@m) AND WoWordCount = 0 
               into outfile 'C:\\Users\\USER\\AppData\\Local\\Temp\\db_440E.tmp') called at [C:\Program Files (x86)\EasyPHP-Devserver-17\eds-www\lwt\inc\database_connect.php:585]
   #1  set_word_count() called at [C:\Program Files (x86)\EasyPHP-Devserver-17\eds-www\lwt\edit_mword.php:53]
   

   

   • I can sometimes trigger this error by doing:

   1. Go to some other LWT page
   2. Open the text to read
   3. Look for a word that is longer than the parsed by MeCab
   4. Click and drag from the beginning to the end of the word, like mentioned in Phrase select broken? #21,
   5. Select any word status and Save the term.

   If I delete the saved term I can trigger it again.

   • It gets trigged whenever I try to create a term longer than the parsed by MeCab. In this case Mecab parsed |さ|か|ま|き| い|ざ|よ|い| so if I wanted to create/ignore the word as a whole, it throws an error. Also if I tried to create a word from 逆廻十六夜, which got parsed as |逆|廻|十|六|夜|, same thing happens.

   （逆廻十六夜(さかまき いざよい)）
   何か面白いことねえかなあ

   • Another example with 佐藤和真, Mecab parses the word as |佐|藤|和|真|

               佐藤和真(さとうかずま)さん            
   

   New Term: 佐藤和真
   Fatal Error in SQL Query: SELECT WoID, WoTextLC FROM words WHERE WoLgID in(@m) AND WoWordCount = 0 into outfile 'C:\\Users\\USER\\AppData\\Local\\Temp\\db_750.tmp'
   
   Error Code & Message: [1290] The MySQL server is running with the --secure-file-priv option so it cannot execute this statement
   
   Backtrace:
   
   #0  do_mysqli_query(SELECT WoID, WoTextLC FROM words 
               WHERE WoLgID in(@m) AND WoWordCount = 0 
               into outfile 'C:\\Users\\USER\\AppData\\Local\\Temp\\db_750.tmp') called at [C:\Program Files (x86)\EasyPHP-Devserver-17\eds-www\lwt\inc\database_connect.php:585]
   #1  set_word_count() called at [C:\Program Files (x86)\EasyPHP-Devserver-17\eds-www\lwt\edit_mword.php:53]
   
6. rc-ops

   reopened this on May 31, 2022
7. rc-ops

   changed the title [-]Unable to mark all terms as known or create new terms[/-] [+]Unable to create term inside specific sentences[/+] on May 31, 2022
8. rc-ops

   changed the title [-]Unable to create term inside specific sentences[/-] [+]Unable to create/ignore a term longer than the parsed by MeCab[/+] on May 31, 2022
9. rc-ops commented on May 31, 2022

   

   rc-ops

   on May 31, 2022

   Author

   More actions

   Ok. I was able to fix the above error by editing mysql config.

   [mysqld]
   secure-file-priv = ""
   

   • It's able to create the term without errors, but it doesn't seem to get updated
     
   • Here for instance I've created the term 不幸にも, but it still appears blue instead of concatenating the characters and changing color
10. HugoFara

    added a commit that references this issue on Jun 1, 2022

    Fixed the "secure-file-priv option" required error

    ...

    1596d06
11. HugoFara commented on Jun 9, 2022

    

    HugoFara

    on Jun 9, 2022

    Last edited by HugoFara

    Owner

    More actions

    I was able to fix your issue with version 2.4.1, saving the file in the SQL folder instead of the server's "temp" directory, so that the "secure-file-priv" flag should no longer be necessary. For the markup referenced in #21, it is a broader issue, still being investigated, any help would be appreciated!

    I'm closing this issue as the problem specific to Japanese is fixed, but I'm aware that things still need a patch...
12. HugoFara

    closed this as completedon Jun 9, 2022
13. HugoFara

    added 2 commits that reference this issue on Jun 13, 2022

    Fixed #34 again.

    ...

    This issue will close once commit b40b889 is merged into the 'main' branch.

    b40b889

    Multi-word insertion fixed.

    ...

    This issue will close once commit 8279b60 is merged into the 'main' branch.

    8279b60