WP Test and WLWManifest XML
CN → USAI分析
[[WP Test]] and [[WLWManifest XML]] are two distinct but related concepts in the early ecosystem of Windows Live Writer (WLW), a popular desktop blogging client developed by Microsoft. They are often encountered by users migrating blogs or troubleshooting connectivity issues, particularly with platforms like WordPress.
Here is a detailed explanation of both, their functions, and how they relate to the Blogging API.
1. WP Test (WordPress Pingback/Connection Test)
"WP Test" is not a formal technical standard but a common term used to describe the connectivity check performed by blogging clients (like Windows Live Writer, Windows Live Writer Beta, or earlier Live Writer versions) to verify that they can successfully communicate with a WordPress blog.
How It Works
When you add a WordPress blog to Windows Live Writer, the client attempts to locate the blog's Blogging API endpoint. For WordPress, this is typically: * xmlrpc.php (for legacy XML-RPC API) * Or the Blogger API endpoint if enabled.
The "test" involves:
1. Sending a request to the blog’s URL.
2. Looking for the wlwmanifest.xml file (see below).
3. Attempting to authenticate using your username and password (or application passwords in modern WordPress).
4. Retrieving the list of recent posts or categories to confirm access.
Common Errors
- "Cannot connect to the blog": Often caused by:
- WordPress security plugins blocking XML-RPC.
- Incorrect URL (e.g., using
httpinstead ofhttps, or missing the/wp-admin/path if required). - WordPress updating to require Application Passwords or Two-Factor Authentication, which older versions of WLW do not support.
- "WP Test" in forums: Users often post "WP Test failed" meaning their client could not fetch posts or publish.
2. WLWManifest XML
WLWManifest XML is a specialized XML file hosted on a WordPress site (usually at the root, e.g., yoursite.com/wlwmanifest.xml) that provides metadata about the blog to Windows Live Writer and other blogging clients that support the Windows Live Writer Manifest format.
Purpose
It acts as a configuration file that tells the blogging client: * The title of the blog. * The URLs for various APIs (Blogger, Movable Type, MetaWeblog, WordPress XML-RPC). * The blog ID (important for multi-user blogs). * Optional features like whether thumbnail support is enabled.
Typical Structure
xml
Key Elements Explained
<clientType>: Specifies which API the client should use (e.g.,MetaWeblog,Blogger).<api>/<url>: The direct endpoint for the XML-RPC service (usuallyxmlrpc.phpin WordPress).<supportsImageTags>: Iftrue, WLW can insert images directly into posts.<supportsCategories>/<supportsPostTags>: Enables WLW to manage categories and tags.
Relationship Between WP Test and WLWManifest XML
- Discovery Phase: When you add a WordPress blog in Windows Live Writer, the client first fetches
wlwmanifest.xmlfrom the root of your site. - Validation: The presence and correctness of
wlwmanifest.xmlconfirm that the blog is WLW-compatible. - Connection Test: After parsing the manifest, WLW uses the URLs provided in the XML to attempt a live connection (the "WP Test") to verify authentication and permissions.
If wlwmanifest.xml is missing or misconfigured, the "WP Test" will fail because WLW won’t know where to send the API requests.
Common Issues & Fixes
| Issue | Cause | Solution |
|---|---|---|
| "WLWManifest not found" | The file is missing from the blog root. | Use a plugin like WLW Manifest for WordPress to generate it, or manually upload it to your site root. |
| "Authentication Failed" | WordPress 5.2+ requires Application Passwords for XML-RPC if 2FA is on. | In WLW, you must use an Application Password (generated in WP Admin > Users > Profile) instead of your regular login password. |
| "XML-RPC Disabled" | Security plugins (e.g., Wordfence, Jetpack) block XML-RPC. | Whitelist xmlrpc.php in your security plugin or disable XML-RPC blocking for trusted IPs. |
| SSL/HTTPS Mismatch | WLW does not handle self-signed or expired SSL certificates well. | Ensure your blog has a valid SSL certificate. Some older WLW versions require manual trust certificate installation. |
Modern Context
- Windows Live Writer is discontinued: Microsoft stopped supporting WLW in 2017. However, many users still use it due to its simplicity.
- WordPress Changes: Modern WordPress (5.2+) deprecates basic authentication over XML-RPC for users with 2FA enabled. You must use Application Passwords.
- Alternatives: If you’re experiencing issues with WLW and
wlwmanifest.xml, consider switching to:- WordPress Block Editor (Gutenberg) with REST API.
- Thrive Editor or Elementor (if using page building).
- Other Blogging Clients: Like BlogJet or Writefull, which may have better modern API support.
Summary
- WP Test: The process of verifying connectivity between a blogging client and a WordPress blog.
- WLWManifest XML: A configuration file that tells Windows Live Writer how to connect to the blog, including API endpoints and features.
- Fixing Issues: Ensure
wlwmanifest.xmlis present, XML-RPC is enabled, and you’re using Application Passwords for authentication in modern WordPress setups.
If you’re troubleshooting a specific error, please provide the exact error message from Windows Live Writer for more targeted advice.
用户评价
关于 HS 编码归类
协调制度(HS)是由世界海关组织(WCO)制定的国际贸易商品分类标准。全球 200 多个国家采用 HS 系统作为海关关税、贸易统计和进出口监管的基础。
每个 HS 编码遵循以下层级结构:
- 章(2 位)——商品大类(例如:第 84 章:机器和机械设备)
- 品目(4 位)——章内的更具体分类
- 子目(6 位)——国际通用细分,所有 WCO 成员国统一使用
- 本国细分(8-10 位)——各国自行扩展的细分编码,如美国 HTSUS 10 位编码
正确的 HS 编码归类对于顺利通关、准确缴纳关税和遵守贸易法规至关重要。错误归类可能导致海关延误、多缴关税或罚款。
从CN进口到US时,适用的关税税率可能包括:
- 最惠国(MFN)税率——适用于 WTO 成员国的标准关税税率
- 普通税率——适用于无贸易协定国家
- 贸易救济关税——附加关税,如 301 条款(反倾销)、232 条款(国家安全)或反补贴税
本页内容仅供参考。如需正式归类,请咨询当地海关或持牌报关代理。