WordPress.org

Andrew Ozz

luciano-croce

Jonathan Desrosiers

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

Toda vez esse plugin me salva, ele é incrível, eu detesto a nova interface!

Esse plugin me salva

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.

btopro

<p>Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here.</p>
<h3>haxtheweb</h3>
<p>Bringing the HAX block editor to ClassicPress & WordPress. <a href="https://haxtheweb.org/" rel="nofollow ugc">HAX</a> is short for headless authoring experience, meaning that it is a block editor that is disconnected from the CMS its used in. HAX recognizes editable blocks by using the <a href="https://www.webcomponents.org/" rel="nofollow ugc">web component standard</a>. HAX provides editing capabilities in a way that attempts to write clean HTML markup the same way an expert end-user could, but without ever touching code! The code is writen in a way that experts and developers can jump in and modify as needed given the semantic nature of webcomponents!</p>
<h3>3rd party dependencies</h3>
<p>While you can host assets locally, the HAX editor defaults to leveraging the Penn State Web components CDN.<br />
You can modify this on the Settings -> Writing page. Additional details on this service:<br />
– Penn State CDN domain https://cdn.webcomponents.psu.edu/ is served from Amazon CloudFront<br />
– You can view assets that are exposed via CDN here https://webcomponents.psu.edu/ in StorybookJS<br />
– Privacy polcies the university adheres to: https://policy.psu.edu/policies/ad53<br />
– The source of HAX and your web components is configurable and you can change it to leverage your own (details below)</p>
<h3>Dependencies</h3>
<ul>
<li>If using WordPress, you’ll need to get the <a href="https://wordpress.org/plugins/classic-editor/" rel="ugc">Classic Editor plugin</a>
<ul>
<li>ClassicPress does not have this dependency</li>
</ul>
</li>
<li>Make sure that your Permalink settings are for pretty links or calls to load data via JSON will fail https://stackoverflow.com/questions/44204307/rest-api-init-event-not-fired</li>
</ul>
<h3>Usage</h3>
<p>This should give you the dependencies you need to get going.<br />
1. Download this plugin and place it in wp-content/plugins/haxtheweb<br />
2. If using WordPress you’ll also need the Classic Editor plugin; and then you’ll have to enable it as the default editor (wp-admin/options-writing.php)<br />
3. Enable the Plugins (wp-admin/plugins.php)<br />
4. Make sure Settings -> Permalinks is set to “Post name”<br />
5. Go to Settings -> Writing and scroll down to change your settings<br />
6. Go to edit or create a new page / post<br />
7. Enjoy HAX’ing the web</p>
<h3>Configuration</h3>
<p>HAX adds options to the Writing Settings page (wp-admin/options-writing.php) to allow for further integrations and customizations though the default settings are fine to get up and started with.</p>
<h3>Note on usage</h3>
<p>The default is to serve the Javascript required for HAX and its web components from a CDN. We default to a Penn State mirror of the required assets so you can get up and running quickly. We recommend that if you choose to go into production with HAX, that you look at doing a build routine locally (outlined below) or leveraging one of the faster CDNs available.</p>
<h3>Hooking up additional “apps” in the “Find” area</h3>
<p>To connect to popular services like YouTube, Flickr, and Vimeo you’ll need an API key. You can find details on how to get these keys as well as where to put them on the Writing Settings (wp-admin/options-writing.php) page.</p>
<h3>Front end Developers</h3>
<p>You may build HAX from source if needed. HAX defaults to use CDNs which will effectively point to<br />
this directory or some mutation of it — https://github.com/elmsln/HAXcms/tree/master/build</p>
<p>If you want to build everything from source, your welcome to use yarn / npm to do so though our<br />
build routine effectively will end in the same net result.  If you want to do custom build routines<br />
such as rollup or webpack and not use our prebuilt copies / split build approaches, then your welcome<br />
to check the box related to not loading front end assets in the settings page in order to tailor<br />
the build to your specific needs.</p>
<h3>Getting dependencies</h3>
<p>You need polymer cli (not polymer but the CLI library) in order to interface with web components in your site. Get polymer cli installed prior to usage of this (and (yarn)[https://yarnpkg.com/lang/en/docs/install/#mac-stable] / an npm client of some kind)<br />
    <code>bash<br />
$ yarn global add polymer-cli</code><br />
Perform this on your computer locally, this doesn’t have to be installed on your server.</p>
<h3>Usage</h3>
<ul>
<li>Find <code>CopyThisStuff</code> directory in <code>/wp-content/plugins/haxtheweb</code>.</li>
<li>create a <code>/wp-content/haxtheweb</code> directory</li>
<li>copy the files from <code>CopyThisStuff</code> into <code>/wp-content/haxtheweb</code></li>
</ul>
<p>Then run the following (from the directory you copied it over to) in order to get dependencies:<br />
    <code>bash<br />
$ yarn install</code><br />
Now run <code>polymer build</code> and you’ll have files in <code>build/</code> which contain everything you’ll need to get wired up to web components in your site. Modifying build.js or package.json can be used in order to get new elements and have them be implemented.</p>
<h3>Shouldn’t I put web components in my theme?</h3>
<p>We don’t think so. While it may seem counter intuitive, the theme layer should be effectively implementing what the site is saying is available. If you think of standard HTML tags are being part of this (p, div, a, etc) then it makes a bit more sense. You don’t want functional HTML components to ONLY be supplied if your theme is there, you want your theme to implement and leverage the components.</p>
<h3>New to web components?</h3>
<p>We built our own tooling to take the guess work out of creating, publishing and testing web components for HAX and other projects. We highly recommend you use this tooling though it’s not required:<br />
– https://open-wc.org – great, simple tooling and open community resource<br />
– https://github.com/elmsln/wcfactory – Build your own web component library<br />
– https://github.com/elmsln/lrnwebcomponents – Our invoking of this tooling to see what a filled out repo looks like</p>


haxtheweb

Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here.

Classic Editor vs haxtheweb