/ - Diff - Club Drupal - Forge Centrale Marseille

       <?php print $scripts; ?>
       <script type="text/javascript"><?php /* Needed to avoid Flash of Unstyled Content in IE */ ?> </script>
     </head>
     <body>
     <body class="advanced-help-popup-body">
       <div id="page">
         <div id="header">
           <?php if (!empty($search_box)): ?>

     name = Advanced help
     description = Allow advanced help and documentation.
     description = Provide extended help and documentation.
     core = 7.x
     ; Information added by Drupal.org packaging script on 2013-12-12
     version = "7.x-1.1"
     attributions[click_icon][type] = 'asset'
     attributions[click_icon][exception] = '#2460769'
     attributions[click_icon][author] = 'Gisle Hannemyr'
     attributions[click_icon][hide] = TRUE
     attributions[click_icon][title] = 'click_icon.png'
     attributions[click_icon][license] = 'Creative Commons 0'
     attributions[click_icon][license_url] = 'https://creativecommons.org/publicdomain/zero/1.0/'
     ; Information added by Drupal.org packaging script on 2015-03-27
     version = "7.x-1.2"
     core = "7.x"
     project = "advanced_help"
     datestamp = "1386871727"
     datestamp = "1427460482"

       $output = array();
       // Print a search widget.
       $output['advanced_help_search'] = module_exists('search') ? drupal_get_form('advanced_help_search_form') : t('Enable the search module to search help.');
       $output['advanced_help_search'] = module_exists('search') ? drupal_get_form('advanced_help_search_form') : array('#markup' => t('Enable the search module to search help.'));
       $breadcrumb = array();
       if ($module) {
-...
         $result = db_query('SELECT * FROM {system}');
         foreach ($result as $info) {
           $module_info = unserialize($info->info);
           $modules[$info->name] = $module_info['name'];
           $modules[$info->name] = isset($module_info['name']) ? $module_info['name'] : $info->name;
+        }
         asort($modules);
-...
           'html' => TRUE)
         );
