WOOCOMMERCE

WooCommerce | REEID Translate 兼容性

REEID 已对 WooCommerce 与 REEID Translate 进行测试，兼容性已验证。目前尚未确认该集成中任何面向访客的具体内容需进行翻译。

访问 WooCommerce ↗

兼容性已验证

WooCommerce 的兼容性已验证。

该集成已通过 REEID 的兼容性测试。插件的结构、设置及功能均独立于已确认的翻译支持。

兼容性已验证
此集成已由 REEID 测试并验证。

翻译支持
目前尚未确认该集成中任何面向访客的具体内容需进行翻译。

验证详情
兼容性和插件功能的验证结果已单独记录，与已确认的翻译支持分开。

兼容性已验证

如何审核 WooCommerce 的兼容性

01 · 测试集成的兼容性
确认 WooCommerce 和 REEID Translate 能否正确协同工作。

02 · 审核插件行为
确认插件的结构、设置、逻辑以及运行时行为仍处于 WooCommerce 的管控之下。

03 · 确定可翻译内容
识别可能需要翻译的面向访客的具体人类可读内容。

04 · 发布已确认的支持
仅在确认面向访客的具体内容已被识别并验证后，才发布翻译支持。

插件信息

插件的功能

插件功能

  • WooCommerce 是用于 WordPress 的开源电商平台。
  • WooCommerce 提供产品模块，用于自定义产品页面。
  • WooCommerce 支持销售订阅、预约及会员服务。
  • WooCommerce 包含中央仪表板，用于监控店铺运营指标。
  • WooCommerce 支持通过 WooPayments 及 100 多种支付网关进行付款。
  • WooCommerce 提供 REST API 和 Webhook，便于与其他服务集成。

独特功能
模块化的产品模块便于定制，广泛支持包括 WooPayments 在内的多种支付网关，内置运输标签打印及承运商对接，经开发者审核的订阅与会员扩展，强大的 REST API 与自定义钩子，以及覆盖多国语言的庞大全球社区。

动态内容
证据显示存在动态内容，如产品页面、购物车体验及移动端通知，但未提供明确的面向访客的动态文本示例。动态内容的翻译相关性虽合理，但并未详细说明。

SEO与元数据
明确提及 SEO 优势，暗示支持 SEO 元数据的翻译，但证据中未提供具体的 SEO 元数据文本示例。

网址与导航
未提供 URL 或导航文本内容的明确证据；URL 与导航的翻译相关性尚不确定。

表单与商务
该插件支持电商表单，如结账与支付表单，面向访客的内容包括支付方式标签与提示信息。然而，证据中未引用任何具体表单字段标签或提示信息。

翻译边界

兼容性验证并不自动确认每个字段的翻译支持。

WooCommerce 已与 REEID Translate 进行测试，但目前尚未确认该集成中任何面向访客的具体内容需进行翻译。

插件的兼容性与已确认的翻译支持分别记录。

限制与质量保证

验证说明

  • WooCommerce 产品设置页面可能因 ProductsSettingsPageAdapter 中无限制的 get_pages() 调用而导致内存耗尽，尤其在页面数量较多的站点。
  • 该问题已在上游报告，并已由 WooCommerce 开发团队修复：
  • https://github.com/woocommerce/woocommerce/issues/69043

常见问题

WooCommerce 和 REEID Translate 常见问题解答。

REEID Translate 是否能与 WooCommerce 配合使用？

是。REEID 已测试并验证了与 WooCommerce 的兼容性。

哪些 WooCommerce 字段已确认可翻译？

目前尚未确认该集成中任何面向访客的具体内容需进行翻译。

已验证的兼容性对 WooCommerce 意味着什么？

这意味着 REEID 已成功测试了 WooCommerce 与 REEID Translate。具体的翻译支持将在面向访客的内容被识别并验证后另行记录。

相关指南

探索更多兼容性指南。

WOOCOMMERCE 集成

浏览 WooCommerce 的集成方案。

探索已发布的兼容性指南，适用于 WooCommerce 扩展、支付网关及相关插件，这些通常与 REEID Translate 一同使用。

Wcik Pennsylvania Shipping

