c-harris /
phpquery
This project does not seem to handle request data directly as such no vulnerable execution paths were found.
include, or for example
via PHP's auto-loading mechanism.
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
| 1 | <meta http-equiv="Content-type" content="text/html; charset=utf-8" /> |
||
| 2 | <?php |
||
| 3 | require_once('../PhpQuery/PhpQuery.php'); |
||
| 4 | //PhpQuery::$debug = 2; |
||
|
0 ignored issues
–
show
|
|||
| 5 | PhpQuery::plugin('Scripts'); |
||
|
0 ignored issues
–
show
The method
plugin() does not seem to exist on object<PhpQuery>.
This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history...
|
|||
| 6 | |||
| 7 | |||
| 8 | //$doc = PhpQuery::newDocumentXML('<article><someMarkupStuff/><p>p</p></article>'); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
68% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 9 | //print $doc['article']->children(':empty')->get(0)->tagName; |
||
| 10 | |||
| 11 | //$doc = PhpQuery::newDocumentFile('test.html'); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
62% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 12 | //setlocale(LC_ALL, 'pl_PL.UTF-8'); |
||
| 13 | //$string = strftime('%B %Y', time()); |
||
| 14 | //$doc['p:first']->append($string)->dump(); |
||
| 15 | |||
| 16 | /* |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
65% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 17 | * |
||
| 18 | $doc1 = PhpQuery::newDocumentFileXHTML('doc1.html'); |
||
| 19 | $doc2 = PhpQuery::newDocumentFileXHTML('doc2.html'); |
||
| 20 | $doc3 = PhpQuery::newDocumentFileXHTML('doc3.html'); |
||
| 21 | $doc4 = PhpQuery::newDocumentFileXHTML('doc4.html'); |
||
| 22 | $doc2['body'] |
||
| 23 | ->append($doc3['body >*']) |
||
| 24 | ->append($doc4['body >*']); |
||
| 25 | $doc1['body'] |
||
| 26 | ->append($doc2['body >*']); |
||
| 27 | print $doc1->plugin('Scripts')->script('safe_print'); |
||
| 28 | */ |
||
| 29 | //$doc = PhpQuery::newDocument('<p> p1 <b> b1 </b> <b> b2 </b> </p><p> p2 </p>'); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
68% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 30 | //print $doc['p']->contents()->not('[nodeType=1]'); |
||
| 31 | |||
| 32 | //print PhpQuery::newDocumentFileXML('tmp.xml'); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
67% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 33 | |||
| 34 | |||
| 35 | //$doc = PhpQuery::newDocumentXML('text<node>node</node>test'); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
68% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 36 | //pq('<p/>', $doc)->insertBefore(pq('node'))->append(pq('node')); |
||
| 37 | //$doc->contents()->wrap('<p/>'); |
||
| 38 | //$doc['node']->wrapAll('<p/>'); |
||
| 39 | // ->contents() |
||
| 40 | // ->wrap('<p></p>'); |
||
| 41 | //print $doc; |
||
| 42 | |||
| 43 | // http://code.google.com/p/phpquery/issues/detail?id=66 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
63% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 44 | //$doc = PhpQuery::newDocumentXML('<p>123<span/>123</p>'); |
||
| 45 | //$doc->dump(); |
||
| 46 | //$doc->children()->wrapAll('<div/>')->dump(); |
||
| 47 | |||
| 48 | // http://code.google.com/p/phpquery/issues/detail?id=69 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
59% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 49 | //$doc = PhpQuery::newDocumentXML('<p class="test">123<span/>123</p>'); |
||
| 50 | //$doc['[class^="test"]']->dump(); |
||
| 51 | |||
| 52 | // http://code.google.com/p/phpquery/issues/detail?id=71 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
58% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 53 | // $doc = PhpQuery::newDocument('<input value=""/>'); |
||
| 54 | // print $doc['input']->val('new')->val(); |
||
| 55 | |||
| 56 | // http://code.google.com/p/phpquery/issues/detail?id=71 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
59% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 57 | // $doc = PhpQuery::newDocument('<select><option value="10">10</option><option value="10">20</option></select>'); |
||
| 58 | // $doc['select']->val('20')->dump(); |
||
| 59 | |||
| 60 | // http://code.google.com/p/phpquery/issues/detail?id=73 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
59% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 61 | // $doc = PhpQuery::newDocument('<input value=""/>'); |
||
| 62 | // var_dump($doc['input']->val(0)->val()); |
||
| 63 | |||
| 64 | // $a = null; |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
59% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 65 | // new CallbackReference($a); |
||
| 66 | // PhpQuery::callbackRun(new CallbackReference($a), array('new $a value')); |
||
| 67 | // var_dump($a); |
||
| 68 | |||
| 69 | // check next() inside (also, but separatly) |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
48% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 70 | // $inputs->dump(); |
||
| 71 | // foreach($inputs as $node) { |
||
| 72 | // } |
||
| 73 | // $inputs->dump(); |
||
| 74 | |||
| 75 | // http://code.google.com/p/phpquery/issues/detail?id=74 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
59% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 76 | // http://code.google.com/p/phpquery/issues/detail?id=31 |
||
| 77 | //$doc = PhpQuery::newDocument('<div class="class1 class2"/><div class="class1"/><div class="class2"/>'); |
||
| 78 | //$doc['div']->filter('.class1, .class2')->dump()->dumpWhois(); |
||
| 79 | |||
| 80 | // http://code.google.com/p/phpquery/issues/detail?id=76 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
55% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 81 | // mb_internal_encoding("UTF-8"); |
||
| 82 | // mb_regex_encoding("UTF-8"); |
||
| 83 | // $xml = PhpQuery::newDocumentXML('<документа/>'); |
||
| 84 | // |
||
| 85 | // $xml['документа']->append('<список></список>'); |
||
| 86 | // $xml['документа список'] = '<эл>1</эл><эл>2</эл><эл>3</эл>'; |
||
| 87 | // print "<xmp>$xml</xmp>"; |
||
| 88 | |||
| 89 | // zeromski 0.9.5 vs 0.9.1 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
53% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 90 | // PhpQuery::newDocumentXML('<xml><b></xml>')->dump(); |
||
| 91 | |||
| 92 | // http://code.google.com/p/phpquery/issues/detail?id=77 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
81% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 93 | // PhpQuery::newDocumentFile('http://google.com/') |
||
| 94 | // ->find('body > *')->dumpWhois(); |
||
| 95 | /*$XHTML = <<<EOF |
||
| 96 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" |
||
| 97 | "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
||
| 98 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="fr" lang="fr"> |
||
| 99 | <head> |
||
| 100 | <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> |
||
| 101 | <meta http-equiv="Content-Language" content="fr" /> |
||
| 102 | </head> |
||
| 103 | <body> |
||
| 104 | <div id="contenu_volets"> |
||
| 105 | <div id="contenu_voletGauche"> |
||
| 106 | <div id="contenu_navigation" class="bloc_arrondi blanc_10_10 administrable"> |
||
| 107 | <div class="bloc_arrondi_haut"> |
||
| 108 | <div class="bloc_arrondi_haut_gauche"></div> |
||
| 109 | <div class="bloc_arrondi_haut_droit"></div> |
||
| 110 | </div> |
||
| 111 | <div class="bloc_arrondi_centre"> |
||
| 112 | <div class="bloc_arrondi_centre1"> |
||
| 113 | <div class="bloc_arrondi_centre2 bloc_contenu administrable_contenu"></div> |
||
| 114 | </div> |
||
| 115 | </div> |
||
| 116 | <div class="bloc_arrondi_bas"> |
||
| 117 | <div class="bloc_arrondi_bas_gauche"></div> |
||
| 118 | <div class="bloc_arrondi_bas_droit"></div> |
||
| 119 | </div> |
||
| 120 | </div> |
||
| 121 | </div> |
||
| 122 | <div id="contenu_voletDroit"> |
||
| 123 | <div id="contenu_article" class="bloc_arrondi grisDegrade_10_10_341 administrable |
||
| 124 | redimensionnable"> |
||
| 125 | <div class="bloc_arrondi_haut"> |
||
| 126 | <div class="bloc_arrondi_haut_gauche"></div> |
||
| 127 | <div class="bloc_arrondi_haut_droit"></div> |
||
| 128 | </div> |
||
| 129 | <div class="bloc_arrondi_centre"> |
||
| 130 | <div class="bloc_arrondi_centre1"> |
||
| 131 | <div class="bloc_arrondi_centre2 bloc_contenu administrable_contenu |
||
| 132 | WAI_element-40-WAI_principal-30 WAI_contenu"> |
||
| 133 | <p class="contenu_filAriane justifier_non"> |
||
| 134 | Vous êtes ici : <span class="filAriane_contenu"></span> |
||
| 135 | </p> |
||
| 136 | <h1 id="IDcmsRef-page-titre">Editorial</h1> |
||
| 137 | <div id="IDcmsTag_article"></div> |
||
| 138 | <div class="nettoyeur"></div> |
||
| 139 | </div> |
||
| 140 | </div> |
||
| 141 | </div> |
||
| 142 | <div class="bloc_arrondi_bas"> |
||
| 143 | <div class="bloc_arrondi_bas_gauche"></div> |
||
| 144 | <div class="bloc_arrondi_bas_droit"></div> |
||
| 145 | </div> |
||
| 146 | </div> |
||
| 147 | </div> |
||
| 148 | <div id="contenu_voletPied"></div> |
||
| 149 | </div> |
||
| 150 | </body> |
||
| 151 | </html> |
||
| 152 | EOF; |
||
| 153 | PhpQuery::newDocumentXHTML($XHTML) |
||
| 154 | ->find('body:first > *')->dumpWhois();*/ |
||
| 155 | |||
| 156 | // http://code.google.com/p/phpquery/issues/detail?id=83 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
63% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 157 | //$doc = PhpQuery::newDocument('<select |
||
| 158 | //name="toto"><option></option><option value="1">1</option></select><div><input |
||
| 159 | //type="hidden" name="toto"/></div>'); |
||
| 160 | //print $doc['[name=toto]']->val('1'); |
||
| 161 | |||
| 162 | //$doc = PhpQuery::newDocumentFile('http://www.google.pl/search?hl=en&q=test&btnG=Google+Search'); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
57% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 163 | //print $doc; |
||
| 164 | |||
| 165 | // http://code.google.com/p/phpquery/issues/detail?id=88 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
66% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 166 | //$doc = PhpQuery::newDocumentXML('<foo><bar/></foo>'); |
||
| 167 | //$doc['foo']->find('bar')->andSelf()->addClass('test'); |
||
| 168 | //$doc->dump(); |
||
| 169 | |||
| 170 | // http://code.google.com/p/phpquery/issues/detail?id=90 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
54% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 171 | //print PhpQuery::newDocument('<html><body></body></html>') |
||
| 172 | // ->find('body') |
||
| 173 | // ->load('http://localhost/phpinfo.php'); |
||
| 174 | |||
| 175 | // http://code.google.com/p/phpquery/issues/detail?id=91 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
57% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 176 | // PhpQuery::newDocumentXML('<foo bar="abc"/><foo bar="bca"/>'); |
||
| 177 | // print pq('foo')->filter('[bar$=c]'); |
||
| 178 | |||
| 179 | // FIXME http://code.google.com/p/phpquery/issues/detail?id=93 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
49% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 180 | //$doc = '<head><title>SomeTitle</title> |
||
| 181 | //</head> |
||
| 182 | //<body bgcolor="#ffffff" text="#000000" topmargin="1" leftmargin="0">blah |
||
| 183 | //</body>'; |
||
| 184 | //$pq = PhpQuery::newDocument($doc); |
||
| 185 | //echo $pq; |
||
| 186 | |||
| 187 | # http://code.google.com/p/phpquery/issues/detail?id=94#makechanges |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
55% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 188 | //$doc = PhpQuery::newDocument(); |
||
| 189 | //$test = pq( |
||
| 190 | //' |
||
| 191 | //<li> |
||
| 192 | // <label>Fichier : </label> |
||
| 193 | // <input type="file" name="pjModification_fichier[0]"/> |
||
| 194 | // <br/> |
||
| 195 | // <label>Titre : </label> |
||
| 196 | // <input type="text" name="pjModification_titre[0]" class="pieceJointe_titre"/> |
||
| 197 | //</li> |
||
| 198 | //' |
||
| 199 | //); |
||
| 200 | |||
| 201 | // http://code.google.com/p/phpquery/issues/detail?id=96 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
60% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 202 | //$doc = PhpQuery::newDocument('<select name="section"><option |
||
| 203 | //value="-1">Niveau</option><option value="1">6°</option><option |
||
| 204 | //value="2">5°</option><option |
||
| 205 | //value="3">4°</option><option value="4">3°</option></select>'); |
||
| 206 | //$doc = PhpQuery::newDocument('<select name="section"><option |
||
| 207 | //value="-1">Niveau</option><option value="1">6°</option><option |
||
| 208 | //value="2">5°</option><option |
||
| 209 | //value="3">4°</option><option value="4">3°</option></select>'); |
||
| 210 | //print $doc['select']->val(3)->end()->script('print_source'); |
||
| 211 | //(16:27:56) jomofcw: $option_element = |
||
| 212 | //(16:27:56) jomofcw: pq('<option/>') |
||
| 213 | //(16:27:56) jomofcw: ->attr('value',$section['id']) |
||
| 214 | //(16:27:56) jomofcw: ->html($section['libelle']) |
||
| 215 | //(16:27:56) jomofcw: ; |
||
| 216 | //(16:29:27) jomofcw: where $section['libelle'] is from a database UTF-8 |
||
| 217 | //16:30 |
||
| 218 | //(16:30:20) jomofcw: the value of $section['libelle'] is exactly "3°" in database... |
||
| 219 | |||
| 220 | # http://code.google.com/p/phpquery/issues/detail?id=98 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
65% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 221 | //$doc = PhpQuery::newDocument('<select id="test"><option value="0">a</option><option |
||
| 222 | //value="10">b</option><option value="20">c</option></select>'); |
||
| 223 | //print $doc['select']->val(0)->end()->script('print_source'); |
||
| 224 | |||
| 225 | // http://groups.google.com/group/phpquery/browse_thread/thread/1c78f7e41fc5808c?hl=en |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
68% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 226 | //$doc = PhpQuery::newDocumentXML(" |
||
| 227 | //<s:Schema id='RowsetSchema'> |
||
| 228 | // <s:ElementType name='row' content='eltOnly'> |
||
| 229 | // <s:AttributeType name='ComparteElementoComun_ID' rs:number='1' |
||
| 230 | //rs:maydefer='true' rs:writeunknown='true'> |
||
| 231 | // <s:datatype dt:type='int' dt:maxLength='4' rs:precision='10' |
||
| 232 | //rs:fixedlength='true'/> |
||
| 233 | // </s:AttributeType> |
||
| 234 | // <s:AttributeType name='ComparteElementoComun' rs:number='2' |
||
| 235 | //rs:nullable='true' rs:maydefer='true' rs:writeunknown='true'> |
||
| 236 | // <s:datatype dt:type='string' dt:maxLength='100'/> |
||
| 237 | // </s:AttributeType> |
||
| 238 | // <s:extends type='rs:rowbase'/> |
||
| 239 | // </s:ElementType> |
||
| 240 | //</s:Schema>"); |
||
| 241 | //foreach($doc['Schema ElementType AttributeType'] as $campo){ |
||
| 242 | // if( count(pq($campo)->find('datatype'))==1 ){ |
||
| 243 | // var_dump(pq($campo)->find('datatype')->attr('dt:type')); // Should print "string" but prints "" |
||
| 244 | // } |
||
| 245 | //} |
||
| 246 | |||
| 247 | // http://code.google.com/p/phpquery/issues/detail?id=97 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
61% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 248 | //function jsonSuccess($data) { |
||
| 249 | // var_dump($data); |
||
| 250 | //} |
||
| 251 | //$url = 'http://api.flickr.com/services/feeds/photos_public.gne?tags=cat&tagmode=any&format=json'; |
||
| 252 | //PhpQuery::ajaxAllowHost('api.flickr.com'); |
||
| 253 | //PhpQuery::getJSON($url, array('jsoncallback' => '?'), 'jsonSuccess'); |
||
| 254 | //var_dump(json_decode($json)); |
||
| 255 | //require_once('../PhpQuery/Zend/Json/Decoder.php'); |
||
| 256 | //var_dump(Zend_Json_Decoder::decode($json)); |
||
| 257 | |||
| 258 | #var_dump(''.PhpQuery::newDocumentFile("http://www.chefkoch.de/magazin/artikel/943,0/AEG-Electrolux/Frischer-Saft-aus-dem-Dampfgarer.html")); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
58% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 259 | // var_dump(PhpQuery::newDocument( |
||
| 260 | // str_replace('<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN"> |
||
| 261 | // ', '', |
||
| 262 | // file_get_contents("http://www.chefkoch.de/magazin/artikel/943,0/AEG-Electrolux/Frischer-Saft-aus-dem-Dampfgarer.html" |
||
| 263 | // )))); |
||
| 264 | |||
| 265 | // http://code.google.com/p/phpquery/issues/detail?id=102 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
49% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 266 | // $doc = PhpQuery::newDocumentFileHTML('http://www.google.de'); |
||
| 267 | // //$doc = PhpQuery::newDocument(''); |
||
| 268 | // $images = $doc['img']->dump(); |
||
| 269 | // |
||
| 270 | // $foo = 'aaa'; |
||
| 271 | // var_dump(mb_ereg_match('^[\w|\||-]+$', $foo) || $foo == '*'); |
||
| 272 | // var_dump(preg_match('@^[\w|\||-]+$@', $foo) || $foo == '*'); |
||
| 273 | |||
| 274 | // http://code.google.com/p/phpquery/issues/detail?id=67 |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
74% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 275 | //$doc = PhpQuery::newDocumentXML("<node1/><node2/>"); |
||
| 276 | //$doc['node1']->data('foo', 'bar'); |
||
| 277 | //var_dump($doc['node1']->data('foo')); |
||
| 278 | //$doc['node1']->removeData('foo'); |
||
| 279 | //var_dump($doc['node1']->data('foo')); |
||
| 280 | //$doc['node1']->data('foo.bar', 'bar'); |
||
| 281 | //var_dump($doc['node1']->data('foo.bar')); |
||
| 282 | //var_dump(PhpQuery::$documents[$doc->getDocumentID()]->data); |
||
| 283 | |||
| 284 | // xhtml fragments |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
43% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 285 | //$doc = PhpQuery::newDocumentXHTML("<p><br/></p>"); |
||
| 286 | //print $doc; |
||
| 287 | |||
| 288 | $doc = PhpQuery::newDocument('<div id="content"></div><div id="content"></div>'); |
||
|
0 ignored issues
–
show
The method
newDocument() does not seem to exist on object<PhpQuery>.
This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history...
|
|||
| 289 | //$content_string = str_repeat('a', 99988); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
59% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 290 | $content_string = str_repeat(str_repeat('a', 350)."\n", 350); |
||
| 291 | //var_dump(strlen($content_string)); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
75% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 292 | ?><pre class='1'><?php |
||
| 293 | //print $content_string; |
||
| 294 | ?></pre><?php |
||
| 295 | pq('#content')->php('echo $content_string;'); |
||
| 296 | //pq('#content')->php('echo '.var_export($content_string, true)); |
||
|
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
73% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
|
|||
| 297 | $doc->dumpTree(); |
||
| 298 | ?><pre class='2'><?php |
||
| 299 | var_dump($doc->php()); |
||
| 300 | ?></pre><?php |
||
| 301 | eval('?>'.$doc->php()); |
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.
The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.
This check looks for comments that seem to be mostly valid code and reports them.