I don't know a lot about Burst Network, but is that how the ad calls
are supposed to look? Have you tried the ad without using WC2 to see
if the ad works straight out of the box?
There's not much there. The strange thing is, it appears as though
it's sending back text/html as the content type of that page... Not
sure if that's a problem?
Sorry I'm not of much more help.
Micky
Peter Gibson
unread,
Oct 17, 2012, 1:14:25 PM10/17/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to writecaptu...@googlegroups.com
Well after a load of debugging it seems I found the problem. I'm not sure whether this is the ideal fix but it seems to work for all of my ad networks. The problem is that Burst Network gives back a script and it ends with </SCRIPT>, it looks like this isn't recognised as the end of the script and so it tries to evaluate this as JScript which obviously fails. If this was </script> as opposed to </SCRIPT> it would work fine.
My fix was on line 98 of element.write.js (not within writeCapture itself), I changed: var specialBody = new RegExp("([\\s\\S]*?)<\/" + stack.last() + "[^>]*>");
To: var specialBody = new RegExp("([\\s\\S]*?)<\/" + stack.last() + "[^>]*>", "i");
Which makes the regex match case-insensitive. This causes element.write to recognise the ending tag and everything works nicely.
Micky Hulse
unread,
Oct 18, 2012, 2:00:46 PM10/18/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to writecaptu...@googlegroups.com
On Wed, Oct 17, 2012 at 10:14 AM, Peter Gibson <rvsp...@gmail.com> wrote:
> My fix was on line 98 of element.write.js (not within writeCapture itself),
> Which makes the regex match case-insensitive. This causes element.write to
> recognise the ending tag and everything works nicely.
Nice catch. I wonder if you should submit a patch? Might be useful to
others, and I don't see any reason why it needs to be case sensitive.
Glad you got it figured.
M
noah
unread,
Oct 18, 2012, 9:11:57 PM10/18/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to writecaptu...@googlegroups.com
I've patched element.write and updated the submodule for WC2. Thanks
for reporting this.
Micky Hulse
unread,
Oct 18, 2012, 9:22:17 PM10/18/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message