thingsym

<p>Custom Post Type Widgets for the Block Editor (Gutenberg).<br />
This WordPress plugin adds default Custom Post Type Widgets to the Block Editor.</p>
<p>You can filter by registered Custom Post Type or Taxonomy on the Block Editor.</p>
<h4>Compatibility</h4>
<ul>
<li>WordPress version 5.8 or later</li>
<li>Gutenberg version 10.7 or later</li>
</ul>
<h4>Descriptions of Widget Blocks</h4>
<h4>Latest Posts (Custom Post Type)</h4>
<p>display a list of your most recent custom posts.</p>
<h4>Archives (Custom Post Type)</h4>
<p>display a monthly archive of your custom posts.</p>
<h4>Categories (Custom Post Type)</h4>
<p>display a list of categories that has custom posts.</p>
<h4>Calendar (Custom Post Type)</h4>
<p>display a calendar of your site’s posts.</p>
<h4>Latest Comments (Custom Post Type)</h4>
<p>display a list of your most recent comments.</p>
<h4>Tag Cloud (Custom Post Type)</h4>
<p>display a list of the your most used tags in a tag cloud.</p>
<h4>Search (Custom Post Type)</h4>
<p>A search form for your site.</p>
<h4>Hooks</h4>
<p>Custom Post Type Widgets has its own hooks. See the reference for details.</p>
<p>Reference: <a href="https://github.com/thingsym/custom-post-type-widgets#hooks" rel="nofollow ugc">https://github.com/thingsym/custom-post-type-widget-blocks#hooks</a></p>
<h4>Support</h4>
<p>If you have any trouble, you can use the forums or report bugs.</p>
<ul>
<li>Forum: <a href="https://wordpress.org/support/plugin/custom-post-type-widget-blocks/" rel="ugc">https://wordpress.org/support/plugin/custom-post-type-widget-blocks/</a></li>
<li>Issues: <a href="https://github.com/thingsym/custom-post-type-widget-blocks/issues" rel="nofollow ugc">https://github.com/thingsym/custom-post-type-widget-blocks/issues</a></li>
</ul>
<h4>Contribution</h4>
<p>Small patches and bug reports can be submitted a issue tracker in Github. Forking on Github is another good way. You can send a pull request.</p>
<p>Translating a plugin takes a lot of time, effort, and patience. I really appreciate the hard work from these contributors.</p>
<p>If you have created or updated your own language pack, you can send gettext PO and MO files to author. I can bundle it into plugin.</p>
<ul>
<li><a href="https://github.com/thingsym/custom-post-type-widget-blocks" rel="nofollow ugc">VCS – GitHub</a></li>
<li><a href="https://wordpress.org/plugins/custom-post-type-widget-blocks/" rel="ugc">Homepage – WordPress Plugin</a></li>
<li><a href="https://translate.wordpress.org/projects/wp-plugins/custom-post-type-widget-blocks" rel="nofollow ugc">Translate Custom Post Type Widget Blocks into your language.</a></li>
</ul>
<p>You can also contribute by answering issues on the forums.</p>
<ul>
<li>Forum: <a href="https://wordpress.org/support/plugin/custom-post-type-widget-blocks/" rel="ugc">https://wordpress.org/support/plugin/custom-post-type-widget-blocks/</a></li>
<li>Issues: <a href="https://github.com/thingsym/custom-post-type-widget-blocks/issues" rel="nofollow ugc">https://github.com/thingsym/custom-post-type-widget-blocks/issues</a></li>
</ul>
<h4>Patches and Bug Fixes</h4>
<p>Forking on Github is another good way. You can send a pull request.</p>
<ol>
<li>Fork <a href="https://github.com/thingsym/custom-post-type-widget-blocks" rel="nofollow ugc">Custom Post Type Widget Blocks</a> from GitHub repository</li>
<li>Create a feature branch: git checkout -b my-new-feature</li>
<li>Commit your changes: git commit -am ‘Add some feature’</li>
<li>Push to the branch: git push origin my-new-feature</li>
<li>Create new Pull Request</li>
</ol>
<h4>Contribute guidlines</h4>
<p>If you would like to contribute, here are some notes and guidlines.</p>
<ul>
<li>All development happens on the <strong>develop</strong> branch, so it is always the most up-to-date</li>
<li>The <strong>master</strong> branch only contains tagged releases</li>
<li>If you are going to be submitting a pull request, please submit your pull request to the <strong>develop</strong> branch</li>
<li>See about <a href="https://help.github.com/articles/fork-a-repo/" rel="nofollow ugc">forking</a> and <a href="https://help.github.com/articles/using-pull-requests/" rel="nofollow ugc">pull requests</a></li>
</ul>
<h4>Test Matrix</h4>
<p>For operation compatibility between PHP version and WordPress version, see below <a href="https://github.com/thingsym/custom-post-type-widget-blocks/actions" rel="nofollow ugc">Github Actions</a>.</p>


