JavaScript Forum

**Brian07002** · 09:53 AM

Hi,

I could somone here have a look at this page and tell me if an image loads up on it? I am talking about a large image with the name Dress Me Up Erotica, or does it just give an error? I am asking cause it's on a hosted server, and I am pretty sure my box has a trojan of some sort, I don't know if the trojan is causing the page to spit out the error message that I see. A simple reply is all I am asking..

Code:

http://dmue.100webspace.net/

Thanks.

**ADAM Web Design** · 08-03-2007, 11:22 AM

There's a syntax error in the Javascript and no picture. I'd say if you have a trojan, it's not causing this issue.

Rock the AVG Free (http://free.grisoft.com) and see if you can kill the trojan that way.

**Brian07002** · 12:20 PM

Thanks for checking it out for me!

I'm even getting the error's on other sites including this one

It's a Java error. But I think the problem on the hosted page is something in the script...I think it's because it not on a F Q D N. The script actually does work, meaning the admin area of the script works great, I just slapped the javascript that display's the images on the page, and it's on a blank html page...Just the javascript inside <body></body>.

So I think it's a FQ DN issue:

Dmue.100webspace.net instead of www.100webspace.net

Btw, the error on wmt:

Quote:

Runtime Error Has Occured

Quote:

Do you wish to debug?

Quote:

Line 168

Quote:

Unexpected call to method or property class

**logic ali** · 08-03-2007, 09:14 PM

Quote:

Originally Posted by Brian07002

Hi,

I could somone here have a look at this page and tell me if an image loads up on it? I am talking about a large image with the name Dress Me Up Erotica, or does it just give an error? I am asking cause it's on a hosted server, and I am pretty sure my box has a trojan of some sort, I don't know if the trojan is causing the page to spit out the error message that I see. A simple reply is all I am asking..

Code:

http://dmue.100webspace.net/

Thanks.

It's complaining about your CSS, probably because you have your <style> block in the body instead of in the head.