-
AuthorPosts
-
mountainman Friend
mountainman
- Join date:
- April 2011
- Posts:
- 65
- Downloads:
- 0
- Uploads:
- 18
- Thanks:
- 10
- Thanked:
- 1 times in 1 posts
September 30, 2011 at 7:46 pm #169154I have used JA_Login as illustrated in the screen shot.
MOD_LOGIN_VALUE_USERNAME & MOD_LOGIN_REMEMBER_ME appear in the screen shot.
They are referred to in line 39 & 48 respectively of mod_jalogin/tmpl/default.phpBut Password seems to be derived from JGLOBAL_PASSWORD from en_GB.ini, while MOD_LOGIN * * * appear to come from the ja_login language files..
If you change these parameters in default.php the output remains unchanged.
What do I need to do to make appropriate text appear on the login form?
pavit Moderatorpavit
- Join date:
- September 2007
- Posts:
- 15749
- Downloads:
- 199
- Uploads:
- 2274
- Thanks:
- 417
- Thanked:
- 4028 times in 3778 posts
September 30, 2011 at 8:45 pm #415964Hi
Have you checked in your language folder if you have the en-GB.mod_jalogin.ini ?
mountainman Friendmountainman
- Join date:
- April 2011
- Posts:
- 65
- Downloads:
- 0
- Uploads:
- 18
- Thanks:
- 10
- Thanked:
- 1 times in 1 posts
October 1, 2011 at 10:38 am #416004Yes. It is present and correct.
It is where my confusion began. The code is asking for MOD_LOGIN_VALUE_USERNAME and there are no values like that in that file.
So I searched for them and they are found in en-GB.mod_login.ini file in languages.
So, back to the code, where TXT_LOGIN and BUTTON_LOGIN are used. These only appear in en-GB.mod_jalogin.ini – which appears in two places – under language files and in the mod_jalogin file set.
I made the following changes
- Add a different number to each of the Password examples.
- Change the MOD_LOGIN references to reflect the variables in mod_jalogin.ini
Cleared all caches, reloaded and tried again but these changes have had no effect at all. But one of the Password changes was seen on the New Account page.
In particular the references to MOD_LOGIN variables still persists. This made me think that the base login modules may be interfering so I de-activated the module in the backend and then changed the path to the Login code. Neither had any effect.
Any clues where to go next?
AuthorPostsViewing 3 posts - 1 through 3 (of 3 total)This topic contains 3 replies, has 2 voices, and was last updated by mountainman 13 years, 1 month ago.
We moved to new unified forum. Please post all new support queries in our New Forum
Login labels display incorrectly
Viewing 3 posts - 1 through 3 (of 3 total)