Page 1 of 1

Runtime error since forum upgrade?

PostPosted: Mon May 12, 2003 1:28 pm
by VEFF
I am not sure if I am alone, but I am getting runtime errors on every page while browsing the forums.
Is this an issue due to the upgrade that was just performed?

I am using IE 5.0 at work. Will try at home tonight (I have IE 6) .
Thanks!

PostPosted: Mon May 12, 2003 1:56 pm
by Ian
Working fine for me under XP with IE 6.0

PostPosted: Mon May 12, 2003 2:32 pm
by CDRecorder
I have IE6 on WinXP, and it works fine for me, too.

PostPosted: Mon May 12, 2003 4:35 pm
by Dan
Windows 2000 Pro, IE 6.0
I'm getting the runtime error messages as well. Not on everypage though.

I think it has to do with the ads =/

PostPosted: Mon May 12, 2003 5:32 pm
by dolphinius_rex
yeah, I'm recieving errors too.

I'm running Win2K and IE 6.0

according to IE, it's a syntax error on Line 225, Char 1 (code: 0)

hope that helps :D

Yeah, I'm getting those too.

PostPosted: Mon May 12, 2003 6:50 pm
by Turkeyscore.com
Yeah, I'm getting those too, but on line 225

PostPosted: Mon May 12, 2003 8:26 pm
by dodecahedron
yes, i'm getting a Runtime Error on every page load/refresh too.
"Error: Syntax Error on line 224". or 245. or 246.

WinXP, no SP1, IE6

PostPosted: Tue May 13, 2003 1:03 am
by David
I'm getting the error also.
Running 98SE IE6.0
Syntax Error on line 225, 230, 246.

PostPosted: Tue May 13, 2003 1:43 am
by CDRecorder
I logged in on my old Win98 box with IE6 SP1, and I am not getting the errors. I wonder if there is a bug or strange setting on some computers which causes this error. Or could it be that ad-blocking or cookie-blocking software is causing errors?

PostPosted: Tue May 13, 2003 6:07 am
by MediumRare
I'm getting these at work now- IE 6, NT4 SP6, but only when I'm logged in, and then each time I change pages. At home I use Opera 7, Win 95A and have no RT errors.

G

PostPosted: Tue May 13, 2003 9:16 am
by cfitz
Alright, that's enough of this already! :wink:

The error is caused because the script for the FastClick pop-under window ( :evil: ) is being inserted within the script block for the private message pop-up window, causing a mismatch of <script></script> tags:

This is how it is:

Code: Select all
<script language="Javascript" type="text/javascript">
<!--
   if ( 0 )
   {
      window.open('privmsg.php?mode=newpm', '_phpbbprivmsg', 'HEIGHT=225,resizable=yes,WIDTH=400');;
   }
//-->
<!-- FASTCLICK.COM POP-UNDER CODE v1.6 for cdrlabs.com -->
<script language="javascript"><!--
var doc=document;  var url=escape(doc.location.href); var date_ob=new Date();
doc.cookie='h2=o; path=/;';var bust=date_ob.getSeconds();
if(doc.cookie.indexOf('e=llo') <= 0 && doc.cookie.indexOf('2=o') > 0){
doc.write('<scr'+'ipt language="javascript" src="http://media.fastclick.net');
doc.write('/w/pop.cgi?sid=2673&m=2&v=1.6&u='+url+'&c='+bust+'"></scr'+'ipt>');
doc.cookie='he=llo; path=/;';} // -->
</script>
<!-- FASTCLICK.COM POP-UNDER CODE v1.6 for cdrlabs.com -->

</script>


This is how it should be:

Code: Select all
<script language="Javascript" type="text/javascript">
<!--
   if ( 0 )
   {
      window.open('privmsg.php?mode=newpm', '_phpbbprivmsg', 'HEIGHT=225,resizable=yes,WIDTH=400');;
   }
//-->
</script>

<!-- FASTCLICK.COM POP-UNDER CODE v1.6 for cdrlabs.com -->
<script language="javascript"><!--
var doc=document;  var url=escape(doc.location.href); var date_ob=new Date();
doc.cookie='h2=o; path=/;';var bust=date_ob.getSeconds();
if(doc.cookie.indexOf('e=llo') <= 0 && doc.cookie.indexOf('2=o') > 0){
doc.write('<scr'+'ipt language="javascript" src="http://media.fastclick.net');
doc.write('/w/pop.cgi?sid=2673&m=2&v=1.6&u='+url+'&c='+bust+'"></scr'+'ipt>');
doc.cookie='he=llo; path=/;';} // -->
</script>
<!-- FASTCLICK.COM POP-UNDER CODE v1.6 for cdrlabs.com -->


While we wait for Socheat to work his magic and fix this, the rest of us can eliminate the annoying "Syntax error" messages by unchecking either of these two checkboxes:

Image

Image

I normally disable reporting of script errors (there are too many buggy scripts out there), so I wasn't getting the message all of you were reporting. But I finally decided to temporarily re-enable it to see what all the fuss was about.

cfitz

PostPosted: Tue May 13, 2003 10:33 am
by Ian
OK, that should be fixed now.

PostPosted: Tue May 13, 2003 10:37 am
by dolphinius_rex
so far so good on this end! :D

PostPosted: Tue May 13, 2003 10:55 am
by cfitz
The fixed code looks fine.

cfitz

PostPosted: Tue May 13, 2003 11:10 am
by Dartman
I turned off the script error thing after I tried it on and it drove me nuts on almost every site I visited :) I also have blocked most of the anoying pop ups and disabled windows messenger, helps a lot.