Ajax Search Pro Documentation

Get Ajax Search Pro!Get Support Knowledge Base

Feature & Bug request Beta Testing Slack Channel Roadmap

Get Ajax Search Pro!Get Support Knowledge Base Development

Ajax Search Pro Documentation
GDPR and Cookie policy
Video Guides
Plugin Updates
Installation instructions
- Uninstallation & Reset
Troubleshooting
- Styling issues
- The response data is missing from the ajax request error message
Getting started
Search Sources
Behavior
Elementor Integration
Other Integration
- Jet Engine Listing Grid Integration
Multisite Settings
Frontend Search Settings & Search Filters
Layout Settings
Autocomplete and Keyword suggestions
Theme Options - Visual changes to the search bar
Index Table
Relevance Options
Advanced Options and Uses
Result priority settings
- Individual Priorities
- Priorities by Rules (priority groups)
Performance Tuning
Compatibility Settings
- Javascript Compatibility
Google Analytics Integration (GA4)
Translating components
- Translating with WPML
- Translating with Polylang
Pre-Purchase FAQ
Plugin API
Other Useful Things

Powered by GitBook

On this page

Translating components

PreviousSite Search Tracking NextTranslating with WPML

Last updated 6 years ago

Because almost every text on the front-end is dynamically adjustable, the default way of translating (.mo and .po files) will not do the job - as they only work with static content.

If you want to translate the front-end of the plugin, you will need a 3rd party multi-language plugin, which supports string translations.

Currently two plugins are supported for this task:

Translating Ajax Search Pro with WPML string translations plugin

Translating Ajax Search Pro with Polylang plugin