Dmitry Pripa

OMG!PRESS

Development Assistant is a comprehensive toolkit designed to streamline the development process and enhance support capabilities within WordPress. Whether you’re a seasoned developer or a novice WordPress user, this plugin provides essential functionalities to manage debugging, diagnose issues, and facilitate smoother development workflows.
<h4>Features</h4>
<ul>
<li>Debugging Made Easy: Enable WP_DEBUG, WP_DEBUG_LOG, and WP_DEBUG_DISPLAY modes directly from the WordPress admin panel without the need to manually edit the wp-config.php file. Effortlessly toggle these settings to facilitate efficient debugging and error tracking.</li>
<li>Create Support User in One Click: Create a support user with a single click to provide temporary access to your WordPress environment. This feature simplifies the process of sharing debugging information with developers or support teams, enabling them to diagnose and resolve issues more effectively. You can control after how many days the user will be auto-deleted. After creating a user, you can quickly copy the credentials to the clipboard, or share them via email (optionally adding a message).</li>
<li>Plugin Conflict Resolution: Simplify the process of identifying and resolving plugin conflicts. Quickly compare the performance of active and inactive plugins, and temporarily disable or enable plugins to isolate issues without disrupting your entire plugin ecosystem.</li>
<li>SMTP Testing with MailHog: Seamlessly integrate MailHog for SMTP testing purposes. Verify the functionality of email delivery within your WordPress environment, ensuring reliable communication with users and clients.</li>
<li>Download Plugins: Download plugins directly from the WordPress admin panel’s plugin view. Streamline your workflow by easily obtaining plugin files for offline storage, manual installation, or testing in other environments and sandboxes. This feature facilitates seamless testing of plugins in various environments, allowing for thorough evaluation and development iterations.</li>
<li>Reset: Effortlessly undo any changes made by the plugin to restore your WordPress environment to its original state. This feature deletes all plugin settings and data from the database, resets debug constants to their pre-activation states, deletes the debug.log file (if it didn’t exist before activation), and activates any temporarily deactivated plugins.</li>
</ul>
<h4>Who Can Benefit</h4>
<ul>
<li>Power Developers: Streamline your development workflow with a comprehensive toolkit tailored for debugging and issue resolution. Enhance productivity and efficiency while tackling complex WordPress projects.</li>
<li>Novice Users: Empower yourself to diagnose and troubleshoot WordPress issues with ease. Quickly share debugging information with developers or support teams to expedite issue resolution and enhance your WordPress experience.</li>
</ul>
Development Assistant is your go-to solution for simplifying WordPress development tasks and enhancing support capabilities. Whether you’re troubleshooting intricate issues or optimizing your development workflow, this plugin equips you with the tools you need for success.

Development Assistant


It basically does what any coder would know how to do manually. But, it leaves code, when deleted, that causes errors. I'll now have to wade through my installation to find what it screwed up.


Horribly buggy!

Toolkit for debugging and customer support.

Alley

Matthew Boynes

This plugin provides a simple interface for testing your custom rewrite rules.
The purpose of this plugin is to be able to test your own rewrite rules, so 
you’re probably most interested in knowing how to do that, right? The plugin 
provides a filter, <code>rewrite_testing_tests</code> to add your own tests. That filter 
passes an associative array of name => tests. The tests array is an associative 
array of URI => expected match. In the outer array, the “name” is arbitrary and 
for your own reference. In the inner array, the “URI” is the path you want to 
test, and the “expected match” is what WordPress should find as a rewrite 
match.
Enough chit-chat, here’s an example:
<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>
You can see the <code>test_cases()</code> method for a full suite of tests for the “Day 
and Name” permalink structure. It’s not necessary to leave these in (in fact, 
the above demo would wipe them out), unless you want to make sure that your 
custom rewrites aren’t affecting core rewrites. If you aren’t using “Day and 
Name” permalinks, you’ll need to adjust the tests to fit your permalink 
structure.
<h3>Todo</h3>
<ul>
<li>Add a debug bar extension which reads a transient; the transient would be 
updated whenever rewrite rules are flushed. The debug bar extension would 
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.

Development Assistant vs Rewrite Rule Testing