Passed
Pull Request — master (#2)
by Mark
02:00
created

syntax.php (8 issues)

1
<?php
2
/**
3
 * Plugin Now: Inserts Talis code for SIOC comments widget
4
 * 
5
 * DEPRECATED!!!
6
 */
7
 
8
// must be run within DokuWiki
9
if(!defined('DOKU_INC')) die();
10
 
11
if(!defined('DOKU_PLUGIN')) define('DOKU_PLUGIN',DOKU_INC.'lib/plugins/');
1 ignored issue
show
The constant DOKU_INC was not found. Maybe you did not declare it correctly or list all dependencies?
Loading history...
12
require_once(DOKU_PLUGIN.'syntax.php');
13
 
14
/**
15
 */
16
class syntax_plugin_dokusioc extends DokuWiki_Syntax_Plugin {
0 ignored issues
show
The type DokuWiki_Syntax_Plugin was not found. Maybe you did not declare it correctly or list all dependencies?

The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:

filter:
    dependency_paths: ["lib/*"]

For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths

Loading history...
17
 
18
    function getInfo(){
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
19
      return array(
20
        'author' => 'Michael Haschke',
21
        'email'  => '[email protected]',
22
        'date'   => '2009-02-16',
23
        'name'   => 'SIOC comments widget',
24
        'desc'   => 'Only a stub for further development. It is doing nothing!',
25
        'url'    => 'http://eye48.com/go/dokusioc',
26
      );
27
    }
28
 
29
    function getType() { return 'substition'; }
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
30
    function getSort() { return 999; }
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
31
    function connectTo($mode) { $this->Lexer->addSpecialPattern('\[SIOCCOMMENTS\]',$mode,'plugin_dokusioc'); }
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
32
    function handle($match, $state, $pos, &$handler){ return array($match, $state, $pos); }
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
33
    function render($mode, &$renderer, $data) {
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
34
    /*
35
      if($mode == 'xhtml'){
36
          $renderer->doc .= '<div class="sioc-has_reply"></div><script type="text/javascript" charset="utf-8" src="http://n2.talis.com/svn/playground/kwijibo/javascript/sioc-comments/bundle.js"></script>';
37
          return true;
38
      }
39
      */
40
      return false;
41
    }
42
}
43
44