| 开发者 | alimuzzamanalim |
|---|---|
| 更新时间 | 2026年8月24日 22:41 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp_set_script_translations integration).clone-post-unsaved-changes folder to the /wp-content/plugins/ directory, or install the plugin through the Plugins screen in WordPress.No. There is nothing to copy until a post has been saved at least once, so the button is hidden on brand-new posts.
Yes, for supported block-editor fields: title, content, excerpt, featured media, discussion settings, sticky state for posts, format, template, parent, menu order, REST taxonomies, and registered REST-visible meta. If another dirty field cannot be copied safely, Save As stops before creating a draft.
Supported public post types must be available through the REST API and use the block editor. Attachments, autosaves, revisions, and trashed posts are not handled by the generic adapter. WooCommerce products require the native WooCommerce adapter and a block-editor integration; product variations and the standard classic Woo product editor remain unsupported. Custom post types that use Elementor require the separate Elementor adapter.
Supported core post fields and registered taxonomies are copied, with current editor changes overlaid. The new draft belongs to the current user, has a fresh slug/guid, and does not inherit the source password, dates, status, or author. Sticky state is copied for posts, subject to WordPress's sticky capability. Featured media is reused by ID. Registered show_in_rest meta keys are copied after capability and operational-key checks; a site developer can narrow the exact set with the clone_post_unsaved_changes_allowed_meta_keys filter. WooCommerce product meta is handled only by WooCommerce's native CRUD adapter. The generic adapter does not directly copy files, attachments, comments, revisions, child records, custom tables, or plugin-owned external data.
Elementor 4.2.3 post/page documents use a separate, version-pinned adapter. Save As mirrors Elementor's persistent-setting defaults, captures the current document container settings and element tree without invoking Elementor's save_builder/autosave request, writes the frozen data to a new draft through Elementor's document API, verifies the draft status, persisted element/settings payload, and CSS generation, and checks that the source post, meta, and taxonomy relationships did not change. Other Elementor versions/document types fail closed. WooCommerce products use WooCommerce's own CRUD duplicate workflow for saved product data; unsaved product-specific fields and the normal classic product editor are not claimed as supported.
Open the editor's ⋮ (Options) menu and choose Save As; that item is always available. Uncheck the "Hide" options in the dialog.