Mikael Korpela

Miguel Lezama

A tool to observe how a page loads in different themes simultaneously. 
Useful for debugging plugins or Gutenberg blocks.
How to Use:
<ol>
<li>Install several themes you’d like to check out.</li>
<li>Create a new page.</li>
<li>Navigate to Tools → Back To The Theme</li>
<li>Choose if you want to demo editor- or view side.</li>
<li>Select the themes you’d like to check out.</li>
<li>Choose the page you just created. This page will be previewed with all the themes you’ve selected.</li>
<li>Click Do it!.</li>
<li>Scroll to see the page rendered with all the themes you selected.</li>
</ol>
You’ll see your page load with different themes in a bunch of iframes for handy preview and debugging.
A nice list of popular themes to test:
<pre><code>`
</code></pre>
wp theme install \ 
 astra \ 
 colormag \ 
 customizr \ 
 generatepress \ 
 hestia \ 
 hueman \ 
 oceanwp \ 
 shapely \ 
 storefront \ 
 sydney \ 
 twentyeleven \ 
 twentyfifteen \ 
 twentyfourteen \ 
 twentynineteen \ 
 twentyseventeen \ 
 twentysixteen \ 
 twentyten \ 
 twentythirteen \ 
 twentytwelve \ 
 vantage 
 `
See docs for <a href="https://developer.wordpress.org/cli/commands/theme/install/" rel="nofollow ugc">wp theme install</a>.
<a href="https://github.com/simison/back-to-the-theme" rel="nofollow ugc">Plugin’s source code on GitHub</a>.

Back To The Theme

See a page with different themes all at once, just like that!

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.

Back To The Theme vs Rewrite Rule Testing