Fixed issue #1537: Add links to documentation to various different "f…

…eatures" after wizard has run

html/docs/include/features/profiler.html

@@ -28,7 +28,13 @@ <h2>Introduction <a name="Introduction" href="#Introduction">#</a></h2>
 
 <h2>Starting The Profiler <a name="starting" href="#starting">#</a></h2>
 
-<p>Profiling is enabled by setting [CFG:mode] to <code>profile</code>. This
+<p>In your <code>php.ini</code>, <code>99-xdebug.ini</code>, or other
+distribution specific PHP ini file, change (or set) the [CFG:mode] setting to
+<code>profile</code>. Please refer to <a
+href='/docs/install#configure-php'>Configure PHP</a> in the documentation to
+find out which PHP ini file to modify.</p>
+
+<p>This
 instructs Xdebug to start writing profiling information into the directory
 configured with the [CFG:output_dir] directive. The name of the generated file
 always starts with "<span class="filename">cachegrind.out.</span>" and ends by

html/docs/include/features/step_debug.html

@@ -14,9 +14,13 @@ <h2>Introduction <a name="Introduction" href="#Introduction">#</a></h2>
 <a name="starting"></a>
 <h2>Configuring Step Debugging <a name="configure" href="#configure">#</a></h2>
 
-<p>In your <code>php.ini</code>, <code>90-xdebug.ini</code>, or other
+<p>In your <code>php.ini</code>, <code>99-xdebug.ini</code>, or other
 distribution specific PHP ini file, change (or set) the [CFG:mode] setting to
-<code>debug</code>. In set-ups where PHP/Xdebug and your IDE all run on the
+<code>debug</code>. Please refer to <a
+href='/docs/install#configure-php'>Configure PHP</a> in the documentation to
+find out which PHP ini file to modify.</p>
+
+<p>In set-ups where PHP/Xdebug and your IDE all run on the
 same host, this is all you need to configure on the PHP and Xdebug side.
 <small>(Skip to <a href='#activate_debugger'>Activating the Debugger</a> if
 that's the case.)</small> </p>

views/docs/all_settings.php

@@ -12,7 +12,7 @@
 </p>
 <p>
 Unless specifically mentioneds, each setting can be set in
-<code>php.ini</code>, files like <code>90-xdebug.ini</code>, but also in
+<code>php.ini</code>, files like <code>99-xdebug.ini</code>, but also in
 Apache's <code>.htaccess</code> and PHP-FPM's <code>.user.ini</code> files.
 </p>
 <a name="XDEBUG_CONFIG"></a>

views/wizard/result.php

@@ -158,3 +158,24 @@
 		<li>Restart the webserver</li>
 	<?php endif ?>
 </ol>
+
+<h2>Enabling Features</h2>
+
+<p>Now Xdebug is installed, you can enable its features. Please refer to the
+dedicated sections in the documentation about information on how to enable and
+configure these Xdebug features.
+<?php if ( $iniFileName ) : ?>
+	Where these sections refer to <code>php.ini</code> or similar, please
+	remember to use <code><?= $iniFileName ?></code>:</p>
+<?php endif ?>
+
+<ul>
+	<li><a href='/docs/develop'>Development Helpers</a> — help you get better
+	error messages and obtain better information from PHP's built-in
+	functions.</li>
+	<li><a href='/docs/step_debug'>Step Debugging</a> — allows you to
+	interactively walk through your code to debug control flow and examine data
+	structures.</li>
+	<li><a href='/docs/profiler'>Profiling</a> — allows you to find
+	bottlenecks in your script and visualize those with an external tool.</li>
+</ul>