GLOTPRESS NOTIFY
GlotPress Notify compatibility with REEID Translate
GlotPress Notify compatibility with REEID Translate is being evaluated from available plugin evidence. Integrates with a GlotPress installation by reading GlotPress tables from the same database as the WordPress instance it runs on. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for GlotPress Notify.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
GlotPress Notify is documented in the Other category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How GlotPress Notify compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Integrates with a GlotPress installation by reading GlotPress tables from the same database as the WordPress instance it runs on.
- Provides an admin-facing listing of GlotPress projects and languages that have translation strings awaiting review/approval.
- Supports subscribing to email notifications for individual GlotPress projects.
- Sends notification emails to users (including admins/validators/translators) who are able to view strings awaiting approval and have subscription settings.
- Requires configuration of the GlotPress table prefix and a sender email address via the plugin’s Settings page in the WordPress admin.
- Allows customization of the email template by copying the plugin’s template from its templates folder into the active theme under `plugins/glotpress-notify`.
- Does not support managing multiple GlotPress installations (explicitly stated as “Not yet”).
CONTENT BOUNDARY
GlotPress Notify capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
GlotPress Notify and REEID Translate FAQ.
What does GlotPress Notify do according to the available plugin evidence?
GlotPress Notify has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for GlotPress Notify?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for GlotPress Notify?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate GlotPress Notify in a multilingual WordPress workflow.
REEID documents GlotPress Notify functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.