The following plugins provide integration of qTranslate-X with other popular plugins:
- ACF qTranslate for Advanced Custom Fields, [GitHub].
- All in One SEO Pack & qTranslate-X for All in One SEO Pack, [GitHub].
- Events Made Easy & qTranslate-X for Events Made Easy, [GitHub].
- Integration-CMB2-qTranslate for CMB2 [GitHub].
- Fusion Core & qTranslate-X for Fusion Core [GitHub].
- qTranslate support for GravityForms for Gravity Forms Directory, [GitHub].
- WooCommerce & qTranslate-X for WooCommerce – excelling eCommerce, [GitHub].
- Integration: Yoast SEO & qTranslate-X for Yoast SEO, [GitHub].
- WPBakery Visual Composer & qTranslate-X for WPBakery Visual Composer, [GitHub].
Please, report other plugins that fit this list.
Plugins Naming Convention
When submitting a new integrating plugin to WordPress, enter the name of plugin on submission form in such a way that it generates slug “[slug of original plugin]-qtranslate-x”. Plugin’s slug gets auto-generated once at the time of submission and can never be changed. This way the two plugins get listed next to each other in folder on file system. Once your plugin is approved, change the title to be “Integration: [Title of Original Plugin] & qTranslate-X”. This is how most of integrating plugins are currently done. Do not start the plugin title with neither name of the original plugin, nor with “qTranslate-X” as this violates trademark policies, as it is explained in the item #17 of WordPress Detailed Plugin Guidelines and WordPress folks will ask you to change it sooner or later when they discover it.