The following warnings occurred: | ||||||||||||
Warning [2] Undefined variable $unreadreports - Line: 26 - File: global.php(961) : eval()'d code PHP 8.2.25 (Linux)
|
No language key found - Printable Version +- UserSpice (https://userspice.com/forums) +-- Forum: Support Center (https://userspice.com/forums/forumdisplay.php?fid=23) +--- Forum: UserSpice 4.3 and Below (https://userspice.com/forums/forumdisplay.php?fid=26) +--- Thread: No language key found (/showthread.php?tid=140) |
No language key found - LBC - 05-24-2016 Hey guys, I cannot seem to get rid of the "No language key found" error message in the form-signin-heading ( Code: <?=lang("SIGNIN_TITLE","");?> Code: <?=lang("SIGNIN_BUTTONTEXT","");?> Code: <?=lang("SIGNUP_TEXT","");?> Not sure what I did wrong there Any ideas? No language key found - mudmin - 05-25-2016 I'm going to send this one over to brian. That doesn't look familiar to me. No language key found - brian - 05-25-2016 Those are part of the $lang associative array in navigation.php that is used to provide named variables for commonly used terms or phrases to make translation to another language easier (in theory...not entirely consistent yet). By updating the array, you would only change text in one place, but it would then update everywhere it was used. It isn't very clear how this could be throwing an error (or rather, not displaying correctly), since it is just a php short tag (which is used gratuitously through the code) and an associative array index. I will take a look at the referencing you mentioned to see... No language key found - brian - 05-25-2016 Can you post a screenshot of the error or message that you are seeing? I don't have a clue how that would be generated...the screenshot should help understand where it is coming from. No language key found - LBC - 05-26-2016 Hello Brian, No need...you were right. It is called for in the navigation.php. I pasted in my own nav and totally forgot to put that piece of coding back. My apologies for bothering you with this. No language key found - brian - 05-26-2016 Not a problem. |