PWaddict Posted November 11, 2018 Share Posted November 11, 2018 The "Live Search" field is messed up. It displays many parts of .phrase-index.txt language's file as text. On Chrome console I'm getting the error: Uncaught SyntaxError: Invalid or unexpected token. How to fix this? Here is small part of it: Link to comment Share on other sites More sharing options...
PWaddict Posted November 13, 2018 Author Share Posted November 13, 2018 I figured why is this happening. Now waiting for a response on how to proceed. For more info check the GitHub issue. 3 Link to comment Share on other sites More sharing options...
ceberlin Posted November 17, 2018 Share Posted November 17, 2018 I could reproduce the effect - see video. I could not figure out yet which module or string creates the problem, but it seems to be some module I use a lot, as the problem appears on many sites. pw-bug-languages.mp4 Link to comment Share on other sites More sharing options...
PWaddict Posted November 17, 2018 Author Share Posted November 17, 2018 30 minutes ago, ceberlin said: I could not figure out yet which module or string creates the problem, but it seems to be some module I use a lot, as the problem appears on many sites. It's very easy to find out which module causing this. Just search the module files if </body> and/or </script> closing tags are inside translatable strings. Link to comment Share on other sites More sharing options...
ceberlin Posted November 17, 2018 Share Posted November 17, 2018 Already found AdminOnSteroids and CookieManagementBanner, there might be more. How do I reset the translation cache to test the effect of their removal? (The language page is plain dead because rendering stops unfinished) Link to comment Share on other sites More sharing options...
ceberlin Posted November 17, 2018 Share Posted November 17, 2018 Github does not seem to bring the (2y old) topic back to the top just because of new entries. The issue might be overlooked? Link to comment Share on other sites More sharing options...
PWaddict Posted November 17, 2018 Author Share Posted November 17, 2018 2 hours ago, ceberlin said: How do I reset the translation cache to test the effect of their removal? You need to go to your language id folder in site/assets/ and delete the .phrase-index.txt file. 37 minutes ago, ceberlin said: Github does not seem to bring the (2y old) topic back to the top just because of new entries. The issue might be overlooked? I don't think so. The issue is still opened and @ryan will be notified. 1 Link to comment Share on other sites More sharing options...
Marco Ro Posted January 14, 2019 Share Posted January 14, 2019 I have the same problem, but I can use the searching box for looking witch file is broken. Also I can't find any phrase-index.txt, where is exactly? Sorry @PWaddict, maybe you know. This problem about the live search could be the reason why after I added a new language it does not appear in the all URL segment ? I mean, I added French, and added fr in Languages Support - Page Names. In all pages the text input field for the French show up, but in the setting section missing all URL fr/link, there is only the link name, without the fr/ About the problem for the link I have fixed, I forgot to upload in the homepage the fr link. When you create the language to defeat in the homepage it's add the defeat language, I need to correct it by hand, even if you add the tag inside the page Languages Support - Page Names. Link to comment Share on other sites More sharing options...
tpr Posted January 14, 2019 Share Posted January 14, 2019 I just noticed this topic, here is a related post for the Cookie Management Banner where this issue was also present: Here you can find the location of the phrase-index.txt file too. 2 Link to comment Share on other sites More sharing options...
PWaddict Posted January 14, 2019 Author Share Posted January 14, 2019 Please inform the module authors to use HTML entities in notes for html tags. I've already fixed my PayPal module and also informed @Soma for EmailObfuscator module. It seems that with HTML entities just removes the whole messed up text but Live Search still remains broken. I will wait for an official fix from @ryan. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now