Request.Script_name problems

[Sparticuz]

This may be a little difficult to explain, so bear with me.

I have a small function that writes errors to a log table. I capture the ulink, the dynamicconnection string, an 'event type' (i define), a description (i also define), the current page, the user agent, the ip address, and finally the timestamp of the error.

FUNCTION write2log as v ( event as c, error as c = "" )

An example would be

flag = globalcn.Execute("SELECT * FROM gen_employee WHERE ulink = '" + session.__protected__ulink + "'")
if flag == .f. then
    write2log("SQL Error",globalcn.CallResult.text)
end if

Which enters this into my table

"ulink","5c51fe10-4c7f-4a0f-a99d-e89ea7cf2c83"
"dyncon","nope",
"event","SQL Error"
"desc","The database could not find the data you requested"
[B]"cur_page","/__a5RunDialog.a5w"[/B]
"user_agent","Mozilla/5.0 (Windows NT 6.1; rv:8.0.1) Gecko/20100101 Firefox/8.0.1"
"ip","nope"
"modified_date","2012-07-19 13:34:22"

I bold current page, because there is where my problem occurs.
Right now I'm using Request.Script_Name to get the script name.
If I run write2log within xbasic ON a a5w page, cur_page works correctly. However, if the write2log is within the xbasic IN a grid or dialog, I get the above __a5RunDialog.a5w as the cur_page. Which is, to my understanding, how the components are run. It is technically correct, but obviously, not what I want.

Looking through the Request variables page on the wiki: http://wiki.alphasoftware.com/Request+Object doesn't turn up anything I feel would be useful. The best solution would be to return the name of the component itself (prospects.a5wcmp, or whatever the component name is) Now, I suppose I could do write2log("Error in prospects") or something similar, but I'm hoping for something automated.

tl;dr
Request.Script_name returns __a5RunDialog.a5w instead of the actual page the component is on, which is probably correct, but not the 'intended' output

[Sparticuz]

Re: Request.Script_name problems

Anyone have any idea how to accomplish this?

[madtowng]

Re: Request.Script_name problems

I think Request.UserAgent is what you're looking for.

[madtowng]

Re: Request.Script_name problems

a5w_info() will show you lots more of whats going on with your web server.

[Sparticuz]

Re: Request.Script_name problems

I think Request.UserAgent is what you're looking for.

UserAgent gives me the UA of the browser the user is using, not the page they are on. (I'm already capturing UA anyways)

a5w_info() will show you lots more of whats going on with your web server.

This isn't exactly what I need either. However, It does show me alot of cool things. One of which is Request.Variables.__pageName which is close enough to what I need. I'll do some testing on it this afternoon and check to see if it's what I want. Thanks!

[madtowng]

Re: Request.Script_name problems

sorry about that, I clued in on the wrong thing.

Try Request.scriptname.

[Sparticuz]

Re: Request.Script_name problems

Try Request.scriptname.

That was what I was using at first, which isn't what I want.

[Sparticuz]

Re: Request.Script_name problems

I ended up using Request.Variables.__pageName

if variable_exists("Request.Variables.__pageName") then
			args.add("cur_page",Request.Variables.__pageName)
		else
			args.add("cur_page",Request.Script_name)
		end if

[madtowng]

Re: Request.Script_name problems

Now I'm curious.
What's the difference between Request.Variables.__pageName and Request.Script_name ?

[Sparticuz]

Re: Request.Script_name problems

When Request.Script_name is run on an a5w page it would return 'page.a5w'
When Request.Script_name is run in a dialog component it would return '__runDialog.a5w'
When Request.Variables.__pageName is run in a dialog component it would return 'page.a5w'
Request.Variables.__pageName is non-existent on an a5w page

[madtowng]

Re: Request.Script_name problems

Cool. I never tried running it from a dialog or grid.
I assigned the Request.Script_name value to a session variable.

[kkfin]

Re: Request.Script_name problems

Try Request.scriptname.

There is really both available: Request.scriptname and Request.SCRIPT_NAME but they seems to have same data. But why they are both there I don't know.

[kkfin]

Re: Request.Script_name problems

Okey now I just found the answer. Request.SCRIPT_NAME is deprecated and you should use instead Request.ScriptName.

Thanks to wiki the answer was easy to find.