
GROVIK PUBLISHER
Grovik Publisher compatibility with REEID Translate
Grovik Publisher compatibility with REEID Translate is being reviewed using official plugin documentation. Registers custom REST API endpoints (/wp-json/grovik/v1/) to allow external service authentication and content publishing without initiating outbound connections from the WordPress site. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Grovik Publisher does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Grovik Publisher is documented in the SEO category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Grovik Publisher compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Registers custom REST API endpoints (/wp-json/grovik/v1/) to allow external service authentication and content publishing without initiating outbound connections from the WordPress site.
- Generates and manages independent API keys for authentication, bypassing WordPress Application Passwords to ensure compatibility with security plugins that may disable core auth features.
- Processes incoming article data including title, body HTML, slug, and featured image URLs, applying wp_kses_post() sanitization before storage to prevent script injection.
- Downloads and imports featured images from external sources into the local WordPress Media Library rather than hotlinking, ensuring assets are stored locally.
- Enables remote management of blog posts (create, update, unpublish, trash) via authenticated API requests, restricted to post types supported by the plugin's endpoints.
- Provides a connection status panel tracking last publish times and total article counts based on local request logs, without making outbound calls during settings display.
TRANSLATION BOUNDARY
Grovik Publisher capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Grovik Publisher and REEID Translate FAQ.
What does Grovik Publisher do?
Grovik Publisher has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Grovik Publisher have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Grovik Publisher?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Grovik Publisher in a multilingual WordPress workflow.
REEID documents Grovik Publisher functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.