Linux 软件免费装
Banner图

Eizport

开发者 eizport
camaleaun
更新时间 2026年10月15日 03:50
捐献地址: 去捐款
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

migration media export import wxr

下载

1.0.1

详情介绍:

Eizport gives Tools → Export a new screen, built like WordPress's newest admin screens, and extends the WordPress Importer. Prefer WordPress's Export screen untouched? One setting moves the new one to its own Tools item; another brings back the classic Export screen with the same choices added. The Export screen Built with DataViews and DataForm, it runs on the plugin's abilities: On Tools → Import → WordPress On the classic Tools → Export Bundle options Settings, from the plugin's row in Plugins (built with DataViews and DataForm) On the WordPress Importer Upload a .wxrz (or .zip) bundle like any WXR file. Its attachment files are taken from the bundle, so nothing is downloaded from the old site, which doesn't even need to be online. Attachments, image sizes and featured images are created by the importer as usual. Content files are put back into the WXR before the import starts. Gzipped WXR files (.xml.gz) are accepted too. The .wxrz format A .wxrz file is a gzipped tar archive: You can open it with any tool that reads .tar.gz files. With Settings → Export → "Bundle as .zip", bundles are plain .zip files with the same entries, which any computer opens. Abilities The same export and import, for AI agents and scripts, through the WordPress Abilities API (/wp-json/wp-abilities/v1/abilities/<name>/run, and as tools with the MCP adapter): They follow the same rules as the screens: the export capability for exporting and copies, import for importing. Only one export runs per request. For developers

安装:

  1. Install and activate Eizport. Exporting works right away, from Tools → Export.
  2. To import, install the WordPress Importer: on Tools → Import, click "Install Now" under WordPress (the plugin's links lead there while it isn't installed), then "Run Importer".

屏幕截图:

  • Pick the exact items to export; the homepage, shop and checkout wear badges.
  • Settings travel too: the ones your pages point to are suggested; add any other one by one.
  • Export a WordPress Playground .zip with the theme and plugins you choose.
  • Set it once: media, linked settings, .zip bundles and saved defaults.
  • Every export is kept as a private copy for a while: download it again, open it in Playground or import it.

升级注意事项:

1.0.1 Fixes "As plugin: allow importing again", which wasn't saved, and documents the external services the plugin uses. 1.0.0 Initial release.

常见问题:

Is it safe to import a bundle from someone else?

Only import files you trust, as with any WXR file. When a bundle is opened, only the files its manifest lists are written, only under a private folder, only with file types WordPress allows to be uploaded (never PHP), and never outside that folder. The folder is deleted when the import ends or is abandoned.

Which plugins are supported?

WooCommerce, with its own support: products, orders and coupons, its pages as linked settings, product galleries, the products its blocks show (suggested) and product reviews. Advanced Custom Fields and Elementor aren't officially supported yet and weren't tested: their data travels in custom fields, which the export carries, but IDs inside them aren't remapped on import. The docs explain what to expect: https://eizport.github.io/docs/developers/compatibilities/

What is an "as plugin" file?

A plugin .zip that holds the bundle. Install it on the other site (Plugins → Add Plugin → Upload Plugin) and open its screen under Tools: it checks that Eizport and the WordPress Importer are there, imports the bundle with one click, and then offers to delete itself.

Is there a size limit?

Uploads are limited by your server's PHP settings (upload_max_filesize and post_max_size), which apply to the compressed file. A bundle may expand to 512 MB by default; developers can change it with the eizport_wxrz_max_bytes filter.

Does it send data anywhere?

Not to its authors: Eizport has no service of its own. It uses WordPress.org's plugin and theme information and downloads, as WordPress does, and opens WordPress Playground only when you click to; see "External services" for what is sent and when. When importing a bundle, the importer's attachment downloads are answered from the bundle on your own server.

What does the Playground blueprint do?

It installs the plugins and themes in the .zip and imports the WXR with Playground's own importer. With media or content files, they are written into Playground first and a temporary must-use plugin answers the importer's downloads from the media files and puts each .html file into its post, and a second one sets the settings when the import ends, with their IDs mapped; all of it is removed after the import. The WordPress Importer is installed by Playground itself, from WordPress.org.

Who can download a Playground copy?

Anyone with its link: the file name ends in a random 16-character token, so it can't be guessed, and it is served only until it expires (a day by default; see the plugin's Settings, where it can also be "until deleted"), then deleted. On a site on your computer (like localhost), the link only works in your own browser. Don't keep copies of content that must stay private.

Where are the files kept?

In wp-content/uploads/eizport/tmp/: Playground copies, and the folders of bundles being imported. Everything there is temporary, and the tmp folder itself is deleted once it is empty. Uninstalling the plugin deletes uploads/eizport/ and the plugin's settings.

Where is the source code?

The PHP is in the plugin, readable. The Export and Settings screens' JavaScript in build/ is compiled; each file ships next to its unminified version, and its source (TypeScript, in routes/ and src/) is at https://github.com/eizport/eizport — build it with npm ci && npm run build (@wordpress/build).

更新日志:

1.0.1 1.0.0