IITECH GLOBAL LANGUAGE & TIMEZONE
iiTech Global Language & Timezone compatibility with REEID Translate
iiTech Global Language & Timezone compatibility with REEID Translate is being reviewed using official plugin documentation. Provides a unified settings page at Settings → Locale & Timezone to control WordPress locale (site language) and site timezone (using WordPress core options) without modifying WordPress core. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What iiTech Global Language & Timezone 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
iiTech Global Language & Timezone is documented in the Other category with 7 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 iiTech Global Language & Timezone 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
- Provides a unified settings page at Settings → Locale & Timezone to control WordPress locale (site language) and site timezone (using WordPress core options) without modifying WordPress core.
- Implements a frontend language switcher UI (UI only) via a shortcode [wpltm_language_switcher].
- Detects visitor timezone using the browser Intl API and stores the detected timezone in a cookie.
- Supports per-user overrides for language and timezone via user profile preferences; when enabled, admin UI switches using switch_to_locale(), and date/time reflects the user timezone with fallback to site defaults.
- Offers timezone-aware shortcodes, including [wpltm_time datetime="…"] and [wpltm_timezone], for displaying localized date/time information.
- Exposes developer helper functions: wpltm_get_effective_timezone(), wpltm_get_effective_locale(), and wpltm_format_datetime().
- Supports WordPress Multisite with network-level defaults.
TRANSLATION BOUNDARY
iiTech Global Language & Timezone 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
iiTech Global Language & Timezone and REEID Translate FAQ.
What does iiTech Global Language & Timezone do?
iiTech Global Language & Timezone has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does iiTech Global Language & Timezone 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 iiTech Global Language & Timezone?
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 iiTech Global Language & Timezone in a multilingual WordPress workflow.
REEID documents iiTech Global Language & Timezone 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.