+      }
       else {
       elseif (user_access('view advanced help topic')) {
         return l($text, "help/$module/$topic", array(
           'attributes' => array(
             'class' => $class,
-...
         $output = file_get_contents($file);
         if (isset($info['readme file']) && $info['readme file']) {
           // Readme files are treated as plain text: filter accordingly.
           $output = check_plain($output);
           $ext = pathinfo($file, PATHINFO_EXTENSION);
           if ('md' == $ext && module_exists('markdown')) {
             $filters = module_invoke('markdown', 'filter_info');
             $md_info = $filters['filter_markdown'];
             if (function_exists($md_info['process callback'])) {
               $function = $md_info['process callback'];
               $output = '<div class="advanced-help-topic">' . filter_xss_admin($function($output, NULL)) . '</div>';
+            }
             else {
               $output = '<div class="advanced-help-topic"><pre class="readme">' . check_plain($output) . '</pre></div>';
+            }
+          }
           else {
             $output = '<div class="advanced-help-topic"><pre class="readme">' . check_plain($output) . '</pre></div>';
+          }
           return $output;
+        }
         // Make some exchanges. The strtr is because url() translates $ into %24
-...
             $navigation = '<div class="help-navigation clear-block">';
             if ($prev) {
               $navigation .= advanced_help_l('<< ' . $topics[$prev[0]][$prev[1]]['title'], "help/$prev[0]/$prev[1]", array('attributes' => array('class' => 'help-left')));
               $navigation .= advanced_help_l('«« ' . $topics[$prev[0]][$prev[1]]['title'], "help/$prev[0]/$prev[1]", array('attributes' => array('class' => 'help-left')));
+            }
             if ($up) {
               $navigation .= advanced_help_l(t('Up'), $up, array('attributes' => array('class' => $prev ? 'help-up' : 'help-up-noleft')));
+            }
             if ($next) {
               $navigation .= advanced_help_l($topics[$next[0]][$next[1]]['title'] . ' >>', "help/$next[0]/$next[1]", array('attributes' => array('class' => 'help-right')));
               $navigation .= advanced_help_l($topics[$next[0]][$next[1]]['title'] . ' »»', "help/$next[0]/$next[1]", array('attributes' => array('class' => 'help-right')));
+            }
             $navigation .= '</div>';
-...
         $output = '<div class="advanced-help-topic">' . $output . '</div>';
         drupal_alter('advanced_help_topic', $output, $popup);
         return $output;
+      }
+    }
-...
         $ini = array('topics' => array(), 'settings' => array());
         $help_path = drupal_get_path('module', 'advanced_help') . '/modules';
         foreach (module_list() as $module) {
           $module_path = drupal_get_path('module', $module);
         foreach (array_merge(module_list(), list_themes()) as $plugin) {
           $module = is_string($plugin) ? $plugin : $plugin->name;
           $module_path = drupal_get_path(is_string($plugin) ? 'module' : 'theme', $module);
           $info = array();
           if (file_exists("$module_path/help/$module.help.ini")) {
             $path = "$module_path/help";
-...
           elseif (!file_exists("$module_path/help")) {
             // Look for one or more README files.
             $files = file_scan_directory("./$module_path",
               '/^(README|readme).*\.(txt|TXT)$/', array('recurse' => FALSE));
               '/^(readme).*\.(txt|md)$/i', array('recurse' => FALSE));
             $path = "./$module_path";
             foreach ($files as $name => $fileinfo) {
               $info[$fileinfo->filename] = array(
-...
       $css = drupal_add_css();
       // Remove theme css.
       foreach ($css as $media => $types) {
         if (isset($css[$media]['theme'])) {
           $css[$media]['theme'] = array();
       foreach ($css as $key => $value) {
         if ($value['group'] == CSS_THEME) {
           $exclude[$key] = FALSE;
+        }
+      }
       $css = array_diff_key($css, $exclude);
       $variables['styles']            = drupal_get_css($css);
       $variables['scripts']           = drupal_get_js();

     .advanced-help-link {
       background: transparent url('help.png') no-repeat top left;
       background-position: 0px 0px;
       display: block;
       float: left; /* this is cheesy, I know */
       display: inline-block;
       height: 12px;
       margin-top: 2px;
       padding: 0px;

drupal7/sites/all/modules/advanced_help/help-popup.css
96	96	margin: 0.4em 0 0.4em .5em; /* LTR */
97	97	}
98	98
99
100	99	#content {
101	100	margin: .5em 1em 1em 1em;
102	101	}

     .advanced-help-topic code,
     .advanced-help-topic pre {
       background: #f1f1f1;
       border: 1px solid #444;
       border: 1px solid #ccc;
       display: block;
       margin: 1em;
       padding: .2em;
       padding: .4em;
+    }
     .advanced-help-topic pre.readme {
       background: white;
       border: none;
       margin: 0em;
       padding: .4em;
+    }
     .advanced-help-topic h3,
-...
       font-weight: normal;
+    }
     .attribution {
       font-size: 0.8em;
       color: #aaa;
+    }
     .help-left {
       display: block;
       float: left; /* LTR */
-...
       display: block;
       float: left; /* LTR */
       margin: 0 5%;
       width: 4%;
       text-align: center;
       width: 10%;
+    }
     .help-up-noleft {
-...
       margin: .5em;
+    }
     .help-block {
       display: block;
       clear: both;
+    }
     .help-img-left {
       margin-right: 1.5em;
       border: solid 1px #ccc;
+    }
     .ta-center {
       margin: 1em;
       text-align: center;
+    }
     .help-img-center {
       margin-left: auto;
       margin-right: auto;
       border: solid 1px #ccc;
+    }
     .help-navigation {
       border-top: 1px dotted #ccc;
+    }

     [readme]
     title = README
     weight = -11
     [using-advanced-help]
     title = Using advanced help
-...
     title = Translating advanced help
     [ini-file]
     title = Help .ini file format
     line break = TRUE
     title = Advanced help .ini file format
     line break = FALSE
     [why-advanced-help]
     title = Why advanced help?

     The advanced help configuration file is in simple .ini file format, divided into sections for each help file, plus an optional section for global settings that might be inherited for each help file.
     <p>The advanced help configuration file is in simple .ini file format.
     It has an optional section for global settings that might be inherited
     for each help file, followed by sections for each help file.</p>
     The first line of an advanced help ini file should be ;&#x24;Id &#x24; which will be a comment providing the CVS identifier for the file. The ; indicates a comment character. Anything after the ; will be ignored.
     <p>Global settings may be put into a section named <code>[advanced help
     settings]</code>.  This means that this name is reserved and it cannot
     be a help file in any module or theme. The following settings may be
     set in this section, with the default value (if any) in brackets.</p>
     Global settings may be put into a section named <strong>[advanced help settings]</strong> -- this means that this name is reserved and it cannot be a help file in any module. The following settings may be set in this section:
     <dl>
     <dt><strong>line break</strong></dt>
     <dd>If set to any value, the line break filter will be applied to all help files defined by this module, unless that help file specifically is set otherwise. By default, the line break filter is not applied; however, help files can be much easier to write with the line break filter on.</dd>
     <dt><strong>navigation</strong></dt>
     <dd>If set to true, the navigation will be displayed at the end of the help topic: previous topic, next topic, and child topics.</dd>
     <dt><strong>css</strong></dt>
     <dd>Specify a css file that will be used for all help files (unless overridden), including the .css extension. This .css file must reside in the help directory along with the .html files, and will not be affected by translation.</dd>
     <dt><strong>name</strong></dt>
     <dd>May be set to override the module name as displayed in both the module index as well as the navigation and breadcrumb trail. In general this does not need to be set, but a few modules may want to use a more friendly name than appears in the .info file.</dd>
     <dt><strong>index name</strong></dt>
     <dd>This may be set to change the name of the module in the module index. It overrides the 'name' setting above, as well as the module name in its .info file.</dd>
     <dt><strong>hide</strong></dt>
     <dd>This may be used to hide a module in the module index. This is particularly useful for modules who insert their help files into the hierarchy of another module, as might be done by modules that extend Views or CCK. By setting "hide = TRUE" the module will not appear as its own entry.</dd>
     <dt><code>line break</code> (FALSE)</dt>
     <dd>If set, the line break filter will be applied to all help files
     defined by this module or theme, unless that help file specifically is
     set otherwise.  The line break converts line breaks
     into <code>br</code> and <code>p</code> tags automatically.</dd>
     <dt><code>navigation</code> (TRUE)</dt>
     <dd>If set, this navigation will be displayed at the end of the topic:
     <em>previous topic</em>, Up (parent), <em>next topic</em>.</dd>
     <dt><code>css</code></dt>
     <dd>Specify a css file that will be used for all help files (unless
     overridden), including the .css extension. This .css file must reside
     in the help directory along with the .html files, and will not be
     affected by translation.</dd>
     <dt><code>name</code></dt>
     <dd>May be set to override the module or theme name as displayed in
     both the module/theme index as well as the navigation and breadcrumb
     trail. Usually, this is not set, but for some projects you may want to
     use a more friendly name than appears in the project's .info file.</dd>
     <dt><code>index name</code></dt>
     <dd>This may be set to change the name of the module or theme in the
     module/theme index. It overrides the <code>name</code> setting above,
     as well as the project's name in its .info file.</dd>
     <dt><code>hide</code> (FALSE)</dt>
     <dd>This may be used to hide a module or theme in the module/theme
     index. This is particularly useful for modules who insert their help
     files into the hierarchy of another module or theme, as might be done
     by modules that extend <strong>Views</strong> or derived themes that
     extend base themes like <strong>Zen</strong>. By setting this to TRUE
     the project will not appear as its own entry.</dd>
     </dl>
     Each section after that will correspond to a single help file, and each one may have the following settings:
     <p>Each section after that will correspond to a single help file for a
     single topic.  It starts with the topic name in square brackets
     (e.g. <code>[ini-file]</code>).  The following settings may be set for
     each file/topic, with the default value (if any) in brackets.</p>
     <dl>
     <dt><strong>title</strong></dt>
     <dd>The title of the topic, presented to the user and used in links. If you have special characters in your title, be sure to enclose it in quotes.</dd>
     <dt><strong>file</strong></dt>
     <dd>The filename, without the .html extension, used for the topic. This is optional; if not specified, the topic name wil be the file name.</dd>
     <dt><strong>weight</strong></dt>
     <dd>The weight, used for sorting topics on the administration page. Defaults to 0 of unspecified. Items with the same weight are sorted alphabetically.</dd>
     <dt><strong>parent</strong></dt>
     <dd>The topic ID to use in a hierarchy; children will be listed beneath parents in the topic list, and will have the parent in their breadcrumb trail. You may parent this topic to another module's topic by using module%topic as the identifier. For example, 'views%display' will make this a child of the 'display' topic in the 'views' module.</dd>
     <dt><strong>line break</strong></dt>
     <dd>If set to true, linebreaks will be converted into br and p tags automatically. If unspecified, will default to off. Set to 0 to disable the filter if this has been turned on in the global settings.</dd>
     <dt><strong>css</strong></dt>
     <dd>Specify a css file that will be used for this file. This .css file must reside in the help directory along with the .html files. This will override any .css file added by the global system.</dd>
     <dt><strong>popup width</strong></dt>
     <dd>The width in pixels of the popup window.  Defaults to 500 if unspecified.</dd>
     <dt><strong>popup height</strong></dt>
     <dd>The height in pixels of the popup window.  Defaults to 500 if unspecified.</dd>
     <dt><code>title</code></dt>
     <dd>The title of the topic, presented to the user and used in
     links. If you have special characters in your title, be sure to
     enclose it in quotes.  (This setting is currently not optional.)</dd>
     <dt><code>file</code> (topic name)</dt>
     <dd>The filename, without the .html extension, used for the file with
     the help text for the topic. This is optional; if not specified, the
     topic name wil be the file name.</dd>
     <dt><code>weight</code> (0)</dt>
     <dd>The weight, used for sorting topics on the administration
     page. The default is 0 (zero) if unspecified. Items with the same weight
     are sorted alphabetically.</dd>
     <dt><code>parent</code></dt>
     <dd>The topic ID to use in a hierarchy; children will be listed
     beneath parents in the topic list, and will have the parent in their
     breadcrumb trail. You may parent this topic to a topic in another
     module or theme by using <code>module%topic</code>
     or <code>theme%topic</code> as the identifier,
     where <code>module</code> or <code>theme</code> is the project's short
     name. For example if parent is set to, '<code>views%display</code>',
     the topic will be regarded as a child of the
     <code>display</code> topic in the <strong>Views</strong> module.</dd>
     <dt><code>line break</code> (FALSE)</dt>
     <dd>Set the line break filter for this topic. Set to FALSE to disable
     the line break filter if this has been turned on in the global
     settings.</dd>
     <dt><code>css</code></dt>
     <dd>Specify a css file that will be used for this file. This .css file
     must reside in the help directory along with the .html files. This
     will override any .css file added by the global settings.</dd>
     <dt><code>popup width</code> (500)</dt>
     <dd>The width in pixels of the popup window.</dd>
     <dt><code>popup height</code> (500)</dt>
     <dd>The height in pixels of the popup window.</dd>
     </dl>
     For example, here is a version of the <strong>advanced_help.help.ini</strong> file:
     <p>For example, here is a version of the <code>advanced_help.help.ini</code> file:</p>
     <pre>
     [readme]
     title = README
     weight = -11
     [using-advanced-help]
     title = "Using advanced help"
     title = Using advanced help
     weight = -10
     [translation]
-...
     [ini-file]
     title = Help .ini file format
     line break = FALSE
     [why-advanced-help]
     title = Why advanced help?
     line break = TRUE
     </pre>
     </pre>

     <h2 id="project-description">Synopsis</h2>
     <p>The <strong>Advanced help</strong> module provides a framework that allows
     module and theme developers integrate help texts in a Drupal site.</p>
     <p>These help texts are stored in ordinary <code>.html</code>-files
     that lives in the file system (as opposed to the database).  These
     files are distributed from the project Drupal.org repo in the same
     package as the module or theme, and placed in a subdirectory named
     <code>help</code> in the project or theme directory.  This means that
     the help texts can be easiely kept in sync with the project they
     provide help texts for, but also that read access to these files
     are not managed by any content access restrictions imposed by Drupal.</p>
     <p>The help texts can be marked up with standard HTML, but are
     rendered within your site's Drupal theming structure.</p>
     <p>If the module or theme author does not make use of the full
     <em>Advanced help</em> framework, but if there is a
     <code>README.md</code> or <code>README.txt</code> in the package,
     the content of that file will be shown instead.</p>
     <p>The help texts may appear in a popup or not as the module prefers.
     By taking away access to view the popups, a site can hide popups from
     users.</p>
     <p>The help texts can be placed in a hierarchy, allowing for top down
     navigation of help.</p>
     <p>The hierarchy is tied into Drupal's search system. If this is
     enabled, all help texts are fully indexed. This means that the entire
     contents of the advanced help set of pages can be searched for
     keywords.</p>
     <h2 id="use">Using the module</h2>
     <p>By itself, this module doesn't do much.  The <strong>Advanced
     help</strong> assists other modules and themes in showing help texts.
     Nothing will show up until you enable at least one other module that
     makes use of the advanced help framework or comes with a file
     named <code>README.md</code> or <code>README.txt</code>.  However, it
     comes with a small companion demo module named
     <strong>Advanced help example</strong> to demonstrate how it works.
     For more extensive example of use of the advanced help features, see
     the <strong>Views</strong> project.</p>
     <h2 id="project-recommended">Recommended modules</h2>
     <ul>
     <!--
     <li><a href="https://www.drupal.org/project/markdown">Markdown filter</a>:<br>
     When this module is enabled, display of any <code>README.md</code> the
     module shows will be rendered with markdown.</li>
     -->
     <li><a href="https://www.drupal.org/project/attributions">Attributions</a>:<br>
     When this module is enabled, attributions of third party content used
     by the project (i.e. some text from Wikipedia) will be available in an
     attribution block and on an atribution page.</li>
     </ul>
     <h2 id="support-status">Support status</h2>
     <p>Reported bugs for the Drupal 7 branch will be fixed in a timely
     manner.  Bugs in the issue queue for the Drupal 6 branch will only be
     fixed if accompanied with a patch, after the patch has been reviewed
     and tested by the community.  No Drupal 8 version is currently under
     development.  Post a message in
     the <a href="https://www.drupal.org/node/1928218">issue queue</a> if
     you're interested in managing a port of the project to to Drupal
 . Older versions are no longer supported.</p>
     <p>Community support in the form of patches are very welcome for both
     Drupal 6 and Drupal 7 versions, and will be given priority. For QA,
     the project needs community support in the form of reviews of patches,
     development versions and releases.</p>
     <p>The primary goal of the module is to remain <strong>light-weight
     and simple</strong>.  This means that not all feature requests will be
     implemented, even if they are a good idea.  Feature requests
     accompanied by patches are more likely to make it into a release.</p>
     <p>The maintainer hopes that the community is willing to help out by
     answering &amp; closing support requests.</p>
     <!--
     <h2 id="project-problems">Known problems</h2>
     -->
     <h2 id="project-maintainers">Credits</h2>
     <ul>
     <li><a href="https://www.drupal.org/u/merlinofchaos"">merlinofchaos</a> (52 commits, original creator)</li>
     <li><a href="https://www.drupal.org/u/redndahead">redndahead</a> (8 commits)</li>
     <li><a href="https://www.drupal.org/u/dmitrig01">dmitrig01</a> (3 commits)</li>
     <li><a href="https://www.drupal.org/u/amitgoyal">amitgoyal </a> (5 commits)</li>
     <li><a href="https://www.drupal.org/u/gisle">gisle</a> (current maintainer)</li>
     </ul>

     <p>To translate advanced help, first create a <b>translations/help/$language</b> directory
     in the module directory. Then, copy the .ini file and all .html files from
     the help directory.</p>
     <p>To translate advanced help, first create a
     directory <code>translations/help/<em>language</em></code> in the
     module directory. Then, copy the .ini file and all the .html files
     from the help directory into this.  If you need to alter an image to
     use it in a translation, you also put the altered image there.</p>
     <p>The .ini file only needs to keep the titles, and if there is a 'name' or 'index name' setting in the 'advanced help settings' portion, that should be retained. Any retained settings should be translated. The rest of the data in the .ini file may be discarded or ignored.</p>
     <p>The .ini file only needs to keep the titles, and if there is
     a <code>name</code> or <code>index name</code> setting in the
     'advanced help settings' portion, that should be retained. Any
     retained settings should be translated. The rest of the data in the
     .ini file may be discarded or ignored.</p>
     <p>Each file should then be translated in place.</p>
     <p>When translating a .html file, you will find that the <b>path</b> keyword will lead to the original directory. If you must translate items that are linked, such as images, use <b>trans_path</b> instead, which will lead to the translated directory. This will allow you to pick and choose which linked items, if any, will be translated.</p>
     <p>When translating a .html file, you will find that
     the <code>&amp;path&amp;</code> keyword will lead to the original
     directory. If you must translate items that are linked, such as images
     containing text, use <code>&amp;trans_path&amp;</code> instead, which
     will lead to the translated directory. This will allow you to pick and
     choose which linked items, if any, will be translated.</p>

     <p>The <em>Advanced help</em> system is a pluggable system that provides advanced help facilities for Drupal and its modules. Although the advanced help does not provide general help by itself, it provides a powerful and easy framework that modules may use to provide their own help.
     </p>
     <p>The <strong>Advanced help</strong> module provides a framework that
     allows module and theme developers integrate help texts in a Drupal
     site.  Although the advanced help does not provide general help by
     itself, it provides a powerful and easy framework that modules and
     themes may use to provide their own help.</p>
     <p>
     Modules utilizing <em>Advanced help</em> should create a 'help' subdirectory inside their
     module's directory. Place the file MODULENAME.help.ini in this subdirectory, formatted
     similar to the following example:
     </p>
     <p>Modules and themes utilizing <strong>Advanced help</strong> should
     create a subdirectory named <code>help</code> inside their own main
     directory. Place the file
     <em>MODULENAME</em>.help.ini (resp. <em>THEMENAME</em>.help.ini) in this subdirectory.
     formatted similar to the following example:</p>
     <pre>
     [about-php]
     title = About PHP
     file = about-php
     weight = -10
     [history]
     title = History of PHP
     parent = about-php
     [usage]
     title = Usage of PHP
     weight = 1
     [security]
     title = Security of PHP
     weight = 2
     [syntax]
     title = PHP syntax
     parent = usage
     </pre>
     <p>This file defines five help topics (inside the square brackets, and
     some settings for them.
     See: <a href="&topic:advanced_help/ini-file&">Advanced help .ini file format</a> for
     a list of defined settings.</p>
     <p>All topics are addressed by the module or theme providing the
     topic, and by the topic id. To produce a themed link to popup
     about a topic, use the a format similar to the following example:</p>
     <!-- D6
     <pre>
     $output = theme('advanced_help_topic', 'help_example', 'about-php');
     $output .= '&nbsp;' . t('Click the help icon!');
     </pre>
     -->
     <!-- D7 -->
     <pre>
     $output = theme('advanced_help_topic', array(
       'module' => 'help_example',
       'topic' => 'about-php',
     ));
     $output .= '&nbsp;' . t('Click the help icon!');
     </pre>
     <p>This produces the following output:</p>
     <pre>
     &lt;a class="advanced-help-link" title="About PHP"
       onclick="var w=window.open(this.href, 'advanced_help_window',
       'width=500,height=500,scrollbars,resizable');
       w.focus(); return false;"
       href="/help/help_example/about-php?popup=1"&gt;
     &lt;span&gt;Help&lt;/span&gt;
     &lt;/a&gt;
      Click the help icon!
     &lt;/div&gt;
     </pre>
     <p>This produces a clickable help icon like the one shown below:</p>
     <div class="ta-center">
     <img class="help-img-center" alt="clickable icon" src="&path&click_icon.png" width="180" height="90" border="0" />
     </div>
     <p>Inside your help file, you may link to other help topics using this format:</p>
     <pre>
     &lt;a href="&amp;topic:module/topic&amp;"&gt;topic&lt;/a&gt;
     </pre>
     <p>This format will ensure the popup status remains consistent when
     switching between links.</p>
     <p>To reference items within the help directory, such as images you
     wish to embed  within the help text, use:</p>
     <pre>
     [buses]
     title = "How buses are tied into the system"
     file = buses
     &lt;img src="&amp;path&amp;example.png"/&gt;
     &lt;img src="&amp;trans_path&amp;example.png"/&gt;
     </pre>
     <p>The latter is to refer to a translated version of the image if it differs from the original.</p>
     [TOPIC_ID]
     title = "Title of topic".
     file = filename of topic, without the .html extension.
     weight = How important the topic is on the index page.
     parent = The optional topic parent to use in the breadcrumb,
              either topic or module%topic.
     <p>To reference any normal path in the site, use:</p>
     <pre>
     &lt;a href="&amp;base_url&amp;admin/settings/site-configuration"&gt;anchor text&lt;/a&gt;
     </pre>
     <p>
     All topics are addressed by the module providing the topic, and by the topic
     id. To embed links, use the following format:
     </p>
     <code>
     $output .= theme('advanced_help_topic', $module, $topic);
     </code>
     <p><strong>NOTE: </strong> In previous versions <strong>Advanced
     help</strong> did not require the &amp;'s to be wrapped around
     <code>topic:</code>, <code>path</code>, and <code>base_url</code>.
     This is currently still supported, but may be removed in a future
     version.  By adding the &amp;'s these tokens are now not limited
     to <code>href=""</code> and <code>src=""</code> parameters.</p>
     <h2 id="access-control">Access control</h2>
     <p>Inside your help file, link to other topics using the format <strong>&lt;a href="&amp;topic:module/topic&amp;"&gt;</strong>. This
     format will ensure the popup status remains consistent when switching between links.</p>
     <p>When this module is installed, users with the
     <code>view advanced help index</code>
     permission can access the advanced help index by going to
     <em>Administer &rarr; Advanced Help</em>
     (<code>admin/advanced_help</code>). Additional permissions
     <code>view advanced help topic</code>  and
     <code>view advanced help popup</code>
     enable users to access the actual help pages and popups.</p>
     <p>Use <strong>&lt;a href="&amp;path&amp;example.jpg"&gt;</strong> to reference items
     within the help directory, such as images you wish to embed within the help text.</p>
     <p>The help texts are stored as plain .html-files and can, unless
     protected, be accessed by anyone who knows their URL.  To protect
     them, place the following four lines in a file named
     <code>.htaccess</code> in project's <code>help</code> directory:</p>
     <p>Use <strong>&lt;a href="&amp;base_url&amp;admin/settings/site-configuration"&gt;</strong> to reference any normal path in the site.</p>
     <pre>
     &lt;Files *\.html&gt;
     Order Allow,Deny
     Deny from all
     &lt;/Files&gt;
     </pre>
     <p>If the search module is enabled, the contents of help system will be indexed on cron. If you enable new modules and wish to immediately index its help text, visit the "Administration -> Reports -> Status report" and click the "Run cron manually" link.</p>
     <p>It as the responsibility of the project author to make sure this
     type of protection is in place if the project's author has help files
     that merits protection from direct access.</p>
     <p>Example: <a href="&path&nowhere.jpg">Don't click this!</a></p>
     <p>See also this tracker in the project's issue queue:
     <a href="https://www.drupal.org/node/1980936">#1980936 Typing complete path to .html help files in module bypasses user permissions</a>.</p>
     <p>See: <a href="&topic:advanced_help/ini-file&">ini file format</a></p>
     <h2 id="search">Search</h2>
     <p><strong>NOTE: </strong> In previous versions Advanced Help did not require the &amp;'s wrapped around the topic:, path:, and base_url: links.  This
     is currently still supported, but may be removed in a future version.  By adding the &'s these tokens are now not limited to href="" and src="" paramaters.</p>
     <p>If the core <strong>Search</strong> module is enabled, the contents
     of the advanced help framework will be indexed on cron. If you enable
     new modules or themes and wish to immediately index their help text,
     navigate to <em>Administration → Reports → Status report</em> and click the link
     “run cron manually”.</p>

     The advanced help system was designed to replace the original Drupal help system, which has several flaws that make it hard to create new help, hard to maintain existing help, and particularly hard to access help.
     The <strong>Advanced help</strong> framework was designed to replace the original Drupal help system, which has several flaws that make it hard to create new help, hard to maintain existing help, and particularly hard to access help.
     The primary goal, then, is to increase the accessibility of help, meaning the ability of both the user and the help text author to access the needed tools to use, create, maintain and translate the help.
     This system is completely separate from Drupal's hook_help(). In Drupal 6, it actually co-exists with it; in the future, it is hoped that it will completely replace it allowing hook_help() to be deprecated and removed.
     This system is completely separate from Drupal's <code>hook_help()</code>. In Drupal 6 and 7, it actually co-exists with it; in the future, it is hoped that it will completely replace it allowing <code>hook_help()</code> to be deprecated and removed.
     Messages added to the top of a page are not really "help". Often these messages are an introduction to a form or a short blurb telling a user what to do with a particular page. The problem is, these messages are always there, they are easily ignored, and they come before the actual page. In general, when users are learning, they want to see the page first, then ask questions. The reverse order is much less conducive to actually teaching a user how to use something. By allowing help to be available on request, the system conforms more naturally to how most people work.
     Messages added to the top of a page are not really “help”. Often these messages are an introduction to a form or a short blurb telling a user what to do with a particular page. The problem is, these messages are always there, they are easily ignored, and they come before the actual page. In general, when users are learning, they want to see the page first, then ask questions. The reverse order is much less conducive to actually teaching a user how to use something. By allowing help to be available on request, the system conforms more naturally to how most people work.
     <h3><strong>Advanced help is organized by topic</strong></h3>
     With the hook_help() method, help text is organized by URL path. This is fine if you have help text describing how to use a particular page or what a particular page does, but ultimately is limiting because manuals and documentation are usually grouped by topic, and those topics are determined by the material itself.
     <h2>Advanced help is organized by topic</h2>
     With the <code>hook_help()</code> method, help text is organized by URL path. This is fine if you have help text describing how to use a particular page or what a particular page does, but ultimately is limiting because manuals and documentation are usually grouped by topic, and those topics are determined by the material itself.
     Advanced help allows the documentation author to organize topics as he or she sees fit; the only restriction, really, is that each individual chunk of text needs to stand on its own as a discrete topic.
     <strong>Advanced help</strong> allows the documentation author to organize topics as he or she sees fit; the only restriction, really, is that each individual chunk of text needs to stand on its own as a discrete topic.
     What's more, modules can insert their topics into another module's hierarchy. This would allow the Drupal core to create a task based help navigation system which allows modules insert topics into that navigation fluidly. This allows modules to continue to keep their systems separate, yet integrate into the main system.
     What's more, modules and themes can insert their topics into another's hierarchy. This would allow the Drupal core to create a task based help navigation system which allows modules and themes to insert topics into that navigation fluidly. This allows modules and themes to continue to keep their systems separate, yet integrate into the main system.
     <h3><strong>Advanced help topics are processed HTML in their own files</strong></h3>
     This separation makes it easy to find and modify. Currently, everything is lumped together in hook_help() in PHP strings that are run through t(), and there is a fair amount of PHP code necessary in this system that actually gets in the way of writing good, explanatory text.
     <h2>Advanced help topics are processed HTML in their own files</h2>
     This separation makes it easy to find and modify. Currently, everything is lumped together in <code>hook_help()</code> in PHP strings that are run through <code>t()</code>, and there is a fair amount of PHP code necessary in this system that actually gets in the way of writing good, explanatory text.
     In fact, requiring a documentation author to understand PHP at all is a detriment. The idea that documentation writers need to have PHP development as a skill seriously reduces the number of available contributors. HTML, on the other hand, is a much more common skill, is relatively easy to learn, and the amount of HTML needed to write documentation is only a little bit more than the HTML used in forum posts.
     Another benefit to not using PHP is that the files themselves are safe. They are unlikely to include malicious PHP code that could take over the server or do worse things. This means that these files can be used relatively easily on the drupal.org hardware so that a module's help files can be made immediately available without needing to download the module. It also means that descriptions of the module can be made on drupal.org that are version aware, can be corrected easily in CVS with patches, but can also be made available with the module so that drupal.org is not required.
     Another benefit to not using PHP is that the files themselves are safe. They are filtered to escape malicious script code that could take over the server or do worse things. This means that these files can be used relatively easily on Drupal.org itself. It also means that descriptions of the project pulled from the project's help pages or README.txt or README.md can be made on the project's Drupal.org without the need to download the module or theme to look at the contents of these files.  This also simplifies maintenance, as the files can be corrected easily by patches, which are updated by tyhe maintainer and pushed to git.
     This also means that we could, if we wanted, package the drupal.org handbooks, or a subset of them, directly into a drupal distribution, or a drupal add-on, so that Drupal administrators can have Drupal help without needing to visit drupal.org. This can be valuable in locked down corporate environments and on planes. But more importantly, the handbooks can be made version aware much more easily than the current method on drupal.org.
     By moving all docymentation into help files, we could, if we wanted, package the Drupal.org handbooks, or a subset of them, directly into a Drupal distribution, or a Drupal add-on, so that Drupal administrators can have Drupal help without needing to visit Drupal.org. This can be valuable in locked down corporate environments and on planes. But more importantly, the handbooks can be made version aware much more easily than the current method on Drupal.org.
     The downside to this method is that these books can't easily be made dynamic. Though the use of alter hooks could allow a module to make modifications to the help as needed, doing this could make the help files less useful when you take them out of context.
     The downside to this method is that these books can't easily be made dynamic. Though the use of alter hooks could allow a module or theme to make modifications to the help as needed, doing this could make the help files less useful when you take them out of context.
     <h3><strong>Advanced help files are translated as a file</strong></h3>
     It is actually not easy to translate documents as strings, particularly when the language being used is very much unlike English. In fact, when translating a document, the organization of the sentences may change drastically. It is also a burden on the CPU to do this, as you are indexing on very long strings.
     <h2>Advanced help files are translated as a file</h2>
     It is actually not easy to translate documents as strings, particularly when the language being used is very much unlike English. In fact, when translating a document, the organization of the sentences may change drastically. It is also a burden on the CPU to do this, as you are indexing on very long strings.
     Translators have a much better time translating a document as a unit, because of the presence of the entire context.
     <h3><strong>Advanced help has its own navigation system</strong></h3>
     By making use of a navigation system specified in a .ini file (which is not PHP code and therefore safe to use on *.drupal.org sites), the help can be structured like a book, which is typical of online manuals. This is familiar to users, can be organized (and re-organized) and allows a module to include significantly richer text without burdening the PHP code with having its help loaded unnecessarily.
     <h2>Advanced help has its own navigation system</h2>
     By making use of a navigation system specified in a .ini file (which is not PHP code and therefore safe to use), the help can be structured like a book, which is typical of online manuals. This is familiar to users, can be organized (and re-organized) and allows a module or theme to include significantly richer text without burdening the PHP code with having its help loaded unnecessarily.
     This book can be navigated hierarchically as well, making it easy to keep related topics together.
     <h3><strong>Advanced help is indexed by the search engine</strong></h3>
     <h2>Advanced help is indexed by the search engine</h2>
     An important goal of this system was to add searchability to the help. By being able to enter keywords into the search box and find relevant topics, we come up with a system that resembles the kind of help that comes with many operating systems. This is very valuable when searching through manuals trying to find out how to do a particular thing.
     This search is specific to the help, meaning that the help will not be mixed in with the global node search. This can be considered both an advantage and a disadvantage. For the most part, this help system is meant to provide help to site administrators, and content searches should not find it. The disadvantage, of course, is when you want to use it for end user help, you will not be able to.
     <h3><strong>Inline help can be brought in via popups</strong></h3>
     In addition to the manual-like hierarchical navigation, advanced help can also provide context-sensitive additional help through a popup. While popups are controversial, the argument for using them is that when getting help while on a form, <i>a popup will not throw away a user's data.</i> Browsers are not very friendly to input forms if they are not submitted, and navigating away from the form can be dangerous. There are various other solutions to this problem, but each one has a drawback. The drawbacks to popups are well known, but mostly it is the irritation of having new windows. When getting help, though, a popup is usually invited. Help should not interfere with what the operation the user is trying to complete. It differs greatly from the uninvited popup, which are usually ads or popups meant to prevent users from navigating away from a site.
     <h2>Inline help can be brought in via popups</h2>
     In addition to the manual-like hierarchical navigation, <strong>Advanced help</strong> can also provide context-sensitive additional help through a popup. While popups are controversial, the argument for using them is that when getting help while on a form, <i>a popup will not throw away a user's data.</i> Browsers are not very friendly to input forms if they are not submitted, and navigating away from the form can be dangerous. There are various other solutions to this problem, but each one has a drawback. The drawbacks to popups are well known, but mostly it is the irritation of having new windows. When getting help, though, a popup is usually invited. Help should not interfere with what the operation the user is trying to complete. It differs greatly from the uninvited popup, which are usually ads or popups meant to prevent users from navigating away from a site.
     These popups can be added to a page with text links or icon links.
     Popups can be added to a page with plain text links or themed icon links.

     <p><b>PHP</b> (<i>PHP: Hypertext Preprocessor</i>) is a computer <a target="_blank" href="http://en.wikipedia.org/wiki/Scripting_language" title="Scripting language">scripting language</a>, originally designed for producing <a target="_blank" href="http://en.wikipedia.org/wiki/Dynamic_web_page" title="Dynamic web page">dynamic web pages</a>. It is mainly used in <a target="_blank" href="http://en.wikipedia.org/wiki/Server-side_scripting" title="Server-side scripting">server-side scripting</a>, but can be used from a <a target="_blank" href="http://en.wikipedia.org/wiki/Command_line_interface" title="Command line interface">command line interface</a> or in <a target="_blank" href="http://en.wikipedia.org/wiki/Standalone" title="Standalone">standalone</a> <a target="_blank" href="http://en.wikipedia.org/wiki/Graphical_user_interface" title="Graphical user interface">graphical applications</a>.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1" title="">[2]</a></sup></p>
     <p><b>PHP</b> (<i>PHP: Hypertext Preprocessor</i>) is a computer <a href="http://en.wikipedia.org/wiki/Scripting_language" title="Scripting language">scripting language</a>, originally designed for producing <a href="http://en.wikipedia.org/wiki/Dynamic_web_page" title="Dynamic web page">dynamic web pages</a>. It is mainly used in <a href="http://en.wikipedia.org/wiki/Server-side_scripting" title="Server-side scripting">server-side scripting</a>, but can be used from a <a href="http://en.wikipedia.org/wiki/Command_line_interface"title="Command line interface">command line interface</a> or in <a  href="http://en.wikipedia.org/wiki/Standalone" title="Standalone">standalone</a> <a href="http://en.wikipedia.org/wiki/Graphical_user_interface" title="Graphical user interface">graphical applications</a>.</p>
     <p>While PHP was originally created by <a target="_blank" href="http://en.wikipedia.org/wiki/Rasmus_Lerdorf" title="Rasmus Lerdorf">Rasmus Lerdorf</a> in 1994, the main implementation of PHP is now produced by The PHP Group and serves as the <a target="_blank" href="http://en.wikipedia.org/wiki/De_facto_standard" title="De facto standard"><i>de facto</i> standard</a> for PHP as there is no <a target="_blank" href="http://en.wikipedia.org/wiki/Formal_specification" title="Formal specification">formal specification</a>.<sup id="cite_ref-history_2-0" class="reference"><a href="#cite_note-history-2" title="">[3]</a></sup> Released under the <a target="_blank" href="http://en.wikipedia.org/wiki/PHP_License" title="PHP License">PHP License</a>, the <a target="_blank" href="http://en.wikipedia.org/wiki/Free_Software_Foundation" title="Free Software Foundation">Free Software Foundation</a> considers it to be <a target="_blank" href="http://en.wikipedia.org/wiki/Free_software" title="Free software">free software</a>.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3" title="">[4]</a></sup></p>
     <p>While PHP was originally created by <a
     href="http://en.wikipedia.org/wiki/Rasmus_Lerdorf" title="Rasmus
     Lerdorf">Rasmus Lerdorf</a> in 1994, the main implementation of PHP is
     now produced by The PHP Group and serves as the <a
     href="http://en.wikipedia.org/wiki/De_facto_standard" title="De facto
     standard"><i>de facto</i> standard</a> for PHP as there is
     no <a
     href="http://en.wikipedia.org/wiki/Formal_specification" title="Formal
     specification">formal specification</a>. Released under the <a
     href="http://en.wikipedia.org/wiki/PHP_License" title="PHP
     License">PHP License</a>, the <a
     href="http://en.wikipedia.org/wiki/Free_Software_Foundation"
     title="Free Software Foundation">Free Software Foundation</a>
     considers it to be <a
     href="http://en.wikipedia.org/wiki/Free_software" title="Free
     software">free software</a>.</p>
     <p>PHP is a widely-used general-purpose scripting language that is especially suited for <a target="_blank" href="http://en.wikipedia.org/wiki/Web_development" title="Web development">web development</a> and can be embedded into <a target="_blank" href="http://en.wikipedia.org/wiki/HTML" title="HTML">HTML</a>. It generally runs on a <a target="_blank" href="http://en.wikipedia.org/wiki/Web_server" title="Web server">web server</a>, taking PHP code as its input and creating <a target="_blank" href="http://en.wikipedia.org/wiki/Web_page" title="Web page">web pages</a> as output. It can be deployed on most web servers and on almost every <a target="_blank" href="http://en.wikipedia.org/wiki/Operating_system" title="Operating system">operating system</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/Platform_%28computing%29" class="mw-redirect" title="Platform (computing)">platform</a> free of charge.<sup id="cite_ref-foundations_4-0" class="reference"><a href="#cite_note-foundations-4" title="">[5]</a></sup> PHP is installed on more than 20 million websites and 1 million <a target="_blank" href="http://en.wikipedia.org/wiki/Server_%28computing%29" title="Server (computing)">servers</a>, although the number of websites with PHP <a target="_blank" href="http://en.wikipedia.org/wiki/Installation_%28computer_programs%29" title="Installation (computer programs)">installed</a> has declined since August 2005.<sup id="cite_ref-usage_5-0" class="reference"><a href="#cite_note-usage-5" title="">[6]</a></sup> It is also the most popular <a target="_blank" href="http://en.wikipedia.org/wiki/Apache_HTTP_Server" title="Apache HTTP Server">Apache</a> module among computers using Apache as a web server.<sup id="cite_ref-usage_5-1" class="reference"><a href="#cite_note-usage-5" title="">[6]</a></sup> The most recent major release of PHP was version 5.2.5 on <a target="_blank" href="http://en.wikipedia.org/wiki/November_8" title="November 8">November 8</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/2007" title="2007">2007</a>.<sup id="cite_ref-php5changelog_6-0" class="reference"><a href="#cite_note-php5changelog-6" title="">[7]</a></sup></p>
     <p>PHP is a widely-used general-purpose scripting language that is
     especially suited for <a
     href="http://en.wikipedia.org/wiki/Web_development" title="Web
     development">web development</a> and can be embedded
     into <a  href="http://en.wikipedia.org/wiki/HTML"
     title="HTML">HTML</a>. It generally runs on a <a
     href="http://en.wikipedia.org/wiki/Web_server" title="Web server">web
     server</a>, taking PHP code as its input and
     creating <a
     href="http://en.wikipedia.org/wiki/Web_page" title="Web page">web
     pages</a> as output. It can be deployed on most web servers and on
     almost every <a
     href="http://en.wikipedia.org/wiki/Operating_system" title="Operating
     system">operating system</a> and <a
     href="http://en.wikipedia.org/wiki/Platform_%28computing%29"
     class="mw-redirect" title="Platform (computing)">platform</a> free of
     charge. PHP is installed on more than 20 million
     websites and 1 million <a
     href="http://en.wikipedia.org/wiki/Server_%28computing%29"
     title="Server (computing)">servers</a>, although the number of
     websites with PHP <a
     href="http://en.wikipedia.org/wiki/Installation_%28computer_programs%29"
     title="Installation (computer programs)">installed</a> has declined
     since August 2005.
     It is also the most popular <a
     href="http://en.wikipedia.org/wiki/Apache_HTTP_Server" title="Apache
     HTTP Server">Apache</a> module among computers using Apache as a web
     server.
     The most recent major release of PHP was version 5.2.5
     on <a  href="http://en.wikipedia.org/wiki/November_8"
     title="November 8">November 8</a>, <a
     href="http://en.wikipedia.org/wiki/2007"
     title="2007">2007</a>.</p>
     <p class="attribution">This excerpt is adapted from <a href="http://en.wikipedia.org/wiki/PHP">Wikipedia: PHP</a>.  It is used here under a <a href="http://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License">Creative Commons BY-SA 3.0</a> license.</p>

     [about-php]
     title = About PHP
     file = about-php
     weight = -10
     [history]
     title = History of PHP
     file = history
     parent = about-php
     [usage]
     title = Usage of PHP
     file = usage
     weight = 1
     [security]
     title = Security of PHP
     file = security
     weight = 2
     [syntax]
     title = PHP syntax
     file = syntax
     parent = usage

     <div class="help-box help-left">
     <div class="thumbinner" style="width:182px;"><a href="http://en.wikipedia.org/wiki/Image:Lerdorf.jpg" class="image" title="Rasmus Lerdorf, who wrote the original Common Gateway Interface binaries"><img alt="Rasmus Lerdorf, who wrote the original Common Gateway Interface binaries" src="path:180px-Lerdorf.jpg" width="180" height="270" border="0" class="thumbimage" /></a>
     <div class="thumbcaption">
     <div class="magnify"><a href="/wiki/Image:Lerdorf.jpg" class="internal" title="Enlarge"><img src="/skins-1.5/common/images/magnify-clip.png" width="15" height="11" alt="" /></a></div>
     <a href="/wiki/Rasmus_Lerdorf" title="Rasmus Lerdorf">Rasmus Lerdorf</a>, who wrote the original <a href="/wiki/Common_Gateway_Interface" title="Common Gateway Interface">Common Gateway Interface</a> binaries</div>
     <a href="http://en.wikipedia.org/wiki/Rasmus_Lerdorf" title="Rasmus Lerdorf">Rasmus Lerdorf</a>, who wrote the original <a href="http://en.wikipedia.org/wiki/Common_Gateway_Interface" title="Common Gateway Interface">Common Gateway Interface</a> binaries</div>
     </div>
     </div>
     <p>PHP, standing for Personal Home Page, began as a set of <a target="_blank" href="http://en.wikipedia.org/wiki/Common_Gateway_Interface" title="Common Gateway Interface">Common Gateway Interface</a> <a target="_blank" href="http://en.wikipedia.org/wiki/Binary_file" title="Binary file">binaries</a> written in the <a target="_blank" href="http://en.wikipedia.org/wiki/C_programming_language" class="mw-redirect" title="C programming language">C programming language</a> in 1994 by the <a target="_blank" href="http://en.wikipedia.org/wiki/Danish_people" title="Danish people">Danish</a>/<a target="_blank" href="http://en.wikipedia.org/wiki/Greenland" title="Greenland">Greenlandic</a> programmer <a target="_blank" href="http://en.wikipedia.org/wiki/Rasmus_Lerdorf" title="Rasmus Lerdorf">Rasmus Lerdorf</a>. Lerdorf initially created these Personal Home Page Tools to replace a small set of <a target="_blank" href="http://en.wikipedia.org/wiki/Perl" title="Perl">Perl</a> scripts he had been using to maintain his <a target="_blank" href="http://en.wikipedia.org/wiki/Personal_homepage" class="mw-redirect" title="Personal homepage">personal homepage</a>. The tools were originally created to perform tasks such as displaying his <a target="_blank" href="http://en.wikipedia.org/wiki/R%C3%A9sum%C3%A9" title="Résumé">résumé</a> and recording how much <a target="_blank" href="http://en.wikipedia.org/wiki/Web_traffic" title="Web traffic">traffic</a> his page was receiving.<sup id="cite_ref-history_2-1" class="reference"><a href="#cite_note-history-2" title="">[3]</a></sup> He combined these binaries with his Form Interpreter to create PHP/FI, which had more functionality. It included a larger <a target="_blank" href="http://en.wikipedia.org/wiki/C_%28programming_language%29" title="C (programming language)">C implementation</a> which could communicate with <a target="_blank" href="http://en.wikipedia.org/wiki/Database" title="Database">databases</a> and helped build simple, dynamic <a target="_blank" href="http://en.wikipedia.org/wiki/Web_application" title="Web application">web applications</a>. He released PHP publicly on <a target="_blank" href="http://en.wikipedia.org/wiki/June_8" title="June 8">June 8</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/1995" title="1995">1995</a> to speed up the finding of <a target="_blank" href="http://en.wikipedia.org/wiki/Software_bug" title="Software bug">bugs</a> and improving the code.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7" title="">[8]</a></sup> This release was named PHP version 2, and already had basic functionality that PHP has today. This includes Perl-like variables, form handling, and the ability to embed HTML. The syntax was similar to Perl but was more limited, simpler, and less consistent.<sup id="cite_ref-history_2-2" class="reference"><a href="#cite_note-history-2" title="">[3]</a></sup></p>
     <p>PHP, standing for Personal Home Page, began as a set of <a href="http://en.wikipedia.org/wiki/Common_Gateway_Interface" title="Common Gateway Interface">Common Gateway Interface</a> <a href="http://en.wikipedia.org/wiki/Binary_file" title="Binary file">binaries</a> written in the <a href="http://en.wikipedia.org/wiki/C_programming_language" class="mw-redirect" title="C programming language">C programming language</a> in 1994 by the <a href="http://en.wikipedia.org/wiki/Danish_people" title="Danish people">Danish</a>/<a href="http://en.wikipedia.org/wiki/Greenland" title="Greenland">Greenlandic</a> programmer <a href="http://en.wikipedia.org/wiki/Rasmus_Lerdorf" title="Rasmus Lerdorf">Rasmus Lerdorf</a>. Lerdorf initially created these Personal Home Page Tools to replace a small set of <a href="http://en.wikipedia.org/wiki/Perl" title="Perl">Perl</a> scripts he had been using to maintain his <a href="http://en.wikipedia.org/wiki/Personal_homepage" class="mw-redirect" title="Personal homepage">personal homepage</a>. The tools were originally created to perform tasks such as displaying his <a href="http://en.wikipedia.org/wiki/R%C3%A9sum%C3%A9" title="Résumé">résumé</a> and recording how much <a href="http://en.wikipedia.org/wiki/Web_traffic" title="Web traffic">traffic</a> his page was receiving. He combined these binaries with his Form Interpreter to create PHP/FI, which had more functionality. It included a larger <a href="http://en.wikipedia.org/wiki/C_%28programming_language%29" title="C (programming language)">C implementation</a> which could communicate with <a href="http://en.wikipedia.org/wiki/Database" title="Database">databases</a> and helped build simple, dynamic <a href="http://en.wikipedia.org/wiki/Web_application" title="Web application">web applications</a>. He released PHP publicly on <a href="http://en.wikipedia.org/wiki/June_8" title="June 8">June 8</a>, <a href="http://en.wikipedia.org/wiki/1995" title="1995">1995</a> to speed up the finding of <a href="http://en.wikipedia.org/wiki/Software_bug" title="Software bug">bugs</a> and improving the code. This release was named PHP version 2, and already had basic functionality that PHP has today. This includes Perl-like variables, form handling, and the ability to embed HTML. The syntax was similar to Perl but was more limited, simpler, and less consistent.</p>
     <div class="help-box help-right">
     <div class="thumbinner" style="width:182px;"><a target="_blank" href="http://en.wikipedia.org/wiki/Image:Andi_Gutmans_1.jpg" class="image" title="Andi Gutmans, who, along with Zeev Suraski, rewrote the parser that formed PHP 3"><img alt="Andi Gutmans, who, along with Zeev Suraski, rewrote the parser that formed PHP 3" src="path:180px-Andi_Gutmans_1.jpg" width="180" height="244" border="0" class="thumbimage" /></a>
     <div class="thumbinner" style="width:182px;"><a href="http://en.wikipedia.org/wiki/Image:Andi_Gutmans_1.jpg" class="image" title="Andi Gutmans, who, along with Zeev Suraski, rewrote the parser that formed PHP 3"><img alt="Andi Gutmans, who, along with Zeev Suraski, rewrote the parser that formed PHP 3" src="path:180px-Andi_Gutmans_1.jpg" width="180" height="244" border="0" class="thumbimage" /></a>
     <div class="thumbcaption">
     <div class="magnify"><a target="_blank" href="http://en.wikipedia.org/wiki/Image:Andi_Gutmans_1.jpg" class="internal" title="Enlarge"><img src="/skins-1.5/common/images/magnify-clip.png" width="15" height="11" alt="" /></a></div>
     <a target="_blank" href="http://en.wikipedia.org/wiki/Andi_Gutmans" title="Andi Gutmans">Andi Gutmans</a>, who, along with <a target="_blank" href="http://en.wikipedia.org/wiki/Zeev_Suraski" title="Zeev Suraski">Zeev Suraski</a>, rewrote the <a target="_blank" href="http://en.wikipedia.org/wiki/Parser" class="mw-redirect" title="Parser">parser</a> that formed PHP 3</div>
     <a href="http://en.wikipedia.org/wiki/Andi_Gutmans" title="Andi Gutmans">Andi Gutmans</a>, who, along with <a href="http://en.wikipedia.org/wiki/Zeev_Suraski" title="Zeev Suraski">Zeev Suraski</a>, rewrote the <a href="http://en.wikipedia.org/wiki/Parsing#Parser" title="Parser">parser</a> that formed PHP&nbsp;3</div>
     </div>
     </div>
     <p><a target="_blank" href="http://en.wikipedia.org/wiki/Zeev_Suraski" title="Zeev Suraski">Zeev Suraski</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/Andi_Gutmans" title="Andi Gutmans">Andi Gutmans</a>, two <a target="_blank" href="http://en.wikipedia.org/wiki/Israelis" title="Israelis">Israeli</a> developers at the <a target="_blank" href="http://en.wikipedia.org/wiki/Technion_IIT" class="mw-redirect" title="Technion IIT">Technion IIT</a>, rewrote the <a target="_blank" href="http://en.wikipedia.org/wiki/Parser" class="mw-redirect" title="Parser">parser</a> in 1997 and formed the base of PHP 3, changing the language's name to the <a target="_blank" href="http://en.wikipedia.org/wiki/Recursive_initialism" class="mw-redirect" title="Recursive initialism">recursive initialism</a> <i>PHP: Hypertext Preprocessor</i>.<sup id="cite_ref-history_2-3" class="reference"><a href="#cite_note-history-2" title="">[3]</a></sup> The development team officially released PHP/FI 2 in November 1997 after months of <a target="_blank" href="http://en.wikipedia.org/wiki/Development_stage#beta" class="mw-redirect" title="Development stage">beta</a> testing. Afterwards, public testing of PHP 3 began, and the official launch came in June 1998. Suraski and Gutmans then started a new <a target="_blank" href="http://en.wikipedia.org/wiki/Rewrite_%28programming%29" title="Rewrite (programming)">rewrite</a> of PHP's core, producing the <a target="_blank" href="http://en.wikipedia.org/wiki/Zend_Engine" title="Zend Engine">Zend Engine</a> in 1999.<sup id="cite_ref-8" class="reference"><a href="#cite_note-8" title="">[9]</a></sup> They also founded <a target="_blank" href="http://en.wikipedia.org/wiki/Zend_Technologies" title="Zend Technologies">Zend Technologies</a> in <a target="_blank" href="http://en.wikipedia.org/wiki/Ramat_Gan" title="Ramat Gan">Ramat Gan</a>, Israel, which manages the development of PHP.<sup id="cite_ref-history_2-4" class="reference"><a href="#cite_note-history-2" title="">[3]</a></sup></p>
     <p><a href="http://en.wikipedia.org/wiki/Zeev_Suraski" title="Zeev Suraski">Zeev Suraski</a> and <a href="http://en.wikipedia.org/wiki/Andi_Gutmans" title="Andi Gutmans">Andi Gutmans</a>, two <a href="http://en.wikipedia.org/wiki/Israelis" title="Israelis">Israeli</a> developers at the <a href="http://en.wikipedia.org/wiki/Technion_IIT" class="mw-redirect" title="Technion IIT">Technion IIT</a>, rewrote the <a href="http://en.wikipedia.org/wiki/Parsing#Parser title="Parser">parser</a> in 1997 and formed the base of PHP 3, changing the language's name to the <a href="http://en.wikipedia.org/wiki/Recursive_initialism" class="mw-redirect" title="Recursive initialism">recursive initialism</a> <i>PHP: Hypertext Preprocessor</i>. The development team officially released PHP/FI 2 in November 1997 after months of <a href="http://en.wikipedia.org/wiki/Development_stage#beta" class="mw-redirect" title="Development stage">beta</a> testing. Afterwards, public testing of PHP 3 began, and the official launch came in June 1998. Suraski and Gutmans then started a new <a href="http://en.wikipedia.org/wiki/Rewrite_%28programming%29" title="Rewrite (programming)">rewrite</a> of PHP's core, producing the <a href="http://en.wikipedia.org/wiki/Zend_Engine" title="Zend Engine">Zend Engine</a> in 1999. They also founded <a href="http://en.wikipedia.org/wiki/Zend_Technologies" title="Zend Technologies">Zend Technologies</a> in <a href="http://en.wikipedia.org/wiki/Ramat_Gan" title="Ramat Gan">Ramat Gan</a>, Israel, which manages the development of PHP.</p>
     <p>On <a href="http://en.wikipedia.org/wiki/May_22" title="May 22">May 22</a>, <a href="http://en.wikipedia.org/wiki/2000" title="2000">2000</a>, PHP 4, powered by the Zend Engine 1.0, was released. On <a href="http://en.wikipedia.org/wiki/July_13" title="July 13">July 13</a>, <a href="http://en.wikipedia.org/wiki/2004" title="2004">2004</a>, PHP 5 was released and is powered by the new Zend Engine II. PHP 5 included new features such as improved support for <a href="http://en.wikipedia.org/wiki/Object-oriented_programming" title="Object-oriented programming">object-oriented programming</a>, the PHP Data Objects extension (which defines a lightweight and consistent interface for accessing databases), and numerous performance enhancements. The most recent update released by The PHP Group is for the older PHP version 4 code branch. As of January 2008, this branch is up to version 4.4.8. PHP 4 will be supported by security updates until <a href="http://en.wikipedia.org/wiki/August_8" title="August 8">August 8</a>, <a href="http://en.wikipedia.org/wiki/2008" title="2008">2008</a>.</p>
     <p>PHP 5 is the only stable version still being developed. <a href="http://en.wikipedia.org/wiki/Late_static_binding" class="mw-redirect" title="Late static binding">Late static binding</a> has been missing from PHP and will be added in version 5.3. Development on PHP 4 ceased at the end of 2007, except for the critical security updates for PHP 4 already mentioned. PHP 6 is now under development and major changes include the removal of <code>register_globals</code>, <a href="http://en.wikipedia.org/wiki/Magic_quotes" title="Magic quotes">magic quotes</a>, and <a href="http://en.wikipedia.org/wiki/Safe_mode#Application_software_safe_mode" title="Safe mode">safe mode</a>. PHP does not have complete native support for <a href="http://en.wikipedia.org/Unicode" title="Unicode">Unicode</a> or multibyte strings; unicode support will be added in PHP 6. Many high profile open source projects ceased to support PHP 4 in new code as of <a href="http://en.wikipedia.org/wiki/February_5" title="February 5">February 5</a>, <a href="http://en.wikipedia.org/wiki/2008" title="2008">2008</a>, due to the GoPHP5 initiative, provided by a consortium of PHP developers promoting the transition from PHP 4 to PHP 5.</p>
     <p>On <a target="_blank" href="http://en.wikipedia.org/wiki/May_22" title="May 22">May 22</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/2000" title="2000">2000</a>, PHP 4, powered by the Zend Engine 1.0, was released.<sup id="cite_ref-history_2-5" class="reference"><a href="#cite_note-history-2" title="">[3]</a></sup> On <a target="_blank" href="http://en.wikipedia.org/wiki/July_13" title="July 13">July 13</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/2004" title="2004">2004</a>, PHP 5 was released and is powered by the new Zend Engine II.<sup id="cite_ref-history_2-6" class="reference"><a href="#cite_note-history-2" title="">[3]</a></sup> PHP 5 included new features such as improved support for <a target="_blank" href="http://en.wikipedia.org/wiki/Object-oriented_programming" title="Object-oriented programming">object-oriented programming</a>, the PHP Data Objects extension (which defines a lightweight and consistent interface for accessing databases), and numerous performance enhancements.<sup id="cite_ref-9" class="reference"><a href="#cite_note-9" title="">[10]</a></sup> The most recent update released by The PHP Group is for the older PHP version 4 code branch. As of January 2008, this branch is up to version 4.4.8. PHP 4 will be supported by security updates until <a target="_blank" href="http://en.wikipedia.org/wiki/August_8" title="August 8">August 8</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/2008" title="2008">2008</a>.<sup id="cite_ref-2007_news_10-0" class="reference"><a href="#cite_note-2007_news-10" title="">[11]</a></sup></p>
     <p class="attribution">This excerpt is adapted from <a href="http://en.wikipedia.org/wiki/PHP#History">Wikipedia: PHP - history</a>. It is used here under a <a href="http://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License">Creative Commons BY-SA 3.0</a> license.</p>
     <p>PHP 5 is the only stable version still being developed. <a target="_blank" href="http://en.wikipedia.org/wiki/Late_static_binding" class="mw-redirect" title="Late static binding">Late static binding</a> has been missing from PHP and will be added in version 5.3.<sup id="cite_ref-11" class="reference"><a href="#cite_note-11" title="">[12]</a></sup> <sup id="cite_ref-12" class="reference"><a href="#cite_note-12" title="">[13]</a></sup> Development on PHP 4 ceased at the end of 2007, except for the critical security updates for PHP 4 already mentioned.<sup id="cite_ref-13" class="reference"><a href="#cite_note-13" title="">[14]</a></sup><sup id="cite_ref-2007_news_10-1" class="reference"><a href="#cite_note-2007_news-10" title="">[11]</a></sup> PHP 6 is now under development and major changes include the removal of <code>register_globals</code><sup id="cite_ref-14" class="reference"><a href="#cite_note-14" title="">[15]</a></sup>, <a target="_blank" href="http://en.wikipedia.org/wiki/Magic_quotes" title="Magic quotes">magic quotes</a>, and <a target="_blank" href="http://en.wikipedia.org/wiki/Safe_mode#Application_software_safe_mode" title="Safe mode">safe mode</a>.<sup id="cite_ref-2007_news_10-2" class="reference"><a href="#cite_note-2007_news-10" title="">[11]</a></sup><sup id="cite_ref-15" class="reference"><a href="#cite_note-15" title="">[16]</a></sup> PHP does not have complete native support for <a target="_blank" href="http://en.wikipedia.org/Unicode" title="Unicode">Unicode</a> or multibyte strings;<sup id="cite_ref-16" class="reference"><a href="#cite_note-16" title="">[17]</a></sup> unicode support will be added in PHP 6.<sup id="cite_ref-17" class="reference"><a href="#cite_note-17" title="">[18]</a></sup> Many high profile open source projects ceased to support PHP 4 in new code as of <a target="_blank" href="http://en.wikipedia.org/wiki/February_5" title="February 5">February 5</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/2008" title="2008">2008</a>, due to the GoPHP5 initiative, provided by a consortium of PHP developers promoting the transition from PHP 4 to PHP 5.<sup id="cite_ref-gophp5_18-0" class="reference"><a href="#cite_note-gophp5-18" title="">[19]</a></sup><sup id="cite_ref-19" class="reference"><a href="#cite_note-19" title="">[20]</a></sup></p>

drupal7/sites/all/modules/advanced_help/help_example/help/security.html
1		<p>PHP is a popular target of <a target="_blank" href="http://en.wikipedia.org/wiki/Hacker" title="Hacker">hackers</a> who exploit vulnerable applications written in PHP. Software vulnerabilities related to PHP are identified among the <a target="_blank" href="http://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures" title="Common Vulnerabilities and Exposures">CVE (Common Vulnerabilities and Exposures)</a> records, available from the <a target="_blank" href="http://en.wikipedia.org/wiki/National_Vulnerability_Database" title="National Vulnerability Database">National Vulnerability Database</a>. The proportion of vulnerabilities related to PHP, out of the total of all common vulnerabilities, amounted to: 12% in 2003, 20% in 2004, 28% in 2005, 43% in 2006, 36% in 2007, and 33.8% for the first quarter of 2008. More than a quarter of all software vulnerabilities listed in this database are related to PHP, and more than a third of vulnerabilities listed recently. Most of these vulnerabilities can be exploited remotely, that is without being logged on the computer hosting the vulnerable application.<sup id="cite_ref-27" class="reference"><a href="#cite_note-27" title="">[28]</a></sup> Such exploitation is made possible due to poor programming habits, such as failing to check data before entering it into a database, and features of the language such as <code>register_globals</code>, which is now deprecated.<sup id="cite_ref-register_globals_21-1" class="reference"><a href="#cite_note-register_globals-21" title="">[22]</a></sup> These result in <a target="_blank" href="http://en.wikipedia.org/wiki/Code_injection" title="Code injection">code injection</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/Cross-site_scripting" title="Cross-site scripting">cross-site scripting</a> and other <a target="_blank" href="http://en.wikipedia.org/wiki/Application_security" title="Application security">application security</a> issues. It's important to note that none of these attacks are exclusive to PHP and all are avoidable by following proper coding techniques and principles.</p>
	1	<p>PHP is a popular target of <a href="http://en.wikipedia.org/wiki/Hacker" title="Hacker">hackers</a> who exploit vulnerable applications written in PHP. Software vulnerabilities related to PHP are identified among the <a href="http://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures" title="Common Vulnerabilities and Exposures">CVE (Common Vulnerabilities and Exposures)</a> records, available from the <a href="http://en.wikipedia.org/wiki/National_Vulnerability_Database" title="National Vulnerability Database">National Vulnerability Database</a>. The proportion of vulnerabilities related to PHP, out of the total of all common vulnerabilities, amounted to: 12% in 2003, 20% in 2004, 28% in 2005, 43% in 2006, 36% in 2007, and 33.8% for the first quarter of 2008. More than a quarter of all software vulnerabilities listed in this database are related to PHP, and more than a third of vulnerabilities listed recently. Most of these vulnerabilities can be exploited remotely, that is without being logged on the computer hosting the vulnerable application. Such exploitation is made possible due to poor programming habits, such as failing to check data before entering it into a database, and features of the language such as <code>register_globals</code>, which is now deprecated. These result in <a href="http://en.wikipedia.org/wiki/Code_injection" title="Code injection">code injection</a>, <a href="http://en.wikipedia.org/wiki/Cross-site_scripting" title="Cross-site scripting">cross-site scripting</a> and other <a href="http://en.wikipedia.org/wiki/Application_security" title="Application security">application security</a> issues. It's important to note that none of these attacks are exclusive to PHP and all are avoidable by following proper coding techniques and principles.</p>
	2
	3	<p class="attribution">This excerpt is adapted from <a href="http://en.wikipedia.org/wiki/PHP#Security">Wikipedia: PHP - security</a>. It is used here under a <a href="http://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License">Creative Commons BY-SA 3.0</a> license.</p>
	4

     <h2> <span class="mw-headline">Syntax</span></h2>
     <div class="help-right">
     <div class="thumbinner" style="width:182px;"><a target="_blank" href="http://en.wikipedia.org/wiki/Image:PHP_Hello_World_screenshot.png" class="image" title="Syntax-highlighted PHP code"><img alt="Syntax-highlighted PHP code" src="path:180px-PHP_Hello_World_screenshot.png" width="180" height="87" border="0" class="thumbimage" /></a>
     <div class="thumbcaption">
     <h2>Syntax</h2>
     <p>PHP only parses code within its <a  href="http://en.wikipedia.org/wiki/Delimiter" title="Delimiter">delimiters</a>. Anything outside its delimiters is sent directly to the output and is not parsed by PHP. The most common delimiters are <span s>&lt;?php</span> and <span>?&gt;</span>, which are open and close delimiters respectively. <span>&lt;script language="php"&gt;</span> and <span>&lt;/script&gt;</span> delimiters are also available. Short tags (<span>&lt;?</span> or <span>&lt;?=</span> and <span>?&gt;</span>) are also commonly used, but like ASP-style tags (<span>&lt;%</span> or <span>&lt;%=</span> and <span>%&gt;</span>), they are less portable as they can be disabled in the PHP configuration. For this reason, the use of short tags and ASP-style tags is discouraged. The purpose of these delimiters is to separate PHP code from non-PHP code, including HTML. Everything outside the delimiters is ignored by the parser and is passed through as output.</p>
     <div class="magnify"><a target="_blank" href="http://en.wikipedia.org/wiki/Image:PHP_Hello_World_screenshot.png" class="internal" title="Enlarge"><img src="/skins-1.5/common/images/magnify-clip.png" width="15" height="11" alt="" /></a></div>
     <a target="_blank" href="http://en.wikipedia.org/wiki/Syntax-highlighted" class="mw-redirect" title="Syntax-highlighted">Syntax-highlighted</a> PHP code</div>
     </div>
     </div>
     <p>PHP only parses code within its <a target="_blank" href="http://en.wikipedia.org/wiki/Delimiter" title="Delimiter">delimiters</a>. Anything outside its delimiters is sent directly to the output and is not parsed by PHP. The most common delimiters are <span s>&lt;?php</span> and <span>?&gt;</span>, which are open and close delimiters respectively. <span>&lt;script language="php"&gt;</span> and <span>&lt;/script&gt;</span> delimiters are also available. Short tags (<span>&lt;?</span> or <span>&lt;?=</span> and <span>?&gt;</span>) are also commonly used, but like ASP-style tags (<span>&lt;%</span> or <span>&lt;%=</span> and <span>%&gt;</span>), they are less portable as they can be disabled in the PHP configuration. For this reason, the use of short tags and ASP-style tags is discouraged.<sup id="cite_ref-basic_syntax_28-0" class="reference"><a href="#cite_note-basic_syntax-28" title="">[29]</a></sup> The purpose of these delimiters is to separate PHP code from non-PHP code, including HTML. Everything outside the delimiters is ignored by the parser and is passed through as output.<sup id="cite_ref-29" class="reference"><a href="#cite_note-29" title="">[30]</a></sup></p>
     <p>Variables are prefixed with a <a target="_blank" href="http://en.wikipedia.org/wiki/Dollar_sign" title="Dollar sign">dollar symbol</a> and a <a target="_blank" href="http://en.wikipedia.org/wiki/Primitive_type" title="Primitive type">type</a> does not need to be specified in advance. Unlike function and class names, variable names are case sensitive. Both double-quoted (<span>""</span>) and <a target="_blank" href="http://en.wikipedia.org/wiki/Heredoc" class="mw-redirect" title="Heredoc">heredoc</a> strings allow the ability to embed the variable's value into the string.<sup id="cite_ref-30" class="reference"><a href="#cite_note-30" title="">[31]</a></sup> PHP treats <a target="_blank" href="http://en.wikipedia.org/wiki/Newline" title="Newline">newlines</a> as <a target="_blank" href="http://en.wikipedia.org/wiki/Whitespace_%28computer_science%29" title="Whitespace (computer science)">whitespace</a> in the manner of a <a target="_blank" href="http://en.wikipedia.org/wiki/Free-form_language" title="Free-form language">free-form language</a> (except when inside string quotes), and statements are terminated by a semicolon.<sup id="cite_ref-31" class="reference"><a href="#cite_note-31" title="">[32]</a></sup> PHP has three types of <a target="_blank" href="http://en.wikipedia.org/wiki/Comparison_of_programming_languages_%28syntax%29#Comments" title="Comparison of programming languages (syntax)">comment syntax</a>: <span>/* */</span> serves as block comments, and <span>//</span> as well as <span>#</span> are used for inline comments.<sup id="cite_ref-32" class="reference"><a href="#cite_note-32" title="">[33]</a></sup> To output text to the browser, either the <tt>print</tt> function or the <tt>echo</tt> function is used. Both functions are nearly identical; the major difference is that <tt>print</tt> is slower than <tt>echo</tt> because the former will return a status indicating if it was successful or not, whereas the latter does not return a status and only returns the text for output.<sup id="cite_ref-33" class="reference"><a href="#cite_note-33" title="">[34]</a></sup></p>
     <p>Variables are prefixed with a <a  href="http://en.wikipedia.org/wiki/Dollar_sign" title="Dollar sign">dollar symbol</a> and a <a  href="http://en.wikipedia.org/wiki/Primitive_type" title="Primitive type">type</a> does not need to be specified in advance. Unlike function and class names, variable names are case sensitive. Both double-quoted (<span>""</span>) and <a  href="http://en.wikipedia.org/wiki/Heredoc" class="mw-redirect" title="Heredoc">heredoc</a> strings allow the ability to embed the variable's value into the string. PHP treats <a  href="http://en.wikipedia.org/wiki/Newline" title="Newline">newlines</a> as <a  href="http://en.wikipedia.org/wiki/Whitespace_%28computer_science%29" title="Whitespace (computer science)">whitespace</a> in the manner of a <a  href="http://en.wikipedia.org/wiki/Free-form_language" title="Free-form language">free-form language</a> (except when inside string quotes), and statements are terminated by a semicolon. PHP has three types of <a  href="http://en.wikipedia.org/wiki/Comparison_of_programming_languages_%28syntax%29#Comments" title="Comparison of programming languages (syntax)">comment syntax</a>: <span>/* */</span> serves as block comments, and <span>//</span> as well as <span>#</span> are used for inline comments. To output text to the browser, either the <tt>print</tt> function or the <tt>echo</tt> function is used. Both functions are nearly identical; the major difference is that <tt>print</tt> is slower than <tt>echo</tt> because the former will return a status indicating if it was successful or not, whereas the latter does not return a status and only returns the text for output.</p>
     <p><a name="Data_types" id="Data_types"></a></p>
     <h3><span class="mw-headline">Data types</span></h3>
     <p>PHP stores whole numbers in a platform-dependent range. This range is typically that of 32-bit <a target="_blank" href="http://en.wikipedia.org/wiki/Signed_number_representations" title="Signed number representations">signed</a> <a target="_blank" href="http://en.wikipedia.org/wiki/Integer_%28computer_science%29" title="Integer (computer science)">integers</a>. Unsigned integers are converted to signed values in certain situations; this behavior is different from other programming languages.<sup id="cite_ref-34" class="reference"><a href="#cite_note-34" title="">[35]</a></sup> Integer variables can be assigned using decimal (positive and negative), <a target="_blank" href="http://en.wikipedia.org/wiki/Octal" title="Octal">octal</a>, and <a target="_blank" href="http://en.wikipedia.org/wiki/Hexadecimal" title="Hexadecimal">hexadecimal</a> notations. <a target="_blank" href="http://en.wikipedia.org/wiki/Real_numbers" class="mw-redirect" title="Real numbers">Real numbers</a> are also stored in a platform-specific range. They can be specified using <a target="_blank" href="http://en.wikipedia.org/wiki/Floating_point" title="Floating point">floating point</a> notation, or two forms of <a target="_blank" href="http://en.wikipedia.org/wiki/Scientific_notation" title="Scientific notation">scientific notation</a>.<sup id="cite_ref-types_35-0" class="reference"><a href="#cite_note-types-35" title="">[36]</a></sup> PHP has a native <a target="_blank" href="http://en.wikipedia.org/wiki/Boolean_datatype" title="Boolean datatype">Boolean</a> type that is similar to the native Boolean types in <a target="_blank" href="http://en.wikipedia.org/wiki/Java_%28programming_language%29" title="Java (programming language)">Java</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/C%2B%2B" title="C++">C++</a>. Using the Boolean type conversion rules, non-zero values are interpreted as true and zero as false, as in Perl and C++.<sup id="cite_ref-types_35-1" class="reference"><a href="#cite_note-types-35" title="">[36]</a></sup> The null data type represents a variable that has no value. The only value in the null data type is <i>NULL</i>.<sup id="cite_ref-types_35-2" class="reference"><a href="#cite_note-types-35" title="">[36]</a></sup> Variables of the "resource" type represent references to resources from external sources. These are typically created by functions from a particular extension, and can only be processed by functions from the same extension; examples include file, image, and database resources.<sup id="cite_ref-types_35-3" class="reference"><a href="#cite_note-types-35" title="">[36]</a></sup> Arrays can contain elements of any type that PHP can handle, including resources, objects, and even other arrays. Order is preserved in lists of values and in <a target="_blank" href="http://en.wikipedia.org/wiki/Hash_table" title="Hash table">hashes</a> with both keys and values, and the two can be intermingled.<sup id="cite_ref-types_35-4" class="reference"><a href="#cite_note-types-35" title="">[36]</a></sup> PHP also supports <a target="_blank" href="http://en.wikipedia.org/wiki/String_%28computing%29" class="mw-redirect" title="String (computing)">strings</a>, which can be used with single quotes, double quotes, or <a target="_blank" href="http://en.wikipedia.org/wiki/Heredoc" class="mw-redirect" title="Heredoc">heredoc syntax</a>.<sup id="cite_ref-36" class="reference"><a href="#cite_note-36" title="">[37]</a></sup></p>
     <p>PHP stores whole numbers in a platform-dependent range. This range is typically that of 32-bit <a  href="http://en.wikipedia.org/wiki/Signed_number_representations" title="Signed number representations">signed</a> <a  href="http://en.wikipedia.org/wiki/Integer_%28computer_science%29" title="Integer (computer science)">integers</a>. Unsigned integers are converted to signed values in certain situations; this behavior is different from other programming languages. Integer variables can be assigned using decimal (positive and negative), <a  href="http://en.wikipedia.org/wiki/Octal" title="Octal">octal</a>, and <a  href="http://en.wikipedia.org/wiki/Hexadecimal" title="Hexadecimal">hexadecimal</a> notations. <a  href="http://en.wikipedia.org/wiki/Real_numbers" class="mw-redirect" title="Real numbers">Real numbers</a> are also stored in a platform-specific range. They can be specified using <a  href="http://en.wikipedia.org/wiki/Floating_point" title="Floating point">floating point</a> notation, or two forms of <a  href="http://en.wikipedia.org/wiki/Scientific_notation" title="Scientific notation">scientific notation</a>. PHP has a native <a  href="http://en.wikipedia.org/wiki/Boolean_datatype" title="Boolean datatype">Boolean</a> type that is similar to the native Boolean types in <a  href="http://en.wikipedia.org/wiki/Java_%28programming_language%29" title="Java (programming language)">Java</a> and <a  href="http://en.wikipedia.org/wiki/C%2B%2B" title="C++">C++</a>. Using the Boolean type conversion rules, non-zero values are interpreted as true and zero as false, as in Perl and C++. The null data type represents a variable that has no value. The only value in the null data type is <i>NULL</i>. Variables of the "resource" type represent references to resources from external sources. These are typically created by functions from a particular extension, and can only be processed by functions from the same extension; examples include file, image, and database resources. Arrays can contain elements of any type that PHP can handle, including resources, objects, and even other arrays. Order is preserved in lists of values and in <a  href="http://en.wikipedia.org/wiki/Hash_table" title="Hash table">hashes</a> with both keys and values, and the two can be intermingled. PHP also supports <a  href="http://en.wikipedia.org/wiki/String_%28computing%29" class="mw-redirect" title="String (computing)">strings</a>, which can be used with single quotes, double quotes, or <a  href="http://en.wikipedia.org/wiki/Heredoc" class="mw-redirect" title="Heredoc">heredoc syntax</a>.</p>
     <p><a name="Functions" id="Functions"></a></p>
     <h3><span class="mw-headline">Functions</span></h3>
     <p>PHP has hundreds of base functions and thousands more from extensions. Functions are not <a target="_blank" href="http://en.wikipedia.org/wiki/First-class_function" title="First-class function">first-class functions</a> and can only be referenced by their name. <sup id="cite_ref-functions_37-0" class="reference"><a href="#cite_note-functions-37" title="">[38]</a></sup> User-defined functions can be created at any time without being prototyped.<sup id="cite_ref-functions_37-1" class="reference"><a href="#cite_note-functions-37" title="">[38]</a></sup> Functions can be defined inside code blocks, permitting a <a target="_blank" href="http://en.wikipedia.org/wiki/Dynamic_dispatch" title="Dynamic dispatch">run-time decision</a> as to whether or not a function should be defined. Function calls must use parentheses, with the exception of zero argument class <a target="_blank" href="http://en.wikipedia.org/wiki/Constructor_%28computer_science%29" title="Constructor (computer science)">constructor</a> functions called with the PHP <span>new</span> operator, where parentheses are optional. PHP supports quasi-<a target="_blank" href="http://en.wikipedia.org/wiki/Anonymous_function" title="Anonymous function">anonymous functions</a> through the <span>create_function()</span> function, although they are not true anonymous functions because anonymous functions are nameless, but functions can only be referenced by name, or indirectly through a variable <span>$function_name();</span>, in PHP.<sup id="cite_ref-functions_37-2" class="reference"><a href="#cite_note-functions-37" title="">[38]</a></sup></p>
     <p>PHP has hundreds of base functions and thousands more from extensions. Functions are not <a  href="http://en.wikipedia.org/wiki/First-class_function" title="First-class function">first-class functions</a> and can only be referenced by their name.  User-defined functions can be created at any time without being prototyped. Functions can be defined inside code blocks, permitting a <a  href="http://en.wikipedia.org/wiki/Dynamic_dispatch" title="Dynamic dispatch">run-time decision</a> as to whether or not a function should be defined. Function calls must use parentheses, with the exception of zero argument class <a  href="http://en.wikipedia.org/wiki/Constructor_%28computer_science%29" title="Constructor (computer science)">constructor</a> functions called with the PHP <span>new</span> operator, where parentheses are optional. PHP supports quasi-<a  href="http://en.wikipedia.org/wiki/Anonymous_function" title="Anonymous function">anonymous functions</a> through the <span>create_function()</span> function, although they are not true anonymous functions because anonymous functions are nameless, but functions can only be referenced by name, or indirectly through a variable <span>$function_name();</span>, in PHP.</p>
     <p><a name="Objects" id="Objects"></a></p>
     <h3><span class="mw-headline">Objects</span></h3>
     <p>Basic <a target="_blank" href="http://en.wikipedia.org/wiki/Object-oriented_programming" title="Object-oriented programming">object-oriented programming</a> functionality was added in PHP 3.<sup id="cite_ref-history_2-10" class="reference"><a href="#cite_note-history-2" title="">[3]</a></sup> Object handling was completely rewritten for PHP 5, expanding the feature set and enhancing performance.<sup id="cite_ref-php_5_objects_38-0" class="reference"><a href="#cite_note-php_5_objects-38" title="">[39]</a></sup> In previous versions of PHP, objects were handled like <a target="_blank" href="http://en.wikipedia.org/wiki/Primitive_type" title="Primitive type">primitive types</a>.<sup id="cite_ref-php_5_objects_38-1" class="reference"><a href="#cite_note-php_5_objects-38" title="">[39]</a></sup> The drawback of this method was that the whole object was copied when a variable was assigned or passed as a parameter to a method. In the new approach, objects are referenced by <a target="_blank" href="http://en.wikipedia.org/wiki/Smart_pointer#Handles" title="Smart pointer">handle</a>, and not by value. PHP 5 introduced private and protected <a target="_blank" href="http://en.wikipedia.org/wiki/Member_variable" class="mw-redirect" title="Member variable">member variables</a> and methods, along with <a target="_blank" href="http://en.wikipedia.org/wiki/Abstract_type" title="Abstract type">abstract classes</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/Final_type" class="mw-redirect" title="Final type">final classes</a> as well as <a target="_blank" href="http://en.wikipedia.org/wiki/Abstract_method" class="mw-redirect" title="Abstract method">abstract methods</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/Final_method" class="mw-redirect" title="Final method">final methods</a>. It also introduced a standard way of declaring <a target="_blank" href="http://en.wikipedia.org/wiki/Constructor_%28computer_science%29" title="Constructor (computer science)">constructors</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/Destructor_%28computer_science%29" title="Destructor (computer science)">destructors</a>, similar to that of other object-oriented languages such as <a target="_blank" href="http://en.wikipedia.org/wiki/C%2B%2B" title="C++">C++</a>, and a standard <a target="_blank" href="http://en.wikipedia.org/wiki/Exception_handling" title="Exception handling">exception handling</a> model. Furthermore, PHP 5 added <a target="_blank" href="http://en.wikipedia.org/wiki/Interfaces" class="mw-redirect" title="Interfaces">interfaces</a> and allowed for multiple interfaces to be implemented. There are special interfaces that allow objects to interact with the runtime system. <a target="_blank" href="http://en.wikipedia.org/wiki/Object" title="Object">Objects</a> implementing <a target="_blank" href="http://en.wikipedia.org/wiki/ArrayAccess" class="mw-redirect" title="ArrayAccess">ArrayAccess</a> can be used with array syntax and <a target="_blank" href="http://en.wikipedia.org/wiki/Object" title="Object">objects</a> implementing <a target="_blank" href="http://en.wikipedia.org/wiki/Iterator" title="Iterator">Iterator</a> or <a target="_blank" href="http://en.wikipedia.org/wiki/IteratorAggregate" class="mw-redirect" title="IteratorAggregate">IteratorAggregate</a> can be used with the <span>foreach</span> language construct. There is no <a target="_blank" href="http://en.wikipedia.org/wiki/Virtual_table" class="mw-redirect" title="Virtual table">virtual table</a> feature in the engine, so <a target="_blank" href="http://en.wikipedia.org/wiki/Static_variable" title="Static variable">static variables</a> are bound with a name instead of a reference at compile time.<sup id="cite_ref-zend_engine_2_39-0" class="reference"><a href="#cite_note-zend_engine_2-39" title="">[40]</a></sup></p>
     <p>Basic <a  href="http://en.wikipedia.org/wiki/Object-oriented_programming" title="Object-oriented programming">object-oriented programming</a> functionality was added in PHP 3. Object handling was completely rewritten for PHP 5, expanding the feature set and enhancing performance. In previous versions of PHP, objects were handled like <a  href="http://en.wikipedia.org/wiki/Primitive_type" title="Primitive type">primitive types</a>. The drawback of this method was that the whole object was copied when a variable was assigned or passed as a parameter to a method. In the new approach, objects are referenced by <a  href="http://en.wikipedia.org/wiki/Smart_pointer#Handles" title="Smart pointer">handle</a>, and not by value. PHP 5 introduced private and protected <a  href="http://en.wikipedia.org/wiki/Member_variable" class="mw-redirect" title="Member variable">member variables</a> and methods, along with <a  href="http://en.wikipedia.org/wiki/Abstract_type" title="Abstract type">abstract classes</a> and <a  href="http://en.wikipedia.org/wiki/Final_type" class="mw-redirect" title="Final type">final classes</a> as well as <a  href="http://en.wikipedia.org/wiki/Abstract_method" class="mw-redirect" title="Abstract method">abstract methods</a> and <a  href="http://en.wikipedia.org/wiki/Final_method" class="mw-redirect" title="Final method">final methods</a>. It also introduced a standard way of declaring <a  href="http://en.wikipedia.org/wiki/Constructor_%28computer_science%29" title="Constructor (computer science)">constructors</a> and <a  href="http://en.wikipedia.org/wiki/Destructor_%28computer_science%29" title="Destructor (computer science)">destructors</a>, similar to that of other object-oriented languages such as <a  href="http://en.wikipedia.org/wiki/C%2B%2B" title="C++">C++</a>, and a standard <a  href="http://en.wikipedia.org/wiki/Exception_handling" title="Exception handling">exception handling</a> model. Furthermore, PHP 5 added <a  href="http://en.wikipedia.org/wiki/Interfaces" class="mw-redirect" title="Interfaces">interfaces</a> and allowed for multiple interfaces to be implemented. There are special interfaces that allow objects to interact with the runtime system. <a  href="http://en.wikipedia.org/wiki/Object" title="Object">Objects</a> implementing <a  href="http://en.wikipedia.org/wiki/ArrayAccess" class="mw-redirect" title="ArrayAccess">ArrayAccess</a> can be used with array syntax and <a  href="http://en.wikipedia.org/wiki/Object" title="Object">objects</a> implementing <a  href="http://en.wikipedia.org/wiki/Iterator" title="Iterator">Iterator</a> or <a  href="http://en.wikipedia.org/wiki/IteratorAggregate" class="mw-redirect" title="IteratorAggregate">IteratorAggregate</a> can be used with the <span>foreach</span> language construct. There is no <a  href="http://en.wikipedia.org/wiki/Virtual_table" class="mw-redirect" title="Virtual table">virtual table</a> feature in the engine, so <a  href="http://en.wikipedia.org/wiki/Static_variable" title="Static variable">static variables</a> are bound with a name instead of a reference at compile time.</p>
     <p>If the developer creates a copy of an object using the reserved word <i>clone</i>, the Zend engine will check if a <tt>__clone()</tt> method has been defined or not. If not, it will call a default <tt>__clone()</tt> which will copy the object's properties. If a <tt>__clone()</tt> method is defined, then it will be responsible for setting the necessary properties in the created object. For convenience, the engine will supply a function that imports the properties of the source object, so that the programmer can start with a by-value <a href="http://en.wiktionary.org/wiki/replica" class="extiw" title="wikt:replica">replica</a> of the source object and only override properties that need to be changed.<sup id="cite_ref-40" class="reference"><a href="#cite_note-40" title="">[41]</a></sup></p>
     <p>If the developer creates a copy of an object using the reserved word <i>clone</i>, the Zend engine will check if a <tt>__clone()</tt> method has been defined or not. If not, it will call a default <tt>__clone()</tt> which will copy the object's properties. If a <tt>__clone()</tt> method is defined, then it will be responsible for setting the necessary properties in the created object. For convenience, the engine will supply a function that imports the properties of the source object, so that the programmer can start with a by-value <a href="http://en.wiktionary.org/wiki/replica" class="extiw" title="wikt:replica">replica</a> of the source object and only override properties that need to be changed.</p>
     <p><a name="Resources" id="Resources"></a></p>
     <h2> <span class="mw-headline">Resources</span></h2>
     <p>PHP includes <a target="_blank" href="http://en.wikipedia.org/wiki/List_of_PHP_libraries" title="List of PHP libraries">free and open source libraries</a> with the core build. PHP is a fundamentally <a target="_blank" href="http://en.wikipedia.org/wiki/Internet" title="Internet">Internet</a>-aware system with modules built in for accessing <a target="_blank" href="http://en.wikipedia.org/wiki/File_transfer_protocol" class="mw-redirect" title="File transfer protocol">FTP</a> servers, many database servers, embedded SQL libraries such as embedded <a target="_blank" href="http://en.wikipedia.org/wiki/MySQL" title="MySQL">MySQL</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/SQLite" title="SQLite">SQLite</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol" title="Lightweight Directory Access Protocol">LDAP</a> servers, and others. Many functions familiar to C programmers such as those in the <tt><a target="_blank" href="http://en.wikipedia.org/wiki/Stdio.h" title="Stdio.h">stdio</a></tt> family are available in the standard PHP build.<sup id="cite_ref-41" class="reference"><a href="#cite_note-41" title="">[42]</a></sup> PHP has traditionally used features such as "<a target="_blank" href="http://en.wikipedia.org/wiki/Magic_quotes" title="Magic quotes">magic_quotes_gpc</a>" and "magic_quotes_runtime" which attempt to escape apostrophes (') and quotes (") in strings in the assumption that they will be used in databases, to prevent <a target="_blank" href="http://en.wikipedia.org/wiki/SQL_injection" title="SQL injection">SQL injection</a> attacks. This leads to confusion over which data is escaped and which is not, and to problems when data is not in fact used as input to a database and when the escaping used is not completely correct.<sup id="cite_ref-42" class="reference"><a href="#cite_note-42" title="">[43]</a></sup> To make code portable between servers which do and do not use magic quotes, developers can preface their code with a script to reverse the effect of magic quotes when it is applied.<sup id="cite_ref-43" class="reference"><a href="#cite_note-43" title="">[44]</a></sup></p>
     <p>PHP includes <a  href="http://en.wikipedia.org/wiki/List_of_PHP_libraries" title="List of PHP libraries">free and open source libraries</a> with the core build. PHP is a fundamentally <a  href="http://en.wikipedia.org/wiki/Internet" title="Internet">Internet</a>-aware system with modules built in for accessing <a  href="http://en.wikipedia.org/wiki/File_transfer_protocol" class="mw-redirect" title="File transfer protocol">FTP</a> servers, many database servers, embedded SQL libraries such as embedded <a  href="http://en.wikipedia.org/wiki/MySQL" title="MySQL">MySQL</a> and <a  href="http://en.wikipedia.org/wiki/SQLite" title="SQLite">SQLite</a>, <a  href="http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol" title="Lightweight Directory Access Protocol">LDAP</a> servers, and others. Many functions familiar to C programmers such as those in the <tt><a  href="http://en.wikipedia.org/wiki/Stdio.h" title="Stdio.h">stdio</a></tt> family are available in the standard PHP build. PHP has traditionally used features such as "<a  href="http://en.wikipedia.org/wiki/Magic_quotes" title="Magic quotes">magic_quotes_gpc</a>" and "magic_quotes_runtime" which attempt to escape apostrophes (') and quotes (") in strings in the assumption that they will be used in databases, to prevent <a  href="http://en.wikipedia.org/wiki/SQL_injection" title="SQL injection">SQL injection</a> attacks. This leads to confusion over which data is escaped and which is not, and to problems when data is not in fact used as input to a database and when the escaping used is not completely correct. To make code portable between servers which do and do not use magic quotes, developers can preface their code with a script to reverse the effect of magic quotes when it is applied.</p>
     <p>PHP allows developers to write <a  href="http://en.wikipedia.org/wiki/Extension_%28computing%29" class="mw-redirect" title="Extension (computing)">extensions</a> in <a  href="http://en.wikipedia.org/wiki/C_%28programming_language%29" title="C (programming language)">C</a> to add functionality to the PHP language. These can then be compiled into PHP or loaded dynamically at runtime. Extensions have been written to add support for the <a  href="http://en.wikipedia.org/wiki/Windows_API" title="Windows API">Windows API</a>, process management on <a  href="http://en.wikipedia.org/wiki/Unix-like" title="Unix-like">Unix-like</a> <a  href="http://en.wikipedia.org/wiki/Operating_system" title="Operating system">operating systems</a>, multibyte strings (<a  href="http://en.wikipedia.org/wiki/Unispan" title="Unispan">Unispan</a>), <a  href="http://en.wikipedia.org/wiki/CURL" title="CURL">cURL</a>, and several popular <a  href="http://en.wikipedia.org/wiki/Compression_formats" class="mw-redirect" title="Compression formats">compression formats</a>. Some more unusual features include integration with <a  href="http://en.wikipedia.org/wiki/Internet_relay_chat" class="mw-redirect" title="Internet relay chat">Internet relay chat</a>, dynamic generation of images and <a  href="http://en.wikipedia.org/wiki/Adobe_Flash" title="Adobe Flash">Adobe Flash</a> content, and even <a  href="http://en.wikipedia.org/wiki/Speech_synthesis" title="Speech synthesis">speech synthesis</a>. The <a  href="http://en.wikipedia.org/wiki/PHP_Extension_Community_Library" class="mw-redirect" title="PHP Extension Community Library">PHP Extension Community Library</a> (PECL) project is a repository for extensions to the PHP language.</p>
     <p>As with many scripting languages, PHP scripts are normally kept as human-readable source code, even on production web servers. While this allows flexibility, releasing scripts in source form is undesirable for commercial software developers, and can raise issues with security of web servers; as an example, if a hacker acquires control of a server, database passwords may be quickly discovered, and undesirable changes to scripts may be made that remain undiscovered indefinitely. Various encoding tools are available for PHP to offer code protection.</p>
     <p>span optimizers improve the quality of the compiled code by reducing its size and making changes that can reduce the execution time and improve performance. The nature of the PHP <a  href="http://en.wikipedia.org/wiki/Compiler" title="Compiler">compiler</a> is such that there are often opportunities for <a  href="http://en.wikipedia.org/wiki/Optimization_%28computer_science%29" title="Optimization (computer science)">span optimization</a>, and an example of a code optimizer is the <a  href="http://en.wikipedia.org/wiki/PHP_accelerator#Zend_Optimizer" title="PHP accelerator">Zend Optimizer</a> PHP extension.</p>
     <p><a  href="http://en.wikipedia.org/wiki/PHP_accelerator" title="PHP accelerator">PHP accelerators</a> can offer significant performance gains by <a  href="http://en.wikipedia.org/wiki/Caching" class="mw-redirect" title="Caching">caching</a> the compiled form of a PHP script in <a  href="http://en.wikipedia.org/wiki/Shared_memory" title="Shared memory">shared memory</a> to avoid the overhead of <a  href="http://en.wikipedia.org/wiki/Parsing" title="Parsing">parsing</a> and <a  href="http://en.wikipedia.org/wiki/Compiling" class="mw-redirect" title="Compiling">compiling</a> the code every time the script runs. They may also perform <a  href="http://en.wikipedia.org/wiki/span_optimization" class="mw-redirect" title="span optimization">span optimization</a> to provide increased execution performance.</p>
     <p>PHP allows developers to write <a target="_blank" href="http://en.wikipedia.org/wiki/Extension_%28computing%29" class="mw-redirect" title="Extension (computing)">extensions</a> in <a target="_blank" href="http://en.wikipedia.org/wiki/C_%28programming_language%29" title="C (programming language)">C</a> to add functionality to the PHP language. These can then be compiled into PHP or loaded dynamically at runtime. Extensions have been written to add support for the <a target="_blank" href="http://en.wikipedia.org/wiki/Windows_API" title="Windows API">Windows API</a>, process management on <a target="_blank" href="http://en.wikipedia.org/wiki/Unix-like" title="Unix-like">Unix-like</a> <a target="_blank" href="http://en.wikipedia.org/wiki/Operating_system" title="Operating system">operating systems</a>, multibyte strings (<a target="_blank" href="http://en.wikipedia.org/wiki/Unispan" title="Unispan">Unispan</a>), <a target="_blank" href="http://en.wikipedia.org/wiki/CURL" title="CURL">cURL</a>, and several popular <a target="_blank" href="http://en.wikipedia.org/wiki/Compression_formats" class="mw-redirect" title="Compression formats">compression formats</a>. Some more unusual features include integration with <a target="_blank" href="http://en.wikipedia.org/wiki/Internet_relay_chat" class="mw-redirect" title="Internet relay chat">Internet relay chat</a>, dynamic generation of images and <a target="_blank" href="http://en.wikipedia.org/wiki/Adobe_Flash" title="Adobe Flash">Adobe Flash</a> content, and even <a target="_blank" href="http://en.wikipedia.org/wiki/Speech_synthesis" title="Speech synthesis">speech synthesis</a>. The <a target="_blank" href="http://en.wikipedia.org/wiki/PHP_Extension_Community_Library" class="mw-redirect" title="PHP Extension Community Library">PHP Extension Community Library</a> (PECL) project is a repository for extensions to the PHP language.<sup id="cite_ref-44" class="reference"><a href="#cite_note-44" title="">[45]</a></sup></p>
     <p class="attribution">This excerpt is adapted from <a href="http://en.wikipedia.org/wiki/PHP#Syntax">Wikipedia: PHP - syntax</a>.  It is used here under a <a href="http://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License">Creative Commons BY-SA 3.0</a> license.</p>
     <p>As with many scripting languages, PHP scripts are normally kept as human-readable source code, even on production web servers.<sup id="cite_ref-45" class="reference"><a href="#cite_note-45" title="">[46]</a></sup> While this allows flexibility, releasing scripts in source form is undesirable for commercial software developers, and can raise issues with security of web servers; as an example, if a hacker acquires control of a server, database passwords may be quickly discovered, and undesirable changes to scripts may be made that remain undiscovered indefinitely. Various encoding tools are available for PHP to offer code protection.<sup class="noprint Template-Fact"><span title="This claim needs references to reliable sources&#160;since March 2008" style="white-space: nowrap;">[<i><a target="_blank" href="http://en.wikipedia.org/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a></i>]</span></sup></p>
     <p>span optimizers improve the quality of the compiled code by reducing its size and making changes that can reduce the execution time and improve performance. The nature of the PHP <a target="_blank" href="http://en.wikipedia.org/wiki/Compiler" title="Compiler">compiler</a> is such that there are often opportunities for <a target="_blank" href="http://en.wikipedia.org/wiki/Optimization_%28computer_science%29" title="Optimization (computer science)">span optimization</a><sup id="cite_ref-46" class="reference"><a href="#cite_note-46" title="">[47]</a></sup>, and an example of a code optimizer is the <a target="_blank" href="http://en.wikipedia.org/wiki/PHP_accelerator#Zend_Optimizer" title="PHP accelerator">Zend Optimizer</a> PHP extension.<sup id="cite_ref-47" class="reference"><a href="#cite_note-47" title="">[48]</a></sup></p>
     <p><a target="_blank" href="http://en.wikipedia.org/wiki/PHP_accelerator" title="PHP accelerator">PHP accelerators</a> can offer significant performance gains by <a target="_blank" href="http://en.wikipedia.org/wiki/Caching" class="mw-redirect" title="Caching">caching</a> the compiled form of a PHP script in <a target="_blank" href="http://en.wikipedia.org/wiki/Shared_memory" title="Shared memory">shared memory</a> to avoid the overhead of <a target="_blank" href="http://en.wikipedia.org/wiki/Parsing" title="Parsing">parsing</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/Compiling" class="mw-redirect" title="Compiling">compiling</a> the code every time the script runs. They may also perform <a target="_blank" href="http://en.wikipedia.org/wiki/span_optimization" class="mw-redirect" title="span optimization">span optimization</a> to provide increased execution performance.<sup class="noprint Template-Fact"><span title="This claim needs references to reliable sources&#160;since March 2008" style="white-space: nowrap;">[<i><a target="_blank" href="http://en.wikipedia.org/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed">citation needed</a></i>]</span></sup></p>

     <p>PHP is a general-purpose scripting language that is especially suited for <a target="_blank" href="http://en.wikipedia.org/wiki/Web_development" title="Web development">web development</a>. It is the fourth most popular computer programming language, ranking behind <a target="_blank" href="http://en.wikipedia.org/wiki/Java_%28programming_language%29" title="Java (programming language)">Java</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/C_%28programming_language%29" title="C (programming language)">C</a>, and <a target="_blank" href="http://en.wikipedia.org/wiki/Visual_Basic" title="Visual Basic">Visual Basic</a>.<sup id="cite_ref-22" class="reference"><a href="#cite_note-22" title="">[23]</a></sup> PHP generally runs on a <a target="_blank" href="http://en.wikipedia.org/wiki/Web_server" title="Web server">web server</a>, taking PHP code as its input and creating <a target="_blank" href="http://en.wikipedia.org/wiki/Web_page" title="Web page">web pages</a> as output. It can also be used for <a target="_blank" href="http://en.wikipedia.org/wiki/Command-line" class="mw-redirect" title="Command-line">command-line</a> scripting and <a target="_blank" href="http://en.wikipedia.org/wiki/Client-side" title="Client-side">client-side</a> <a target="_blank" href="http://en.wikipedia.org/wiki/Graphical_user_interface" title="Graphical user interface">GUI</a> applications. PHP can be deployed on most <a target="_blank" href="http://en.wikipedia.org/wiki/Web_server" title="Web server">web servers</a>, many <a target="_blank" href="http://en.wikipedia.org/wiki/Operating_system" title="Operating system">operating systems</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/Platform_%28computing%29" class="mw-redirect" title="Platform (computing)">platforms</a>, and can be used with many <a target="_blank" href="http://en.wikipedia.org/wiki/Relational_database_management_system" title="Relational database management system">relational database management systems</a>. It is available free of charge, and the PHP Group provides the complete source code for users to build, customize and extend for their own use.<sup id="cite_ref-foundations_4-1" class="reference"><a href="#cite_note-foundations-4" title="">[5]</a></sup></p>
     <p>PHP is a general-purpose scripting language that is especially suited for <a  href="http://en.wikipedia.org/wiki/Web_development" title="Web development">web development</a>. It is the fourth most popular computer programming language, ranking behind <a  href="http://en.wikipedia.org/wiki/Java_%28programming_language%29" title="Java (programming language)">Java</a>, <a  href="http://en.wikipedia.org/wiki/C_%28programming_language%29" title="C (programming language)">C</a>, and <a  href="http://en.wikipedia.org/wiki/Visual_Basic" title="Visual Basic">Visual Basic</a>. PHP generally runs on a <a  href="http://en.wikipedia.org/wiki/Web_server" title="Web server">web server</a>, taking PHP code as its input and creating <a  href="http://en.wikipedia.org/wiki/Web_page" title="Web page">web pages</a> as output. It can also be used for <a  href="http://en.wikipedia.org/wiki/Command-line" class="mw-redirect" title="Command-line">command-line</a> scripting and <a  href="http://en.wikipedia.org/wiki/Client-side" title="Client-side">client-side</a> <a  href="http://en.wikipedia.org/wiki/Graphical_user_interface" title="Graphical user interface">GUI</a> applications. PHP can be deployed on most <a  href="http://en.wikipedia.org/wiki/Web_server" title="Web server">web servers</a>, many <a  href="http://en.wikipedia.org/wiki/Operating_system" title="Operating system">operating systems</a> and <a  href="http://en.wikipedia.org/wiki/Platform_%28computing%29" class="mw-redirect" title="Platform (computing)">platforms</a>, and can be used with many <a  href="http://en.wikipedia.org/wiki/Relational_database_management_system" title="Relational database management system">relational database management systems</a>. It is available free of charge, and the PHP Group provides the complete source code for users to build, customize and extend for their own use.</p>
     <p>PHP primarily acts as a <a target="_blank" href="http://en.wikipedia.org/wiki/Filter_%28software%29" title="Filter (software)">filter</a><sup id="cite_ref-23" class="reference"><a href="#cite_note-23" title="">[24]</a></sup>, taking input from a file or stream containing text and/or PHP instructions and outputs another stream of data; most commonly the output will be HTML. From PHP 4, the PHP <a target="_blank" href="http://en.wikipedia.org/wiki/Parser" class="mw-redirect" title="Parser">parser</a> <a target="_blank" href="http://en.wikipedia.org/wiki/Compiler" title="Compiler">compiles</a> input to produce <a target="_blank" href="http://en.wikipedia.org/wiki/Bytecode" title="Bytecode">bytecode</a> for processing by the <a target="_blank" href="http://en.wikipedia.org/wiki/Zend_Engine" title="Zend Engine">Zend Engine</a>, giving improved performance over its <a target="_blank" href="http://en.wikipedia.org/wiki/Interpreter_%28computing%29" title="Interpreter (computing)">interpreter</a> predecessor.<sup id="cite_ref-24" class="reference"><a href="#cite_note-24" title="">[25]</a></sup></p>
     <p>PHP primarily acts as a <a  href="http://en.wikipedia.org/wiki/Filter_%28software%29" title="Filter (software)">filter</a>, taking input from a file or stream containing text and/or PHP instructions and outputs another stream of data; most commonly the output will be HTML. From PHP 4, the PHP <a  href="http://en.wikipedia.org/wiki/Parser" class="mw-redirect" title="Parser">parser</a> <a  href="http://en.wikipedia.org/wiki/Compiler" title="Compiler">compiles</a> input to produce <a  href="http://en.wikipedia.org/wiki/Bytecode" title="Bytecode">bytecode</a> for processing by the <a  href="http://en.wikipedia.org/wiki/Zend_Engine" title="Zend Engine">Zend Engine</a>, giving improved performance over its <a  href="http://en.wikipedia.org/wiki/Interpreter_%28computing%29" title="Interpreter (computing)">interpreter</a> predecessor.</p>
     <p>Originally designed to create dynamic web pages, PHP's principal focus is <a target="_blank" href="http://en.wikipedia.org/wiki/Server-side_scripting" title="Server-side scripting">server-side scripting</a><sup id="cite_ref-25" class="reference"><a href="#cite_note-25" title="">[26]</a></sup>, and it is similar to other server-side scripting languages that provide dynamic content from a web server to a <a target="_blank" href="http://en.wikipedia.org/wiki/Client_%28computing%29" title="Client (computing)">client</a>, such as <a target="_blank" href="http://en.wikipedia.org/wiki/Microsoft" title="Microsoft">Microsoft</a>'s <a target="_blank" href="http://en.wikipedia.org/wiki/ASP.NET" title="ASP.NET">ASP.NET</a> system, <a target="_blank" href="http://en.wikipedia.org/wiki/Sun_Microsystems" title="Sun Microsystems">Sun Microsystems</a>' <a target="_blank" href="http://en.wikipedia.org/wiki/JavaServer_Pages" title="JavaServer Pages">JavaServer Pages</a><sup id="cite_ref-26" class="reference"><a href="#cite_note-26" title="">[27]</a></sup>, and <a target="_blank" href="http://en.wikipedia.org/wiki/Mod_perl" title="Mod perl">mod_perl</a>. PHP has also attracted the development of many <a target="_blank" href="http://en.wikipedia.org/wiki/Software_framework" title="Software framework">frameworks</a> that provide building blocks and a design structure to promote <a target="_blank" href="http://en.wikipedia.org/wiki/Rapid_application_development" title="Rapid application development">rapid application development</a> (RAD). Some of these include <a target="_blank" href="http://en.wikipedia.org/wiki/CakePHP" title="CakePHP">CakePHP</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/PRADO" title="PRADO">PRADO</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/Symfony" title="Symfony">Symfony</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/Zend_Framework" title="Zend Framework">Zend Framework</a>, offering features similar to other <a target="_blank" href="http://en.wikipedia.org/wiki/List_of_web_application_frameworks" title="List of web application frameworks">web application frameworks</a>.</p>
     <p>Originally designed to create dynamic web pages, PHP's principal focus is <a  href="http://en.wikipedia.org/wiki/Server-side_scripting" title="Server-side scripting">server-side scripting</a>, and it is similar to other server-side scripting languages that provide dynamic content from a web server to a <a  href="http://en.wikipedia.org/wiki/Client_%28computing%29" title="Client (computing)">client</a>, such as <a  href="http://en.wikipedia.org/wiki/Microsoft" title="Microsoft">Microsoft</a>'s <a  href="http://en.wikipedia.org/wiki/ASP.NET" title="ASP.NET">ASP.NET</a> system, <a  href="http://en.wikipedia.org/wiki/Sun_Microsystems" title="Sun Microsystems">Sun Microsystems</a>' <a  href="http://en.wikipedia.org/wiki/JavaServer_Pages" title="JavaServer Pages">JavaServer Pages</a>, and <a  href="http://en.wikipedia.org/wiki/Mod_perl" title="Mod perl">mod_perl</a>. PHP has also attracted the development of many <a  href="http://en.wikipedia.org/wiki/Software_framework" title="Software framework">frameworks</a> that provide building blocks and a design structure to promote <a  href="http://en.wikipedia.org/wiki/Rapid_application_development" title="Rapid application development">rapid application development</a> (RAD). Some of these include <a  href="http://en.wikipedia.org/wiki/CakePHP" title="CakePHP">CakePHP</a>, <a  href="http://en.wikipedia.org/wiki/PRADO" title="PRADO">PRADO</a>, <a  href="http://en.wikipedia.org/wiki/Symfony" title="Symfony">Symfony</a> and <a  href="http://en.wikipedia.org/wiki/Zend_Framework" title="Zend Framework">Zend Framework</a>, offering features similar to other <a  href="http://en.wikipedia.org/wiki/List_of_web_application_frameworks" title="List of web application frameworks">web application frameworks</a>.</p>
     <p>The <a target="_blank" href="http://en.wikipedia.org/wiki/LAMP_%28software_bundle%29" title="LAMP (software bundle)">LAMP</a> architecture has become popular in the web industry as a way of deploying web applications. PHP is commonly used as the <i>P</i> in this bundle alongside <a target="_blank" href="http://en.wikipedia.org/wiki/Linux" title="Linux">Linux</a>, <a target="_blank" href="http://en.wikipedia.org/wiki/Apache_HTTP_Server" title="Apache HTTP Server">Apache</a> and <a target="_blank" href="http://en.wikipedia.org/wiki/MySQL" title="MySQL">MySQL</a>, although the <i>P</i> can also refer to <a target="_blank" href="http://en.wikipedia.org/wiki/Python_%28programming_language%29" title="Python (programming language)">Python</a> or <a target="_blank" href="http://en.wikipedia.org/wiki/Perl" title="Perl">Perl</a>.</p>
     <p>The <a  href="http://en.wikipedia.org/wiki/LAMP_%28software_bundle%29" title="LAMP (software bundle)">LAMP</a> architecture has become popular in the web industry as a way of deploying web applications. PHP is commonly used as the <i>P</i> in this bundle alongside <a  href="http://en.wikipedia.org/wiki/Linux" title="Linux">Linux</a>, <a  href="http://en.wikipedia.org/wiki/Apache_HTTP_Server" title="Apache HTTP Server">Apache</a> and <a  href="http://en.wikipedia.org/wiki/MySQL" title="MySQL">MySQL</a>, although the <i>P</i> can also refer to <a  href="http://en.wikipedia.org/wiki/Python_%28programming_language%29" title="Python (programming language)">Python</a> or <a  href="http://en.wikipedia.org/wiki/Perl" title="Perl">Perl</a>.</p>
     <p>As of April 2007, over 20 million Internet domains were hosted on servers with PHP installed, and PHP was recorded as the most popular Apache module.<sup id="cite_ref-usage_5-2" class="reference"><a href="#cite_note-usage-5" title="">[6]</a></sup></p>
     <p>As of April 2007, over 20 million Internet domains were hosted on servers with PHP installed, and PHP was recorded as the most popular Apache module.</p>
     <p class="attribution">This excerpt is adapted from <a href="http://en.wikipedia.org/wiki/PHP#Use">Wikipedia: PHP - use</a>.  It is used here under a <a href="http://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License">Creative Commons BY-SA 3.0</a> license.</p>

     core = 7.x
     dependencies[] = advanced_help
     ; Information added by Drupal.org packaging script on 2013-12-12
     version = "7.x-1.1"
     attributions[wikipedia_adaption][type] = 'asset'
     attributions[wikipedia_adaption][weight] = -10
     attributions[wikipedia_adaption][exception] = '#2460769'
     attributions[wikipedia_adaption][title] = 'About PHP, History of PHP, Usage of PHP, PHP Syntax, Security of PHP'
     attributions[wikipedia_adaption][license_url] = 'http://creativecommons.org/licenses/by-sa/3.0/'
     attributions[wikipedia_adaption][org_title] = 'PHP (Wikipedia)'
     attributions[wikipedia_adaption][org_author] = 'multiple Wikipedia contributors'
     attributions[wikipedia_adaption][org_author_url] = 'http://en.wikipedia.org/w/index.php?title=PHP&action=history'
     attributions[wikipedia_adaption][org_work_url] = 'http://en.wikipedia.org/wiki/PHP'
     attributions[wikipedia_adaption][org_license] = 'Creative Commons BY-SA 3.0'
     attributions[wikipedia_adaption][org_license_url] = 'http://en.wikipedia.org/wiki/Wikipedia:Text_of_Creative_Commons_Attribution-ShareAlike_3.0_Unported_License'
     attributions[lerdorf][type] = 'asset'
     attributions[lerdorf][exception] = '#2460769'
     attributions[lerdorf][author] = 'Jud Dagnall'
     attributions[lerdorf][work_url] = 'http://en.wikipedia.org/wiki/File:Lerdorf.jpg'
     attributions[lerdorf][title] = 'Lerdorf'
     attributions[lerdorf][license] = 'Creative Commons BY-SA 3.0'
     attributions[lerdorf][license_url] = 'http://creativecommons.org/licenses/by-sa/3.0/deed.en'
     attributions[gutmans][type] = 'asset'
     attributions[gutmans][exception] = '#2460769'
     attributions[gutmans][author] = 'Jim Winstead'
     attributions[gutmans][author_url] = 'https://www.flickr.com/people/81342178@N00'
     attributions[gutmans][work_url] = 'http://en.wikipedia.org/wiki/File:Andi_Gutmans_1.jpg'
     attributions[gutmans][title] = 'Andi Gutmans'
     attributions[gutmans][license] = 'Creative Commons BY 2.0'
     attributions[gutmans][license_url] = 'http://creativecommons.org/licenses/by/2.0/deed.en'
     ; Information added by Drupal.org packaging script on 2015-03-27
     version = "7.x-1.2"
     core = "7.x"
     project = "advanced_help"
     datestamp = "1386871727"
     datestamp = "1427460482"

+    }
     /**
      * Help topic index.
      * Topic index callback.
      */
     function help_example_index_page() {
       $output = theme('advanced_help_topic', array(

       );
       $form['captcha_form_protection']['captcha_form_id_overview']['captcha_captcha_points'] = array();
       $captcha_type_options = _captcha_available_challenge_types();
       $result = db_select('captcha_points', 'cp')->fields('cp')->orderBy('form_id')->execute();
       foreach ($result as $captcha_point) {
         $form['captcha_form_protection']['captcha_form_id_overview']['captcha_captcha_points'][$captcha_point->form_id] = array();
         $form['captcha_form_protection']['captcha_form_id_overview']['captcha_captcha_points'][$captcha_point->form_id]['form_id'] = array(
       $captcha_points = captcha_get_captcha_points();
       foreach ($captcha_points as $captcha_point) {
         $elem = array();
         $elem['form_id'] = array(
           '#markup' => $captcha_point->form_id,
         );
         // Select widget for CAPTCHA type.
-...
         else {
           $captcha_type = 'none';
+        }
         $form['captcha_form_protection']['captcha_form_id_overview']['captcha_captcha_points'][$captcha_point->form_id]['captcha_type'] = array(
         $elem['captcha_type'] = array(
           '#type' => 'select',
           '#default_value' => $captcha_type,
           '#options' => $captcha_type_options,
         );
         // Additional operations.
         $form['captcha_form_protection']['captcha_form_id_overview']['captcha_captcha_points'][$captcha_point->form_id]['operations'] = array(
           '#markup' => implode(", ", array(
             l(t('delete'), "admin/config/people/captcha/captcha/captcha_point/{$captcha_point->form_id}/delete"),
           )),
         );
         $ops = array();
         if (module_exists('ctools') && $captcha_point->export_type & EXPORT_IN_CODE) {
           if ($captcha_point->export_type & EXPORT_IN_DATABASE) {
             $ops[] = l(t('revert'), "admin/config/people/captcha/captcha/captcha_point/{$captcha_point->form_id}/delete");
+          }
           // TODO Disable exported points.
+        }
         else {
           $ops[] = l(t('delete'), "admin/config/people/captcha/captcha/captcha_point/{$captcha_point->form_id}/delete");
+        }
         $elem['operations'] = array('#markup' => implode(", ", $ops));
         $form['captcha_form_protection']['captcha_form_id_overview']['captcha_captcha_points'][$captcha_point->form_id] = $elem;
+      }
       // Form items for new form_id.
-...
       // Process CAPTCHA points.
       if (isset($form_state['values']['captcha_form_id_overview']['captcha_captcha_points'])) {
         // Load existing data.
         $captcha_points = captcha_get_captcha_points();
         foreach ($form_state['values']['captcha_form_id_overview']['captcha_captcha_points'] as $captcha_point_form_id => $data) {
           // If this is an in-code captcha point and its settings are unchanged,
           // don't save to the database.
           if (module_exists('ctools') && isset($captcha_points[$captcha_point_form_id])) {
             // Parse module and captcha_type from submitted values.
             if (is_string($data['captcha_type']) && substr_count($data['captcha_type'], '/') == 1) {
               list($module, $captcha_type) = explode('/', $data['captcha_type']);
+            }
             else {
               $module = '';
               $captcha_type = $data['captcha_type'];
+            }
             $point = $captcha_points[$captcha_point_form_id];
             if ($point->export_type & EXPORT_IN_CODE && !($point->export_type & EXPORT_IN_DATABASE) && $point->module == $module && $point->captcha_type == $captcha_type) {
               continue;
+            }
+          }
           captcha_set_form_id_setting($captcha_point_form_id, $data['captcha_type']);
+        }
+      }

      */
     function captcha_get_form_id_setting($form_id, $symbolic = FALSE) {
       // Fetch setting from database.
       $result = db_query("SELECT module, captcha_type FROM {captcha_points} WHERE form_id = :form_id", array(':form_id' => $form_id));
       $captcha_point = $result->fetchObject();
       if (module_exists('ctools')) {
         ctools_include('export');
         $object = ctools_export_load_object('captcha_points', 'names', array($form_id));
         $captcha_point = array_pop($object);
+      }
       else {
         $result = db_query("SELECT module, captcha_type FROM {captcha_points} WHERE form_id = :form_id",
           array(':form_id' =>  $form_id));
         $captcha_point = $result->fetchObject();
+      }
       // If no setting is available in database for the given form,
       // but 'captcha_default_challenge_on_nonlisted_forms' is enabled, pick the default type anyway.
-...
       return $captcha_point;
+    }
     /**
      * Helper function to load all captcha points.
+     *
      * @return array of all captcha_points
      */
     function captcha_get_captcha_points() {
       if (module_exists('ctools')) {
         ctools_include('export');
         $captcha_points = ctools_export_load_object('captcha_points', 'all');
+      }
       else {
         $captcha_points = array();
         $result = db_select('captcha_points', 'cp')->fields('cp')->orderBy('form_id')->execute();
         foreach ($result as $captcha_point) {
           $captcha_points[] = $captcha_point;
+        }
+      }
       return $captcha_points;
+    }
     /**
      * Helper function for generating a new CAPTCHA session.
+     *

     files[] = captcha.install
     files[] = captcha.test
     ; Information added by Drupal.org packaging script on 2014-11-29
     version = "7.x-1.2"
     ; Information added by Drupal.org packaging script on 2015-03-27
     version = "7.x-1.3"
     core = "7.x"
     project = "captcha"
     datestamp = "1417219372"
     datestamp = "1427464219"

       // Table for positions and types of the challenges.
       $schema['captcha_points'] = array(
         'description' => 'This table describes which challenges should be added to which forms.',
         'export' => array(
           'key' => 'form_id',
           'identifier' => 'captcha',
           'default hook' => 'captcha_default_points',  // Function hook name.
           'status' => 'mark_status',
           'api' => array(
             'owner' => 'captcha',
             'api' => 'captcha',  // Base name for api include files.
             'minimum_version' => 1,
             'current_version' => 1,
           ),
         ),
         'fields' => array(
           'form_id' => array(
             'description' => 'The form_id of the form to add a CAPTCHA to.',
-...
      */
     function captcha_install() {
       $t = get_t();
       // Insert some default CAPTCHA points.
       $form_ids = array(
         'contact_site_form', 'contact_personal_form',
         'user_register_form', 'user_pass', 'user_login', 'user_login_block',
         'forum_node_form',
       );
       // Add form_ids of all currently known node types too.
       foreach (node_type_get_names() as $type => $name) {
         $form_ids[] = 'comment_node_' . $type . '_form';
+      }
       foreach ($form_ids as $form_id) {
         db_insert('captcha_points')
           ->fields(array(
             'form_id' => $form_id,
             'module' => NULL,
             'captcha_type' => NULL,
           ))
           ->execute();
+      }
       // Be friendly to your users: what to do after install?
       drupal_set_message($t('You can now <a href="!captcha_admin">configure the CAPTCHA module</a> for your site.',

       return $element;
+    }
     /**
      * Implementation of hook_captcha_default_points_alter().
+     *
      * Provide some default captchas only if defaults are not already
      * provided by other modules.
      */
     function captcha_captcha_default_points_alter(&$items) {
       $modules = array(
         'comment' => array(
         ),
         'contact' => array(
           'contact_site_form',
           'contact_personal_form'
         ),
         'forum' => array(
           'forum_node_form',
         ),
         'user' => array(
           'user_register_form',
           'user_pass',
           'user_login',
           'user_login_block',
         ),
       );
       // Add comment form_ids of all currently known node types.
       foreach (node_type_get_names() as $type => $name) {
         $modules['comment'][] = 'comment_node_' . $type . '_form';
+      }
       foreach ($modules as $module => $form_ids) {
         // Only give defaults if the module exists.
         if (module_exists($module)) {
           foreach ($form_ids as $form_id) {
             // Ensure a default has not been provided already.
             if (!isset($items[$form_id])) {
               $captcha = new stdClass;
               $captcha->disabled = FALSE;
               $captcha->api_version = 1;
               $captcha->form_id = $form_id;
               $captcha->module = '';
               $captcha->captcha_type = 'default';
               $items[$form_id] = $captcha;
+            }
+          }
+        }
+      }
+    }
     /**
      * Theme function for a CAPTCHA element.
+     *
-...
         $form['caching']['captcha'] = array(
           '#type' => 'item',
           '#title' => t('CAPTCHA'),
           '#markup' => t('!icon The CAPTCHA module will disable the caching of pages that contain a CAPTCHA element.', array(
             '!icon' => '<span class="icon">' . $icon . '</span>')
           '#markup' => t(
             '!icon The CAPTCHA module will disable the caching of pages that contain a CAPTCHA element.',
             array(
               '!icon' => '<span class="icon">' . $icon . '</span>'
+            )
           ),
           '#attributes' => array('class' => array('warning')),
         );
-...
+    }
     /**
      * Helper function for getting the posted CAPTCHA info (posted form_id and CAPTCHA sessions ID) from a form in case it is posted.
      * Helper function for getting the posted CAPTCHA info (posted form_id and
      * CAPTCHA sessions ID) from a form in case it is posted.
+     *
      * This function hides the form processing mess for several use cases an
      * browser bug workarounds.
-...
         // we should be extra cautious and filter this data.
         $posted_form_id = isset($form_state['input']['form_id']) ? preg_replace("/[^a-z0-9_]/", "", (string) $form_state['input']['form_id']) : NULL;
         $posted_captcha_sid = isset($form_state['input']['captcha_sid']) ? (int) $form_state['input']['captcha_sid'] : NULL;
         $posted_captcha_token = isset($form_state['input']['captcha_token']) ? preg_replace("/[^a-zA-Z0-9]/", "", (string) $form_state['input']['captcha_token']) : NULL;
         $posted_captcha_token = !empty($form_state['input']['captcha_token']) ? preg_replace("/[^a-zA-Z0-9]/", "", (string) $form_state['input']['captcha_token']) : NULL;
         if ($posted_form_id == $this_form_id) {
           // Check if the posted CAPTCHA token is valid for the posted CAPTCHA
-...
               "SELECT token FROM {captcha_sessions} WHERE csid = :csid",
               array(':csid' => $posted_captcha_sid)
             )->fetchField();
             if ($expected_captcha_token !== $posted_captcha_token) {
               drupal_set_message(t('CAPTCHA session reuse attack detected.'), 'error');
               // Invalidate the CAPTCHA session.
               $posted_captcha_sid = NULL;
+            }
             // Invalidate CAPTCHA token to avoid reuse.
             db_update('captcha_sessions')
               ->fields(array('token' => NULL))
               ->condition('csid', $posted_captcha_sid);
               ->condition('csid', $posted_captcha_sid)
               ->execute();
+          }
+        }
         else {
-...
      * files).
      */
     function captcha_validate($element, &$form_state) {
       // If disable captcha mode is enabled, bypass captcha validation.
       if (variable_get('disable_captcha', FALSE)) {
         return;
+      }
       $captcha_info = $form_state['captcha_info'];
       $form_id = $captcha_info['this_form_id'];

drupal7/sites/all/modules/captcha/captcha_api.txt
215	215	- in the 'my_fancy_form' form inside the container $form['items']['buttons'],
216	216	just before the element $form['items']['buttons']['sacebutton'].
217	217	- in the 'another_form' form at the toplevel of the form, with a weight 34.
218

     It possible to put your own fonts for the Image CAPTCHA in this folder.
     However, this is not the recommended way, as they can get lost easily during
     a module update. The recommended way to provide your own fonts is putting them
     in the files directory of your Drupal setup or, just like with contributed
     modules and themes, in the "libraries" folders sites/all/libraries/fonts
     or sites/<site>/libraries/fonts.
     or sites/<site>/libraries/fonts.

drupal7/sites/all/modules/captcha/image_captcha/image_captcha.css
27	27	.image_captcha_admin_fonts_selection img {
28	28	vertical-align: middle;
29	29	}
30

     name = "Image CAPTCHA"
     description = "Provides an image based CAPTCHA."
     description = "Provides an image based CAPTCHA challenge."
     package = "Spam control"
     dependencies[] = captcha
     core = 7.x
-...
     files[] = image_captcha.admin.inc
     files[] = image_captcha.user.inc
     ; Information added by Drupal.org packaging script on 2014-11-29
     version = "7.x-1.2"
     ; Information added by Drupal.org packaging script on 2015-03-27
     version = "7.x-1.3"
     core = "7.x"
     project = "captcha"
     datestamp = "1417219372"
     datestamp = "1427464219"

drupal7/sites/all/modules/captcha/image_captcha/image_captcha.module
246	246	);
247	247	$img_src = check_url(url("image_captcha", $options));
248	248	list($width, $height) = _image_captcha_image_size($code);

Projet

Général

Profil

Club Drupal

Révision 00c2605a

Ajouté par Assos Assos il y a environ 9 ans