David Pullin

<p>A WordPress plugin to provide general tools to assist with WordPress development and maintenance. Each tool within this collection is pluggable, allowing you full control, over which ones are loaded.</p>
<p>Main features include:-</p>
<ul>
<li>Internal Developer Log (database table with viewer) that can be called from code to log message, debug details etc.</li>
<li>Send A Test Email</li>
<li>List Cookies (client side)</li>
<li>Clear WordPress’ Core Updater Lock & Increase PHP execution time to assist with timeout issues</li>
</ul>
<h3>Deactivation</h3>
<p>When deactivating this plugin from WordPress’ Plugins maintenance any option relating to deactivating will be adhered to even if that tool is disabled (as<br />
long as the tool’s physical file is still present).</p>
<p>For example, even if you disable the loading of the Development Logging Support tool, when this plugin is deactivated, if the Logging Support’s tool option to drop the log table on deactivation is set, the database table will still be deleted.</p>
<h3>Pluggable</h3>
<p>Each tool is in itself pluggable and can be removed or disabled from your WordPress installation.</p>
<p>You may wish to do this to limit which tools are available on your live site.</p>
<p>There are two different methods of disabling a tool.</p>
<h4>Removing via Administration Options</h4>
<p>On the main general settings screen you are able to choose which tools are active.  By default tools are active and by default any new tools in<br />
future updates of this plugin will default to active. You can also change this behaviour by turning off the option to activate new tools by default.</p>
<h4>Removing via Physical File Deletion</h4>
<p>Each tool exists within the tools\ sub-directory.  You can disable a tool simply by deleting the file or rename it so it is no longer prefixed with zhu_dt_.</p>
<p>Please note, if you apply an update to this plugin the removed file will be placed back as part of the update process.  Upon restoring the file it will be treated as a newly detected tool which may be enabled depending on the option to activate new tools by default.  You can find this option on the general settings screen.</p>
<h3>The Tools</h3>
<ol>
<li>Tool Activator & Client Development Toolbar</li>
<li>Generic development log database table</li>
<li>Quick email test</li>
<li>Cookie viewer</li>
<li>Update Assist</li>
</ol>
<h3>1. Tool Activator & Client Development Toolbar</h3>
<p>This tool provides UI support on the general settings screen to allow you to enable and disable other tools.</p>
<p>You cannot disable this tool via the UI but like the other files in the tool directory you can remove the file zhu_dt_activator.class.php to disable UI support.</p>
<h3>Client Development Toolbar</h3>
<p>Some tools provide features to be available on the client side (i.e. your website not the admin area of WordPress). If there are no tools enabled that provide client side features the toolbar will not be displayed.</p>
<p>To prevent the toolbar being displayed for everyone, i.e. public, it is also restricted to the specified user as per its settings.  This however, will only work when that user is logged into WordPress and viewing their site.</p>
<p>However, there may be times, when you wish to use these tools when visiting your site as a member of the public and therefore you will not be logged into WordPress.  To achieve this, the toolbar has an option to create a browser cookie containing an Activation ID.  This ID is then matched with the ID that you will need to enter into the tool’s settings.  If matched then the toolbar is rendered on the system with the matching cookie value.</p>
<p>The toolbar hooks into WordPress wp_body_open action to inject required HTML. wp_body_open was introduced into WordPress 5.2.0 which should be triggered via your theme after the open body html tag.  As such, if your theme does not support this then the client toolbar will not be displayed.</p>
<h3>2. Generic development log database table</h3>
<p>Tool filename: zhu_dt_log.class.php</p>
<p>Provides a public function to call via your code to record a log into the database</p>
<pre><code>public function zhu_log(    string $content) {}
E.g. zhu_log(‘testing my feature ‘ . $mode);
</code></pre>
<p>This function records, with a date a time stamp, into the database table [wp]_zhu_log.  Where [wp] is your site’s database table prefix.  Entries in this table can be viewed via this plugin’s log viewer which is accessible from the Administration Menu.</p>
<p>The log can be truncated at anytime via the truncate button found on this plugin’s options page.</p>
<p>In the event that this tool has been disabled or zhu_dt_log.class.php has been removed any calls to zhu_log() within your own code will <em>not</em> fail. However no logging will take place as zhu_log() simply becomes a do nothing function.  This allows you to keep your logging code in place, if required, and enable/disable the actual recording to the database by enabling and disabling this tool as required.</p>
<h3>3. Email Test</h3>
<p>Tool filename: zhu_dt_send_test_email.class.php</p>
<p>Provides, within this plugin’s options screen, a quick test to send an email using WordPress’ wp_mail() function.</p>
<p>The email address, subject and body of the email are remembered for next time. If an error is detected its details are displayed on screen.</p>
<h3>4. Cookie Viewer</h3>
<p>Tool filename: zhu_dt_cookie_viewer.class.php</p>
<p>When enabled, this tool adds an icon to the main site’s floating toolbar. The feature allows you to view cookies used by the site.  Detection is performed bia locally running JavaScript.</p>
<p>This pop-up viewer also provides an easy method of deleting individual cookies.</p>
<h3>5. Update Assist</h3>
<p>Tool filename: zhu_dt_cookie_viewer.class.php</p>
<p>This tool provides a simple button to remove WordPress’s Core Updater Lock. This will remove WordPress’s internal “lock” that is used by WordPress to indicate that a core update is taking place.  Whan a core update fails, for example, due to a timeout issue when downloading, the lock may still be present.  As such, when you try again WordPess displays the message “Another Update in Progress”.</p>
<p>This tool also allows you to set the value of PHP’s max_execution_time.  This may assist with timeout issues when downloading updates.  After enabling this option and pressing save the tool will inform you as best it can with the results of applying the change.  Please note, that some hosting providers configure their systems so changing this value has no effect even even if PHP reports the change was successful.</p>


