
BANI HONAR TOOLKIT
Bani Honar Toolkit compatibility with REEID Translate
Bani Honar Toolkit compatibility with REEID Translate is being reviewed using official plugin documentation. Visitor statistics module tracking page views, unique visitors, and online status with detailed breakdowns by country, device type, browser, OS, and referring sources. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Bani Honar Toolkit 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
Bani Honar Toolkit is documented in the Analytics category with 8 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 Bani Honar Toolkit 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
- Visitor statistics module tracking page views, unique visitors, and online status with detailed breakdowns by country, device type, browser, OS, and referring sources.
- Real-time visit logging capturing IP addresses (with optional anonymization), user-agent data, screen size, language, time zone, and internal site search queries.
- Frontend script injection for data collection that operates without setting cookies, using sessionStorage for session identification and ensuring compatibility with page caching plugins.
- Traffic source attribution identifying direct visits, search engines, social networks, messengers, and UTM campaign parameters.
- Administrative controls to block specific IP addresses or ranges temporarily or permanently based on visitor log details.
- Optional external geolocation lookup via ipwho.is or GeoJS when server-side CDN headers do not provide country information, disabled by default.
- Data retention management allowing configurable automatic deletion of old visit records and manual CSV export of analytics data.
- Integration with WordPress privacy tools for exporting and erasing personal data associated with logged-in user visits.
TRANSLATION BOUNDARY
Bani Honar Toolkit 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. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
Bani Honar Toolkit and REEID Translate FAQ.
What does Bani Honar Toolkit do?
Bani Honar Toolkit has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does Bani Honar Toolkit 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 Bani Honar Toolkit?
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 Bani Honar Toolkit in a multilingual WordPress workflow.
REEID documents Bani Honar Toolkit 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.