=== Classic Editor ===
Contributors: wordpressdotorg, azaozz, melchoyce, chanthaboune, alexislloyd, pento, youknowriad, desrosj, luciano-croce
Tags: gutenberg, disable, disable gutenberg, editor, classic editor, block editor
Requires at least: 4.9
Tested up to: 6.2
Stable tag: 1.6.3
Requires PHP: 5.2.4
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Enables the previous "classic" editor and the old-style Edit Post screen with TinyMCE, Meta Boxes, etc. Supports all plugins that extend this screen.
== Description ==
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.
Classic Editor is an official WordPress plugin, and will be fully supported and maintained until 2024, or as long as is necessary.
At a glance, this plugin adds the following:
* Administrators can select the default editor for all users.
* Administrators can allow users to change their default editor.
* When allowed, the users can choose which editor to use for each post.
* 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.
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.
By default, this plugin hides all functionality available in the new block editor ("Gutenberg").
== Changelog ==
= 1.6.3 =
* Added some WPCS fixes, props NicktheGeek on GitHub.
* Updated "Tested up to" in the readme and removed it from classic-editor.php. This should fix false positive errors in security plugins in the future.
= 1.6.2 =
* Fixed bug that was preventing saving of the last used editor.
= 1.6.1 =
* Fixed a warning on the block editor based widgets screen.
* Fixed use of a deprecated filter.
= 1.6 =
* Updated for WordPress 5.5.
* Fixed minor issues with calling deprecated functions, needlessly registering uninstall hook, and capitalization of some strings.
= 1.5 =
* Updated for WordPress 5.2 and Gutenberg 5.3.
* Enhanced and fixed the "open posts in the last editor used to edit them" logic.
* Fixed adding post state so it can easily be accessed from other plugins.
= 1.4 =
* On network installations removed the restriction for only network activation.
* Added support for network administrators to choose the default network-wide editor.
* Fixed the settings link in the warning on network About screen.
* Properly added the "Switch to classic editor" menu item to the block editor menu.
= 1.3 =
* Fixed removal of the "Try Gutenberg" dashboard widget.
* Fixed condition for displaying of the after upgrade notice on the "What's New" screen. Shown when the classic editor is selected and users cannot switch editors.
= 1.2 =
* Fixed switching editors from the Add New (post) screen before a draft post is saved.
* Fixed typo that was appending the edit URL to the `classic-editor` query var.
* Changed detecting of WordPress 5.0 to not use version check. Fixes a bug when testing 5.1-alpha.
* Changed the default value of the option to allow users to switch editors to false.
* Added disabling of the Gutenberg plugin and lowered the required WordPress version to 4.9.
* Added `classic_editor_network_default_settings` filter.
= 1.1 =
Fixed a bug where it may attempt to load the block editor for post types that do not support editor when users are allowed to switch editors.
= 1.0 =
* Updated for WordPress 5.0.
* Changed all "Gutenberg" names/references to "block editor".
* Refreshed the settings UI.
* Removed disabling of the Gutenberg plugin. This was added for testing in WordPress 4.9. Users who want to continue following the development of Gutenberg in WordPress 5.0 and beyond will not need another plugin to disable it.
* Added support for per-user settings of default editor.
* Added support for admins to set the default editor for the site.
* Added support for admins to allow users to change their default editor.
* Added support for network admins to prevent site admins from changing the default settings.
* Added support to store the last editor used for each post and open it next time. Enabled when users can choose default editor.
* Added "post editor state" in the listing of posts on the Posts screen. Shows the editor that will be opened for the post. Enabled when users can choose default editor.
* Added `classic_editor_enabled_editors_for_post` and `classic_editor_enabled_editors_for_post_type` filters. Can be used by other plugins to control or override the editor used for a particular post of post type.
* Added `classic_editor_plugin_settings` filter. Can be used by other plugins to override the settings and disable the settings UI.
= 0.5 =
* Updated for Gutenberg 4.1 and WordPress 5.0-beta1.
* Removed some functionality that now exists in Gutenberg.
* Fixed redirecting back to the classic editor after looking at post revisions.
= 0.4 =
* Fixed removing of the "Try Gutenberg" call-out when the Gutenberg plugin is not activated.
* Fixed to always show the settings and the settings link in the plugins list table.
* Updated the readme text.
= 0.3 =
* Updated the option from a checkbox to couple of radio buttons, seems clearer. Thanks to @designsimply for the label text suggestions.
* Some general updates and cleanup.
= 0.2 =
* Update for Gutenberg 1.9.
* Remove warning and automatic deactivation when Gutenberg is not active.
= 0.1 =
Initial release.
== Frequently Asked Questions ==
= Default settings =
When activated and when using a classic (non-block) theme, this plugin will restore the previous ("classic") WordPress editor and hide the new block editor ("Gutenberg").
These settings can be changed at the Settings => Writing screen.
= Default settings for network installation =
There are two options:
* When network-activated and when using a classic (non-block) theme, this plugin will set the classic editor as default and prevent site administrators and users from changing editors.
The settings can be changed and default network-wide editor can be selected on the Network Settings screen.
* When not network-activated each site administrator will be able to activate the plugin and choose options for their users.
= Cannot find the "Switch to classic editor" link =
It is in the main block editor menu, see this [screenshot](https://ps.w.org/classic-editor/assets/screenshot-7.png?rev=2023480).
= Does this work with full site editing and block themes? =
No, as block themes rely on blocks. [See Block themes article](https://wordpress.org/support/article/block-themes/) for more information.
== Screenshots ==
1. Admin settings on the Settings -> Writing screen.
2. User settings on the Profile screen. Visible when the users are allowed to switch editors.
3. "Action links" to choose alternative editor. Visible when the users are allowed to switch editors.
4. Link to switch to the block editor while editing a post in the classic editor. Visible when the users are allowed to switch editors.
5. Link to switch to the classic editor while editing a post in the block editor. Visible when the users are allowed to switch editors.
6. Network settings to select the default editor for the network and allow site admins to change it.
7. The "Switch to classic editor" link.
Chris (71, single, gay man) remarked, “If I got to the point where my life was not – JNO Construction & Design
At JNO Construction we don’t build houses, we build homes.
Chris (71, single, gay man) remarked, “If I got to the point where my life was not
Similarly, Bill (66, separated, gay man) remarks:
Many participants also reported intentions to age in place and stay in their home as long as possible, not unlike heterosexual individuals (Bell & Menec, 2015; Cicero & Pynoos, 2016). However, their motivations for doing so were distinct, often due to fears of homophobia and heightened financial concerns. Married and partnered participants were more likely to indicate a desire to “age in place,” as it was understood that partners would help provide care. For example, Barbara (66, married, lesbian) noted that partners often provide care, but that the health and age of a partner are crucial in allowing one to age in place. However, due to a general tendency to be childfree, participants noted that friends, a partner, or a hospice care service would also help them age in their home. Roger (70, married, gay man) noted that “we have to rely on each other, whether that be spouses or family of choice.” It was well understood-even sometimes in the absence of conversation about it-that chosen family will provide care in one’s home.
Other participants shone further light on how friends provide unpaid care, which allows older LGB people to age in their own home. Barbara revealed that it is not uncommon for older gays and lesbians to be estranged from the family, which creates a situation where people must rely on friends for care. She noted, “I know many, many cases where the friends … have come together, provided food, provided transportation, been there by the bedside when somebody dies.” Teddy (63, married, bisexual man) echoed this sentiment, reily results in older LGB people turning to friends for care.
However, the ability to age in place may not always be possible, as social isolation (e.g., lack of social networks) leaves some older LGB adults unable to live at home. Consistent with prior literature (Cicero & Pynoos, 2016), participants also acknowledged that their houses would have kissbridesdate.com browse around this web-site to be more accessible to accommodate physical decline and disability to “age in place.” Notably, this approach to care differs from “aging in LGBTQ-friendly communities” insofar as participants wish to live independently in their own homes, rather than in shared residences or long-term care homes. A similarity, however, in both approaches is an embracement of the notion of interdependency and a rejection of heterosexual models of care that typically include a heavy reliance on biological family and children.
Quality Over Quantity of Life
Older LGB people also expressed a strong desire for quality over quantity of life in late adulthood. Participants, specifically, named assisted suicide as one possible method to opt for quality over quantity of life should they no longer be able to provide care for themselves. .. enjoyable … if I got bedridden or something like that I’m ready to go. I don’t want to live like that. I don’t want to live in a bed. I don’t want to live on a machine … I would probably want to end my life myself.” Chris, similar to other participants, later elaborated that he is unable to accept what he perceives as a low quality of life, including an inability to complete basic bodily functions (e.g., eating, mobility).
… I do believe that people should have the right to end their life . You know, I don’t consider myself suicidal, but … people should have the dignity to live their life to the fullest. And when they feel like they have no dignity, I think they should have the right to say, ‘You know, I’d like to have some medication and go to sleep.’ I mean, that’s what I would want.