Zhu Development Tools for WordPress

A WordPress plugin to provide general tools to assist with WordPress development and maintenance. Each tool within this collection is pluggable, allow …

Alley

Matthew Boynes

<p>This plugin provides a simple interface for testing your custom rewrite rules.</p>
<p>The purpose of this plugin is to be able to test your <em>own</em> rewrite rules, so<br />
you’re probably most interested in knowing how to do that, right? The plugin<br />
provides a filter, <code>rewrite_testing_tests</code> to add your own tests. That filter<br />
passes an associative array of name => tests. The tests array is an associative<br />
array of URI => expected match. In the outer array, the “name” is arbitrary and<br />
for your own reference. In the inner array, the “URI” is the path you want to<br />
test, and the “expected match” is what WordPress should find as a rewrite<br />
match.</p>
<p>Enough chit-chat, here’s an example:</p>
<pre><code>function my_rewrite_tests( $tests ) {
  return array(
    'Events' => array(
      '/event/super-bowl/' => 'index.php?event=$matches[1]',
      '/event/super-bowl/page/2/' => 'index.php?event=$matches[1]&paged=$matches[2]'
    )
  );
}
add_filter( 'rewrite_testing_tests', 'my_rewrite_tests' );
</code></pre>
<p>You can see the <code>test_cases()</code> method for a full suite of tests for the “Day<br />
and Name” permalink structure. It’s not necessary to leave these in (in fact,<br />
the above demo would wipe them out), unless you want to make sure that your<br />
custom rewrites aren’t affecting core rewrites. If you aren’t using “Day and<br />
Name” permalinks, you’ll need to adjust the tests to fit your permalink<br />
structure.</p>
<h3>Todo</h3>
<ul>
<li>Add a debug bar extension which reads a transient; the transient would be<br />
updated whenever rewrite rules are flushed. The debug bar extension would<br />
show pass/fail status and link directly to the settings page.</li>
<li>Add tests for other permalink structures?</li>
<li>Add a way to run this as part of phpunit</li>
</ul>


Rewrite Rule Testing

Regex and WordPress rewrite rules are probably my two Least Favourite Things, so this plugin is essential for making sure I haven't messed anything up :)



Nice

Unit test your rewrite rules from the WordPress Admin.

Zhu Development Tools for WordPress vs Rewrite Rule Testing