Custom Post Type Widget Blocks

Custom Post Type Widgets for the Block Editor (Gutenberg). This WordPress plugin adds default Custom Post Type Widgets to the Block Editor.

WordPress.org

Andrew Ozz

Jonathan Desrosiers

luciano-croce

Mel Choyce-Dwan

Gary Pendergast

Riad Benguella

Brian Alexander

Josepha

Alexis Lloyd

<p>Classic Editor is an official plugin maintained by the WordPress team that restores the previous (“classic”) WordPress editor and the “Edit Post” screen. It makes it possible to use plugins that extend that screen, add old-style meta boxes, or otherwise depend on the previous editor.</p>
<p>Classic Editor is an official WordPress plugin, and will be fully supported and maintained until 2024, or as long as is necessary.</p>
<p>At a glance, this plugin adds the following:</p>
<ul>
<li>Administrators can select the default editor for all users.</li>
<li>Administrators can allow users to change their default editor.</li>
<li>When allowed, the users can choose which editor to use for each post.</li>
<li>Each post opens in the last editor used regardless of who edited it last. This is important for maintaining a consistent experience when editing content.</li>
</ul>
<p>In addition, the Classic Editor plugin includes several filters that let other plugins control the settings, and the editor choice per post and per post type.</p>
<p>By default, this plugin hides all functionality available in the new block editor (“Gutenberg”).</p>


Classic Editor

Great plugin

This is the first plugin I install on any new website. I wish this was an option built into WordPress, as I feel like it's essential to be able to manage content using a WYSIWYG editor. 

My top plugin

This plugin is not compatible with the latest releases of WordPress. I really liked the feature for being able to switch between classic and gutenberg editing - it was perfect for migrating sites to gutenberg.

Not compatible with WP6


I wish this was installed automatically instead of hello dolly!


I wish this was standard

No comments


I know the block editor is a major effort, but I still find it gets in my way more than it helps. For me, enabling the Classic Editor is a necessity.


One of my must-have plugins


Thanks for this!!! This makes my life easier!


LOVE IT

My favorite Editor.


I really thankful wordpress team for their work but gutenberg is a wrong turn in wordpress history.


Best plugin ever


Must have plugin. Simple, fast and easy to use.


no block no pain :)


Simple understandable and really better than blocks at this time, maybe in the future I move to blocks but currently I'm using classic mode. 


Good

Love it


Classic Editor is simple, fast, and reliable. It keeps the editing experience clean without unnecessary distractions. I appreciate how stable it is even with the latest WordPress versions. A must-have plugin for those who prefer the traditional way of editing content.


Still the Most Reliable Editor

Enables the previous "classic" editor and the old-style Edit Post screen with TinyMCE, Meta Boxes, etc. Supports all plugins that extend this screen.

Custom Post Type Widget Blocks vs Classic Editor