开发者 | autoglot |
---|---|
更新时间 | 2025年8月22日 00:30 |
PHP版本: | 7.0 及以上 |
WordPress版本: | 6.8.2 |
版权: | GPLv2 or later |
版权网址: | 版权信息 |
Yes, you can! Starting from version 2.3.0, Autoglot provides a flexible Translation Editor that lets you manually modify translations. This tool displays all records from translation DB with convenient "search" and "filter by language" functions. There is an option to delete translation records so they will be re-generated. The most important, translation editor comes with a "Quick Edit" button to let a site administrator, translator or proofreader manually adjust and modify the translation.
If you're using a caching plugin or server-side caching in your hosting provider, please start with clearing/purging it. Try refreshing your website page or access it in incognito mode.
When you first open an untranslated page, it might take a bit longer to load. This is normal - it just takes some time to extract the content, send it to our API for translation, and get it back. Once it's translated, it's stored in your local database and will load quickly for future visitors, just like any other WordPress page.
Yes, this can be done using our "Text Replacement" tool. This feature of Autoglot plugin lets you easily change pieces of content on your translated pages. For example, you can change video URLs depending on current language, so you will show different videos in different languages. Additionally, you can localize external links, images, and even your site appearance!
Currently, it is not possible to automatically translate text on images. Even with the latest advancements in AI technologies, the results of this "AI translation" can be unpredictable. The only way to proceed is manual replacement, and this is what Autoglot can do using the "Text Replacement" module. This can be done in 3 steps:
You can use a [ag_switcher] shortcode to add a language switcher to your website posts, pages, popups, etc. Add a "title" argument if you want to set a custom title of this box: [ag_switcher title = "Website Translation"]. Use a "type" argument in order to select a type of language switcher:
The quality of NMT (neural machine translation) has increased significantly lately. According to some experts, the leading machine translation providers can show the quality comparable to medium-level professional translators. Moreover, many of these translators also use neural machine translation systems to generate the initial translation and then slightly proofread it. Sounds weird? Add the fact that you will have to pay them 100 times more. Autoglot provides reasonable quality for the fraction of this cost. And it is fully automated!
We currently support these languages. The more languages are coming soon. If you have special requests, do not hesitate to contact our support.
Yes, Autoglot supports translation of basic WooCommerce functionality. This includes WooCommerce products, cart and checkout process, including dynamic updates of shopping cart and checkout, and switching between different shipping addresses. In order to prevent excessive expenses, Autoglot will not translate all dynamic messages and emails. However, please note the following:
Yes, starting from version 2.6.1, WP users with "Editors" role can access Translation Editor module and edit/delete translations. To enable this, please proceed to Advanced settings and under Admin Settings choose "Yes, Editors can edit and delete translations". Don't forget to save settings!
Yes, you can use the same API key on different websites. These can be your staging and production sites, or even completely different domains. If you need to activate Autoglot account on another website, simple install and activate the plugin, then use the same Autoglot API key during setup or on the Autoglot settings page. When you enter your Autoglot API key on a different website, it will link that new site to your existing Autoglot account, allowing you to use your translation balance there. Please make sure this is secure as there isn't any way to limit the consumption of translation credits for each individual website. Sharing API keys with other people isn't secure and could lead to unexpected expenses. However, if you own all the sites where the key is used, this approach works perfectly.
All translation are stored in your local WP database, particularly in [wp_prefix]_autoglot_translations table. In order to move translations from your staging to your production environment, simply move this table to the production DB. In this case, no new API call should be made (this is only valid if the original content is absolutely the same). Please note, if you set up Autoglot on two separate sites (e.g., your staging and production environments) and translate the same content on both simultaneously, you will use your quota twice (once on the staging site, and then again on the production site). Think of it like your main post content: if you add content on your staging server and then move that database to your production server, you'll see it there. If you don't move the database, you'd have to add the content on both your staging and production servers twice.