ASSINATURA DO WORDPRESS

Integrações de assinatura do WordPress para REEID Translate

Explore a compatibilidade documentada com plugins de assinatura do WordPress, preservando funções, permissões, planos e regras de acesso.

COMPATIBILIDADE DE ASSINATURA

Navegue pelas integrações de assinatura do WordPress.

Encontre guias de compatibilidade publicados para plugins de assinatura e suporte a registro, conta e conteúdo multilíngue voltado ao membro.

Visibility Controls for Editor Blocks

Visibility Controls for Editor Blocks — Adds native visibility settings in the WordPress block editor sidebar for Gutenberg blocks, allowing blocks to be hidden or shown based on device type (mobile/tablet/desktop).

WordPress.org

Webvriend – Custom login screen

Webvriend – Custom login screen — {"task": "Research factual plugin behavior for compatibility context only. Do not extract translation-surface observations.", "plugin_identity": {"name": "Webvriend – Custom login screen", "slug": "webvriend-wp-login", "homepage_url": "https://www.webvriend.nl/", "plugin_url": "https://www.webvriend.nl/"}, "official_search_domains": ["webvriend.nl", "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 only when supplied evidence is insufficient.", "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 plugin behavior, capabilities, settings, or integrations.", "Do not decide REEID compatibility, translation support, approval, or eligibility.", "Follow category_research.rules for what to investigate in this Integration Category.", "Return observations as an empty list.", "Return 4 to 8 concise high-value factual capabilities in features.", "Group related implementation details into broader capability statements.", "Prefer stable product capabilities over minor settings or repeated variations.", "Do not include ratings, installation counts, version requirements, or promotional claims.", "Use unknowns only for materially relevant facts that official evidence does not establish.", "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": "Membership", "mode": "compatibility_only", "rules": ["Research factual membership-plugin behavior relevant to compatibility, including protected content, member areas, access rules, and account-facing rendering.", "This Integration Category is compatibility-only.", "Do not research, infer, or emit translation-surface observations.", "Return observations as an empty list.", "Use features and unknowns only for factual compatibility context."], "evidence_focus": {"integration_category": "Membership", "look_for_literal_terms": []}, "output_schema": {"observations": [{"text": "", "evidence": "", "source_url": ""}], "features": [], "unknowns": [], "seo_display_name": "", "seo_keyword_candidates": []}, "evidence": {"description": "In this plugin we build a custom WordPress login screen.", "readme_text": "=== Webvriend - Custom login screen ===\nContributors: Webvriend\nRequires at Least: 6.0.0\nTested up to: 7.0\nTags: webvriend\nStable tag: 2.2.0\nLicense: GPLv2 or later\nLicense URI:http://www.gnu.org/licenses/gpl-3.0.html\n\nIn this plugin we build a custom WordPress login screen\n\n== Description ==\n\nIn this plugin we build a custom WordPress login screen."}}}

Product website WordPress.org

WP Frontend Delete Account

WP Frontend Delete Account — Provides a frontend account-deletion flow for WooCommerce customers from the My Account area, with a Delete Account tab created automatically.

WordPress.org
Shopping Cart
Scroll to Top