Post Reply 
update for Pre-Head Blocks?
Feb. 21, 2013, 05:14 PM
Post: #1
update for Pre-Head Blocks?
i'm not sure if this is a 'bug' and in need of an update or not for the "Cut: Specific Pre-Head Blocks 09.07.04 [jd sd] (d.2)" filter...

what happens is that when this filter kicks in, the lower right corner Prox Menu will no longer function...

and any filter that is supposed to match "(^(^<ProxHdrTop>))$STOP()" will no longer match, but will if the mentioned filter is disabled...

example sites -
http://www.usatoday.com/
http://www.bizjournals.com/
http://www.fiercebiotech.com/
http://beta.fool.com/
http://www.vehicleservicepros.com/articl...e-ecm-data
Add Thank You Quote this message in a reply
Feb. 22, 2013, 03:56 AM
Post: #2
RE: update for Pre-Head Blocks?
Filter is removing the closing IE conditional comment, <!--<![endif]-->.

What about

Code:
[Patterns]
Name = "Cut: Specific Pre-Head Blocks     13.02.21 [jd sd] (d.2) TEST [add]"
Active = TRUE
URL = "$TST(hCT=*html)(^$TST(keyword=*.(a_code|a_prepos).*))"
Limit = 10000
Match = "<("
        ""
        "("
        "$TST(mHtml=include|ajax&\1)|$TST(tHead=\1)|$TST(script=s\1)"
        "|$TST(preBlock=prx-\1)$SET(preBlock=prx-stop2)"
        ")$STOP()PrxFail$TST()"
        "|"
        "(^$TST(\1=*))("
        ""
        "("
        "script$TST(script=1(^*1)*)(^$TST(comment=1))"
        "(((*>)+{1} <script)+$INEST(<script,</script)</(script)\3*> )\4"
        "$SET(script=)$SET(2=\3 for="proxMoved-\1"\4)"
        "|"
        "("
        "noscript*</(noscript)\3 > $SET(tNoscript=)"
        "|style(^$TST(comment=1))*</(style)\3 > $SET(tStyle=)"
        "|frameset(^$TST(comment=1))$INEST(<frameset,</frameset >)</(frameset)\3 >"
        " (<noframes*>(*</noframes >|) |)|(base|link)\3\s(^$TST(comment=1))*>"
        " )\2"
        ")"
        "$TST(mHtml=[#1:*]$SET(1=head)*|h-tag$SET(1=html))"
        "$SET(eCode=$GET(eCode)"
        "%3Cspan class=%22Pr0xFly-Span%22%3EMoved:%3C/span%3E      \3 above \1%3Cbr class=%22Pr0xFly-Br%22 /%3E"
        ")"
        "|(!--(^\sPROX[:-]| <!\[endif\]-->)$TST(comment=1)$INEST(<!--,-- >)-- > $NEST(<!--,-- > )+(^(^<(^!--))))\2"
        "$SET(3=comment)$SET(comment=)$TST(mHtml=[#1:*]$SET(1=head)*|h-tag$SET(1=html)|$SET(1=void)*)"
        ""
        ")$SET(preBlock=$GET(preBlock)<\2)"
        "($TST(volat=*.log:2*)$ADDLST(Log-Main,[$DTM(d T)]\tWEB StripMove_Pre_\1 \t\3 \t\u)|)"
        ""
        ")(($TST(eCode=*)|$TST(eAdComm=*)|$TST(hOrigUA=*msie(^*opera)*))(<\?xml*\?> )+<!doctype *> |)"

?

Do we need to protect the conditional argument?
For example, "Mark First - Remove Dupes" is removing the reason for the conditionals existence on the example sites.

Code:
<!--[if lt IE 7 ]><html lang="en" class="no-js ie6"  xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml">
<![endif]-->
<!--[if IE 7 ]>
<Match: <html><body>: Mark First - Remove Dupes     09.06.28 (multi) [sd] (d.r) >
<html lang="en" class="no-js ie7"  xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml">
</Match>
<![endif]-->
<!--[if IE 8 ]>
<Match: <html><body>: Mark First - Remove Dupes     09.06.28 (multi) [sd] (d.r) >
<html lang="en" class="no-js ie8"  xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml">
</Match>
<![endif]-->
<!--[if IE 9 ]>
<Match: <html><body>: Mark First - Remove Dupes     09.06.28 (multi) [sd] (d.r) >
<html lang="en" class="no-js ie9"  xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml">
</Match>
<![endif]-->
<!--[if (gt IE 9)|!(IE)]><!-->
<Match: <html><body>: Mark First - Remove Dupes     09.06.28 (multi) [sd] (d.r) >
<html lang="en" class="no-js"  xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml">
</Match>
<!--<![endif]-->

HTH
Add Thank You Quote this message in a reply
[-] The following 1 user says Thank You to JJoe for this post:
ProxRocks
Post Reply 


Forum Jump: