Closed Bug 304752 Opened 19 years ago Closed 19 years ago

if i use a user-defined command, which is written locally, this message appears: "TypeError: ary has no properties @ <chrome://chatzilla/content/commands.js> 337", but the command works as it should

Categories

(Other Applications :: ChatZilla, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rp1987, Assigned: rginda)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.10) Gecko/20050717 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

example:
[ERROR]	Internal error while sending command "login".
[ERROR]	TypeError: ary has no properties @
<chrome://chatzilla/content/commands.js> 337

Reproducible: Always

Steps to Reproduce:
1. Make a user-defined command
2. Attach to ANY server you want
3. Use the user-defined command

Actual Results:  
Command worked normally, but the error message appeared

Expected Results:  
Not resulting that error.

I used the german chatzilla
I bet you did something silly like put a ";" at the end of the alias.
Indeed, telling us what alias you used should be part of your steps to
reproduce. Right now this bug is useless - all my aliases work, so it's
definitely not 'ANY user-defined command'. Please be more specific.
(In reply to comment #1)
> I bet you did something silly like put a ";" at the end of the alias.

This can bring up the error.
I used the Semicolon (;) to seperate commands from previous command's variables.
(In reply to comment #3)
> (In reply to comment #1)
> > I bet you did something silly like put a ";" at the end of the alias.
> 
> This can bring up the error.
> I used the Semicolon (;) to seperate commands from previous command's variables.

Right. So because you misdid your alias, ChatZilla gets confused. Not a bug ->
INVALID. If you don't understand how an alias works, ask for help in #chatzilla
on moznet. If it's still an issue afterwards, feel free to reopen the bug then.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.