WP Manifestindependent plugin directory
manifest / content / acf-move-wp-editor

Advanced Custom Fields: Move WP Editor WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA

This is a simple ACF Field that moves the WordPress content editor of a post or page to the location of this field.

★ 36stars
1.1kcomposer installs
v1.0.1latest · 8 years ago

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/log1x/acf-move-wp-editor/archive/refs/heads/master.zip

On Packagist as log1x/acf-move-wp-editor:

composer require log1x/acf-move-wp-editor
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.

This is a simple ACF Field that moves the WordPress content editor of a post or page to the location of this field.

This can be useful for cleaning up your Edit Post screen with something like ACF tabs:

Example

Installation

Install ACF Move WP Editor using Composer:

$ composer require log1x/acf-move-wp-editor

The filters below remove the TinyMCE editor feature that expands its container to the height of the content as well as removes the option from the Help menu.

/**
 * Unregister the editor expand script.
 *
 * @return void
 */
add_action('admin_init', function () {
    wp_deregister_script('editor-expand');
});

/**
 * Disable TinyMCE's autoresize.
 *
 * @param  array $init
 * @return array
 */
add_filter('tiny_mce_before_init', function ($init) {
    unset($init['wp_autoresize_on']);
    return $init;
});

Releases

2 releases.

Tag
Published
v1.0.1 latest
Sep 28, 2018 8 years ago
Sep 13, 2017 9 years ago

These releases are tags only. The author does not attach a packaged zip, so there are no download counts to report.

A grade

Security

Advanced Custom Fields: Move WP Editor 1.0.0 · audited by WP Registry

No security issues found.

Audited release
1.0.0
Findings
none
Worst severity
—
Content hash
5bc7de7a77d5df58dbc14b26…

WP Registry hashes the installable build and reports on that exact bytes-for-bytes copy. Embargoed findings are withheld until they are disclosed, so a clean verdict means nothing public is outstanding. WP Manifest does not audit code itself.