Wcik Pennsylvania Shipping — {"task": "Research and extract factual plugin content evidence for the specified Integration Category. Do not decide REEID support or compatibility.", "plugin_identity": {"name": "Wcik Pennsylvania Shipping", "slug": "wcik-pennsylvania-shipping", "homepage_url": "http://imran1.com/woo-checkout-pennsylvania-based-surcharge-fee-my-clients-custom-solution/", "plugin_url": "http://imran1.com/woo-checkout-pennsylvania-based-surcharge-fee-my-clients-custom-solution/"}, "official_search_domains": ["imran1.com", "wordpress.org", "plugins.svn.wordpress.org"], "rules": ["Return one JSON object only.", "Use only facts supported by supplied plugin evidence or web research from the allowed official domains.", "Use web search when supplied evidence does not explicitly establish the evidence_focus values.", "For web research, use only first-party vendor/product documentation and WordPress.org sources within official_search_domains.", "Do not use reviews, blogs, forums, aggregators, search snippets, or third-party documentation as evidence.", "Do not invent content surfaces, fields, settings, or behavior.", "Do not decide compatibility, translation support, approval, or eligibility.", "Do not assign canonical surface identifiers or canonical surface types.", "Do not assign translation_candidate or similar decision fields.", "Do not use REEID capability contracts, blueprints, category profiles, or internal rules to infer support.", "Follow category_research.rules for what to investigate in this Integration Category.", "If evidence_focus is supplied, investigate every look_for_literal_terms value independently; do not stop after finding only some of them.", "For every evidence_focus value, search the allowed official sources for explicit supporting documentation before concluding that it is unavailable.", "A translation-category result is incomplete if any evidence_focus value has been neither supported by an observation nor explicitly accounted for in unknowns.", "For each evidence_focus value that remains unsupported after research, add a concise unknowns entry stating that official evidence for that value was not found.", "Evidence focus terms are search hints only. They are not proof that the plugin contains, manages, exposes, or supports those values.", "Never output an evidence focus term as an observation unless supplied evidence or an official source explicitly names that textual value.", "The supplied description, readme, FAQ, installation text, metadata, and documentation are evidence sources only; never treat their own prose as plugin-managed website content.", "Extract only literal evidence for explicitly named website textual values.", "text must be an exact phrase copied from the supporting supplied evidence or official source. Never invent, normalize, rename, summarize, classify, or semantically reinterpret it.", "evidence must be an exact supporting sentence or passage copied from the supplied evidence or official source and must contain or directly establish text.", "For translation-category observations, inspect supplied official evidence first. When the supporting passage exists in supplied evidence, source_url may be empty because provenance is validated against that official corpus. Use web research only when supplied evidence does not establish the value; for web-researched evidence, source_url must be the exact official page URL containing the evidence.", "Do not infer location, ownership, configurability, visibility, translation relevance, canonical type, or support.", "Do not create observations from documentation prose merely because that prose itself contains human-readable text.", "Do not create observations from FAQ copy, installation instructions, privacy notices, plugin metadata, requirements, ratings, marketing copy, or from the mere existence of containers, screens, forms, product pages, carts, dashboards, integrations, APIs, systems, widgets, blocks, or features. Official documentation or feature prose may support an observation only when it explicitly names or quotes the actual website textual value being documented.", "If the evidence does not explicitly name a website textual value, return no observation for it.", "features are for a concise human-readable capability summary, not a documentation inventory.", "Return 4 to 8 high-value factual capabilities that best explain what the plugin does.", "Group related settings and implementation details into broader capability statements instead of listing individual settings.", "Prioritize capabilities that help a prospective user understand the plugin's main functionality, important integrations, and distinctive behavior.", "Prefer stable product capabilities over minor configuration options, UI settings, technical implementation details, or repeated variations of the same capability.", "Do not include ratings, installation counts, version requirements, marketing claims, or promotional language.", "Do not repeat the same capability in different wording.", "Use concise factual sentences suitable for a public integration directory and search indexing.", "features may contain concise factual capabilities directly stated by the evidence, but features are not translation evidence.", "unknowns may record areas where the evidence does not explicitly establish a textual value.", "seo_display_name must be the shortest distinctive search-facing product or brand identity that can be copied exactly as one contiguous phrase from plugin_identity.name. Preserve the exact capitalization, spelling, and punctuation used in plugin_identity.name. Never invent, rename, expand, normalize, lowercase, or substitute the plugin brand. Remove generic leading or trailing descriptors when a shorter distinctive product or brand phrase is present, including terms such as Plugin, WordPress Plugin, Page Builder, Website Builder, WooCommerce, Forms, SEO, Addons, Widgets, Templates, Booking, Membership, or similar category/marketing wording. The distinctive brand may appear at the beginning, middle, or end of plugin_identity.name; for example, a title shaped like generic description – Brand should return Brand when Brand is clearly the product identity. When a short distinctive acronym, product token, or branded abbreviation appears after a separator and clearly identifies the plugin, prefer that exact token over the preceding generic description; for example Database Addon for Contact Form 7 – CFDB7 should return CFDB7. Use plugin_identity.slug only as an identity clue, not as output text unless that exact casing and phrase also appears in plugin_identity.name. If no shorter distinctive product or brand phrase can be selected safely, return the full plugin_identity.name.", "seo_keyword_candidates must contain 2 to 4 concise plugin-specific identity phrases based on seo_display_name, plugin_identity.name, and plugin_identity.slug. When the slug corresponds to a brand or product phrase present in the official name, include that phrase as a candidate. Do not return generic category-only phrases and do not assert REEID compatibility, verification, translation support, or other unsupported state claims."], "category_research": {"integration_category": "WooCommerce", "mode": "translation", "rules": ["Actively research official WooCommerce documentation for individual product text values managed by WooCommerce.", "Prioritize product titles or names, product descriptions including short or long descriptions, and product attributes including names, labels, options, or values.", "A product, product page, product block, catalog, variation, or attribute system is not itself a textual value. Extract an observation only when official evidence explicitly names or quotes the product text-bearing value."]}, "evidence_focus": {"integration_category": "WooCommerce", "look_for_literal_terms": ["product title", "product name", "product description", "long description", "short description", "product attribute", "attribute label", "attribute name", "attribute option", "attribute value", "attribute values", "name of an attribute", "value of an attribute", "values of an attribute", "values of the attributes"]}, "output_schema": {"observations": [{"text": "", "evidence": "", "source_url": ""}], "features": [], "unknowns": [], "seo_display_name": "", "seo_keyword_candidates": []}, "evidence": {"description": "WooCommerce Plugin that adds checkout fields and surcharge for shipping to pennsylvania state. A Custom solution for one of my client, On checkout page when you will choose billing or shipping state to pennsylvania, the additional fields will be displayed and he surcharge fee will be added to the order totals.\n Minimum Requirements\n WooCommerce 7.0 or greater\n WordPress 6.5 or greater\n PHP version 8.2 or greater (PHP 8.1 or greater is recommended)\n MySQL version 5.6 or greater (MySQL 5.6 is recommended)\n Automatic installation\n Log in to your WordPress dashboard\n Navigate to the Plugins menu and click Add New.\n Search and locate ‘Wcik Pennsylvania Shipping’.\n Click ‘Install Now’\n Manual installation\n The manual installation method involves downloading Wcik Pennsylvania Shipping’ plugin and uploading it to your webserver via FTP application. You may find more\n instructions on how to do this here (https://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation).", "sections": {"faq": "Can I go back to WooCommerce default settings at a later point?\n Yes. you can uninstall the plugin at any stage.", "readme_text": "===Wcik Pennsylvania Shipping===\nContributors: awanhrp\nlink: https://codeinform.com \nTags: WooCommere Pennsylvania Shipping checkout fields and surcharge\nRequires at least: 6.0 \nTested up to: 6.8.0\nRequires PHP: 8.2 \nStable tag: 1.4.0\nLicense: GPLv2 or later \nLicense URI: http://www.gnu.org/licenses/gpl-2.0.htmlWcik\n\n== Description ==\nWooCommerce Plugin that adds checkout fields and surcharge for shipping to pennsylvania state. A Custom solution for one of my client, On checkout page when you will choose billing or shipping state to pennsylvania, the additional fields will be displayed and he surcharge fee will be added to the order totals.\n\n= Minimum Requirements =\n* WooCommerce 7.0 or greater\n* WordPress 6.5 or greater\n* PHP version 8.2 or greater (PHP 8.1 or greater is recommended)\n* MySQL version 5.6 or greater (MySQL 5.6 is recommended)\n\n= Automatic installation =\n1. Log in to your WordPress dashboard\n2. Navigate to the Plugins menu and click Add New.\n3. Search and locate 'Wcik Pennsylvania Shipping'.\n4. Click 'Install Now'\n\n= Manual installation =\nThe manual installation method involves downloading Wcik Pennsylvania Shipping' plugin and uploading it to your webserver via FTP application. You may find more \n\ninstructions on how to do this here (http://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation).\n\n== Frequently Asked Questions ==\n= Can I go back to WooCommerce default settings at a later point? =\nYes. you can uninstall the plugin at any stage. \n\n== Screenshots ==\n1. Manufacturers\n\n== Change log ==\n= 1.0.0 =\n* First Release\n* WooCommerce Plugin that adds checkout fields and surcharge for shipping to pennsylvania state"}}}

Product website WordPress.org

已验证的集成

使用 WooCommerce 时，应确保其具备已验证的多语言兼容性。

REEID 已验证了 WooCommerce 与 REEID Translate 之间的兼容性。具体的翻译支持将在确认后另行记录。

已确认的翻译字段将在其内容被识别并验证后予以列出。

探索 REEID Translate
浏览集成
Shopping Cart
Scroll to Top