Armandi Content Sync
| 开发者 | acaballerop |
|---|---|
| 更新时间 | 2026年5月26日 04:12 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Armandi Content Sync helps administrators import content from another WordPress installation in a controlled and secure way.
You can work with two import methods:
- REST API import, started manually or scheduled with WP-Cron.
- Classic XML import using a standard WordPress WXR export file.
- Manual REST API import.
- Classic XML WXR import.
- Classic XML import from a local server path for large files that cannot be uploaded through the browser.
- Dry run mode for REST API and XML imports.
- Pause, resume, and cancel controls for active imports.
- Scheduled REST API imports with a fixed execution time and a repeat frequency of daily, every 7 days, every 15 days, or monthly.
- Import of categories, tags, featured images, inline images, authors, and SEO metadata.
- Fallback local author assignment when the source site does not expose author details.
- Per-run logs with CSV export.
- Blocked media host reporting for failed image imports.
- Optional allowlist for trusted external media hosts such as source CDNs.
- Optional Visual Composer/WPBakery content normalization for cleaner imported HTML.
- Optional authentication with WordPress Application Passwords when anonymous REST access is restricted.
- REST API overview in the manual import screen showing the active authentication mode and primary endpoint.
- By default, remote images are downloaded only from the configured source host or its subdomains.
- If the source site uses a CDN or a separate image host, an administrator can explicitly allow those hosts.
- Blocked media hosts are listed in the import logs so administrators can review them before allowing any additional hosts.
安装:
- Upload the
armandi-content-syncfolder to the/wp-content/plugins/directory, or install the plugin through the WordPress admin. - Activate the plugin through the
Pluginsscreen in WordPress. - Open the plugin settings page from the WordPress admin menu.
- Enter the base URL of the source WordPress site.
- If the source REST API is restricted, configure an Application Password with a valid user account from the source site.
- Adjust the import options to match your workflow.
- Open the manual import page and run a dry run or a full import.
- For very large XML files, copy the WXR file to the recommended uploads subdirectory and use the local server path import option instead of a browser upload.
屏幕截图:
常见问题:
What is the difference between REST API import and XML import?
REST API import fetches content directly from the configured source WordPress site. XML import works from a previously exported WordPress WXR file.
Large XML files can also be imported from a local server path when the hosting environment rejects browser uploads with errors such as 413 Request Entity Too Large.
Why are authors not always imported?
Some source sites block endpoints such as users through security plugins or custom rules. In those cases, the plugin may not have enough data to resolve the original author and will assign the post to the configured fallback local user.
When should I use an Application Password?
Use it when the source WordPress site restricts anonymous REST API access or blocks some of the endpoints required for a complete import.
How do scheduled imports work?
Scheduled imports run through WP-Cron. You can choose the execution time and the repeat frequency. Available frequencies are:
- Daily
- Every 7 days
- Every 15 days
- Monthly
Why are some images shown as blocked in the logs?
The plugin limits remote media downloads to the source host and to any extra hosts that you explicitly allow. If the source site uses a CDN or a separate media domain, review the blocked hosts in the run detail view and allow only the trusted ones.
Does the plugin depend on external services?
No. The plugin only needs:
- a source WordPress site that can be reached through the REST API, or
- a WordPress WXR export file.
更新日志:
0.1.2
- Added optional Visual Composer/WPBakery content normalization for imported content.
- Improved cleanup of builder shortcodes, classes and attributes while preserving HTML, inline styles and images.
- Tested with WordPress 7.0 and PHP 8.3.27.
- Added WordPress.org plugin listing assets.
- Added Spanish translation support if translation files already exist.
- Improved release metadata.
- Initial public release.
- REST API post import.
- Classic XML WXR import.
- Local server path import option for large XML files.
- Author, taxonomy, image, and SEO metadata import support.
- Dry run support for REST API and XML imports.
- Per-run logging and CSV export.
- Pause, resume, and cancel controls.
- Scheduled imports with fixed execution time and repeat frequency.
- REST API details panel showing authentication mode and primary endpoint.
- Security hardening for remote media and authenticated requests.