LDAP STAFF DIRECTORY
LDAP Staff Directory compatibility with REEID Translate
LDAP Staff Directory compatibility with REEID Translate is being evaluated from available plugin evidence. LDAP/LDAPS connection to an LDAP server (including Active Directory/OpenLDAP/Samba) with scheme selection and configurable connection parameters such as Base OU and Bind DN No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for LDAP Staff Directory.
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
LDAP Staff Directory is documented in the Other category with 8 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 LDAP Staff Directory 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
- LDAP/LDAPS connection to an LDAP server (including Active Directory/OpenLDAP/Samba) with scheme selection and configurable connection parameters such as Base OU and Bind DN
- Employee directory field extraction from LDAP including full name, email, job title, department, phone, and telephone extension
- Public directory rendering via a native shortcode `[ldap_directory]` and also via native Elementor widget / Beaver Builder module
- Server-side directory features including search and pagination with configurable items per page, designed to handle large directories using RFC 2696 paged LDAP results
- Department filtering and exclusion enforced at the LDAP query level, including the ability to exclude specific departments and optionally exclude employees with no department assigned
- Caching of LDAP results using transients with configurable TTL, one-click invalidation (Clear Cache), and a resilient stale fallback when LDAP is temporarily unreachable
- Admin settings UI under **Settings → LDAP Directory** with guided connection/employee/field configuration, including an option to encrypt the bind password at rest and a toggle for SSL certificate verification (plus optional CA certificate file path)
- Multisite compatibility with per-site settings
CONTENT BOUNDARY
LDAP Staff Directory 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
LDAP Staff Directory and REEID Translate FAQ.
What does LDAP Staff Directory do according to the available plugin evidence?
LDAP Staff Directory has 8 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 LDAP Staff Directory?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for LDAP Staff Directory?
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 LDAP Staff Directory in a multilingual WordPress workflow.
REEID documents LDAP Staff Directory 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.