Map your archives to pages. Map 404 and term archives as well.

Ronald Huereca

Paal Joachim Romdahl

Christopher Logan

<p>A WordPress plugin for displaying posts and terms (e.g., categories) using a Gutenberg block. Works well with posts, pages, custom post types, taxonomies, and terms.</p>
<p>Bonus: archive mapping.</p>
<blockquote>
<p><strong>Archive Pages Pro is here</strong>: Map post types, terms, authors, and more to pages. <a href="https://dlxplugins.com/plugins/archive-pages-pro/" rel="nofollow ugc">Learn more about Archive Pages Pro</a></p>
</blockquote>
<ul>
<li>Map your post type archives to a page for customization of the post type archive page.</li>
<li>Map your category archives to a page for customization of the term archive page.</li>
<li>Map your 404 template to a page and easily customize your 404 page.</li>
</ul>
<p><a href="https://mediaron.com/custom-query-blocks/" rel="nofollow ugc">View Documentation and Overview</a></p>
<p>The plugin currently has three blocks:</p>
<ul>
<li><a href="https://mediaron.com/custom-query-blocks/custom-post-types-block/" rel="nofollow ugc">Custom Post Types Block</a></li>
<li><a href="https://mediaron.com/custom-query-blocks/term-category-grid-block/" rel="nofollow ugc">Term (Category) Grid Block</a></li>
<li><a href="https://mediaron.com/custom-query-blocks/featured-posts-by-category-block/" rel="nofollow ugc">Featured Posts by Category Block</a></li>
</ul>
<h3>Post Type Archive Mapping</h3>
<p>This plugin allows you to map your custom post type archive pages. Just create a page and go to Settings->Reading to set the page for your archive.</p>
<p>Ensure your post types have <code>has_archive</code> set to true.</p>
<ul>
<li>Select a Public page to use as your post type archive page.</li>
<li>View the archive and you will see the page content instead of the archive content.</li>
<li>Use page templates on your pages for flexibility.</li>
<li>Custom Gutenberg block for showing your posts.</li>
</ul>
<h3>Term Archive Mapping</h3>
<p>This plugin also allows you to map your term archives to a page. Just create a page and go edit your term to set the archive page.</p>
<ul>
<li>Create a public page to use as your term archive.</li>
<li>Visit the edit term page and select the page.</li>
<li>View the term and you will see your selected page.</li>
<li>Use Gutenberg on your public page to customize the archive.</li>
</ul>
<h3>404 Page Mapping</h3>
<p>This plugin allows you to map a page to your 404 template, so you can customize a 404 page as needed.</p>
<h3>Development is on GitHub</h3>
<p><a href="https://github.com/MediaRon/post-type-archive-mapping" rel="nofollow ugc">Development is on GitHub</a></p>
<h3>Archive Pages Pro</h3>
<p>Archive Pages Pro has all the mapping feature of this plugin and more. You can map post types, terms, authors, and more to pages. <a href="https://dlxplugins.com/plugins/archive-pages-pro/" rel="nofollow ugc">Learn more about Archive Pages Pro</a></p>


Custom Query Blocks

I installed this plugin to run and output custom queries with the Gutenberg block. That aspect of the plugin is beyond fantastic.

However, the mapping feature doesn't make sense (to me) to include.. it seems like it ought to be its own separate plugin.

On top of that, there was no way to disable the mapping functionality and it automatically broke all of my archives. Despite having all options for mapping set to 'default' my archives would either throw a 404 or return a page outputting ALL post, page and CPT content.

I have no reason to create custom archives and the original reason I installed the plugin doesn't offer enough value to justify the added work of creating and mapping archive pages.

Mapping "feature" compromises the usefulness of the whole plugin

I get it, it started as a custom Archive page mapping plugin. And it needed a custom query block to be useful in the block editor era.

But the custom query block is useful on its own, and it's really hard to find. A so useful feature for the block editor should be top priority.

Not sure how you could make it work, but both features should be detached.

Thanks for sharing your work.

Alternatives to Custom Query Blocks

Top alternatives