Unhelpful error messages

[GoogleCodeExporter]

<b>What steps will reproduce the problem?<b>
1. I think any time a page is loading and an error occurs in my code

<b>What is the expected output? What do you see instead?<b>
My error, but a wub-error occurs and I have no idea how to fix it:

wrong # args: should be "error message ?errorInfo? ?errorCode?"
    while executing
"error"

It doesn't even specify in which file this happens or code around it so that I 
can find it. I've done a search, but it started taking up too much time. 

There is also an error:

No such variable 'quote' in "unset quoted"


<b>What version of the product are you using? On what operating system?<b>

Wub-4.something on MS Windows XP Professional

<b>Please provide any additional information below.<b>

Original issue reported on code.google.com by candicem...@gmail.com on 23 Nov 2012 at 7:44

[GoogleCodeExporter]

Wub itself does not contain a script with a naked [error] invocation which 
would provoke the message you describe.

However, it is conceivable that the compilation of a .config file, particularly 
one which was improperly formatted, could produce code resembling that.

I therefore suspect your site.config file may have errors, and propose to 
investigate that possibility first.  Could you please paste that here, if it's 
not private, so I can possibly reproduce the error, and better handle the error 
case.

Original comment by mcc...@gmail.com on 23 Nov 2012 at 11:20

[GoogleCodeExporter]

Regarding the second issue, [unset quoted] appears nowhere in Wub, but catch 
{unset quoted} does appear.  From this, I deduce that you are using an old 
version of Wub, and suggest you upgrade it.

The best version is almost always the svn HEAD, and I recommend you use svn to 
extract HEAD.  If you can't do this, I can make a new 'release' and put it 
somewhere, but you can generally expect 'releases' to lag well behind the 
development HEAD.

Original comment by mcc...@gmail.com on 23 Nov 2012 at 11:28

[GoogleCodeExporter]

Oh I see. Seems I don't know enough about it, because I can't find the 
site.config file. You can delete this issue. 

Original comment by candicem...@gmail.com on 27 Nov 2012 at 8:37