Caps Lock Detection on Login

[candidosa2]

yes nice work good mod thank you
when update dont forget portuguese

Code Select Expand

<file name="$languagedir/Modifications.portuguese_pt.php" error="skip">
<operation>
<search position="end" />
<add><![CDATA[
// Caps Lock detection on Login Mod by Nas translate candidosa2
$txt['capslock_warning'] = 'Caps Lock est&aacute; activada.';
// End Caps Lock detection on Login Mod by Nas

]]></add>
</operation>
</file>
<file name="$languagedir/Modifications.portuguese_pt-utf8.php" error="skip">
<operation>
<search position="end" />
<add><![CDATA[
// Caps Lock detection on Login Mod by Nas translate candidosa2
$txt['capslock_warning'] = 'Caps Lock est&aacute; activada.';
// End Caps Lock detection on Login Mod by Nas

]]></add>
</operation>
</file>
<file name="$languagedir/Modifications.portuguese_brazilian.php" error="skip">
<operation>
<search position="end" />
<add><![CDATA[
// Caps Lock detection on Login Mod by Nas translate darkness
$txt['capslock_warning'] = 'Caps Lock est&aacute; ativada.';
// End Caps Lock detection on Login Mod by Nas

]]></add>
</operation>
</file>
<file name="$languagedir/Modifications.portuguese_brazilian-utf8.php" error="skip">
<operation>
<search position="end" />
<add><![CDATA[
// Caps Lock detection on Login Mod by Nas translate darkness
$txt['capslock_warning'] = 'Caps Lock est&aacute; ativada.';
// End Caps Lock detection on Login Mod by Nas

]]></add>
</operation>
</file>

[Sirius OCTeam]

hi,

thanks for this one.

here you are the french

Code Select Expand

  <file name="$languagedir/Modifications.french.php">
<operation>
<search position="end" />
<add><![CDATA[
// Caps Lock detection on Login Mod by Nas
$txt['capslock_warning'] = 'La touche MAJ est active.';
// End Caps Lock detection on Login Mod by Nas

]]></add>
  <file name="$languagedir/Modifications.french-utf8.php">
<operation>
<search position="end" />
<add><![CDATA[
// Caps Lock detection on Login Mod by Nas
$txt['capslock_warning'] = 'La touche MAJ est active.';
// End Caps Lock detection on Login Mod by Nas

]]></add>
</operation>
</file>

[Joe N]

Could you attach Login.template.php and index.template.php here?

I attached them

[Blinker]

Hi Nas

Nice mod, thanks.

I was wondering if you could help me with something: on the main login screen the password input box has been pushed up slightly and is now out of alignment. I noticed in your screenshots the same thing occurs.

Since most of the time the warning isn't there it would be nice to have everything line up again. How difficult would it be to have the text display to the right of the password box as per my screenshot? Alternatively, there is some room below that would allow the box to come down just a little (again, see screenie).

What do you think? Is this possible?

[TurtleKicker]

Installed fine here on SMF 1.1.9 with no errors but also not working. I've tried the login fields on the top of the main page, as well as the dedicated index.php?action=login screen.

Using the default theme.

[Joe N]

Installed fine here on SMF 1.1.9 with no errors but also not working. I've tried the login fields on the top of the main page, as well as the dedicated index.php?action=login screen.

Using the default theme.

Went on your site and used a test username and did a caps lock password. shows up fine

[Mystiquo]

it'ok but there is a problem, w3c isn't valid
this is my result:

Code Select Expand

#  Warning  Line 117, Column 20: character "&" is the first character of a delimiter but occurred as data

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 117, Column 21: character "&amp;" is the first character of a delimiter but occurred as data

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 117, Column 31: character "<" is the first character of a delimiter but occurred as data

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 117, Column 38: character "&amp;" is the first character of a delimiter but occurred as data

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 117, Column 39: character "&amp;" is the first character of a delimiter but occurred as data

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 117, Column 69: character "&amp;" is the first character of a delimiter but occurred as data

... keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey))

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 117, Column 70: character "&amp;" is the first character of a delimiter but occurred as data

...eyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey))

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 117, Column 80: character "<" is the first character of a delimiter but occurred as data

...iftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey))

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 117, Column 88: character "&amp;" is the first character of a delimiter but occurred as data

...|((keyCode >= 97 && keyCode <= 122) && shiftKey))

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 117, Column 89: character "&amp;" is the first character of a delimiter but occurred as data

...((keyCode >= 97 && keyCode <= 122) && shiftKey))

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Error Line 117, Column 20: XML Parsing Error: xmlParseEntityRef: no name

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉
# Error Line 117, Column 21: XML Parsing Error: xmlParseEntityRef: no name

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉
# Error Line 117, Column 31: XML Parsing Error: StartTag: invalid element name

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉
# Error Line 117, Column 38: XML Parsing Error: xmlParseEntityRef: no name

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉
# Error Line 117, Column 39: XML Parsing Error: xmlParseEntityRef: no name

if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <

✉
# Error Line 117, Column 69: XML Parsing Error: xmlParseEntityRef: no name

... keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey))

✉
# Error Line 117, Column 70: XML Parsing Error: xmlParseEntityRef: no name

...eyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey))

✉
# Error Line 117, Column > 80: XML Parsing Error: StartTag: invalid element name

...iftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey))...

✉
# Error Line 117, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...iftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey))...

✉
# Error Line 117, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...iftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey))...


Can you help me?

[Marcus Forsberg]

W3c should be valid. I'll look at it in the next update.



Also, if you have any feature request, feel free to sign up and file a request at this site:
http://www.forentadatorerna.se/

[ailarkaljurand]

That's good I can use it everywhere I want. But what is that file where I must type it? I don't understand. ANd else, I'm not much good in english, but I hope you understand me

[Marcus Forsberg]

That's good I can use it everywhere I want. But what is that file where I must type it?

The file will depend on what area you want to use the mod in.
If, for example, you wish to use the caps lock detection in the password field at rehistration, the file would be Register.template.php.

[chriso29]

I'm using version 1.1.10 with the theme kani. I haven't been able to get it to work. Do you have any tips?

Thanks

[badaliens]

W3c should be valid. I'll look at it in the next update.



Also, if you have any feature request, feel free to sign up and file a request at this site:
_http:hxxp:www.forentadatorerna.se/ [nonactive]

i have last version and have the same problem

Code Select Expand

#  Warning  Line 82, Column 202: character "&" is the first character of a delimiter but occurred as data

...16)?true:false); if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCod

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 82, Column 203: character "&amp;" is the first character of a delimiter but occurred as data

...6)?true:false); if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 82, Column 213: character "<" is the first character of a delimiter but occurred as data

...lse); if(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 &&

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 82, Column 220: character "&amp;" is the first character of a delimiter but occurred as data

...f(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 82, Column 221: character "&amp;" is the first character of a delimiter but occurred as data

...(((keyCode >= 65 && keyCode <= 90) && !shiftKey)||((keyCode >= 97 && keyCode

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 82, Column 251: character "&amp;" is the first character of a delimiter but occurred as data

... 90) && !shiftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey)) document

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 82, Column 252: character "&amp;" is the first character of a delimiter but occurred as data

...90) && !shiftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey)) document.

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 82, Column 262: character "<" is the first character of a delimiter but occurred as data

...iftKey)||((keyCode >= 97 && keyCode <= 122) && shiftKey)) document.getElement

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 82, Column 270: character "&amp;" is the first character of a delimiter but occurred as data

...|((keyCode >= 97 && keyCode <= 122) && shiftKey)) document.getElementById(div

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Warning Line 82, Column 271: character "&amp;" is the first character of a delimiter but occurred as data

...((keyCode >= 97 && keyCode <= 122) && shiftKey)) document.getElementById(div)

✉

This message may appear in several cases:

    * You tried to include the "<" character in your page: you should escape it as "&lt;"
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    * Another possibility is that you forgot to close quotes in a previous tag.

# Error Line 82, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

✉
# Error Line 82, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

✉
# Error Line 82, Column > 80: XML Parsing Error: StartTag: invalid element name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

✉
# Error Line 82, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

✉
# Error Line 82, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

✉
# Error Line 82, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

✉
# Error Line 82, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

✉
# Error Line 82, Column > 80: XML Parsing Error: StartTag: invalid element name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

✉
# Error Line 82, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

✉
# Error Line 82, Column > 80: XML Parsing Error: xmlParseEntityRef: no name

...vascript"> function capsLock(e,div){ keyCode = e.keyCode?e.keyCode:e.which; s...

[Joe N]

where is this shone?

Also, what theme and smf version?

[SpelingMistakes]

Is it possible to use this for nicknames - usernames – I hate when people type whole nickname with big letters – searching for solution for that I found this – Maybe it will solve my problems

Few questions

1.   this is only notice – it cant stop user in going trough other steps of registration
2.   I am interested in solution which will stop user in doing something if it is not kind of good manned (writing with big letter – especially if you write your username) – can this do that?
3.   Can this be used for names of Topics also

Thanks in advance for your answer

Spel

[Marcus Forsberg]

Yes, it is possible. Please read the "Customize this modification" in the first post.

1. No, it was never supposed to stop them from registering - Only warn them about it.
2. Whit some tweaking, perhaps.
3. Yes. Again, read the "Customize this modification".

[SpelingMistakes]

I have read about adjusting it to my needs or "Customize this modification", but I am not a coder, and there is not explicitly written – it works that and that – because of that I ask this

Spel

[Marcus Forsberg]

Changelog
1.1.0.1 | November 9 2009
* Supports SMF 2.0 RC2 and Curve!

[Marcus Forsberg]

I have read about adjusting it to my needs or "Customize this modification", but I am not a coder, and there is not explicitly written – it works that and that – because of that I ask this

Spel

Please attach Post.template.php here and I'll show you how to fix this for topic names.

2.   I am interested in solution which will stop user in doing something if it is not kind of good manned (writing with big letter – especially if you write your username) – can this do that?

In the next update I'm going to include a new setting for admins. If it's set to true, an alert message will popup when someone writes with capslock on, making it impossible for them to do anything if they keep writing with capslock on.

[Guardian ekiM]

While trying to install this mod on 2.0 RC2, I received 1 error in my Theme's index.template.php and the mod appears to be NOT working.
Currently, I'm using theme Extreme6 from:

Code Select Expand

http://custom.simplemachines.org/themes/index.php?lemma=1078

[Marcus Forsberg]

Mind attaching index.template.php here?