Alright, that's enough of this already!
The error is caused because the script for the FastClick pop-under window (

) 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:
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