I can’t see the language selector

If you can’t see the GPTranslate language selector in the frontend after installing and enabling the plugin, it’s very likely that a JavaScript error or conflict is preventing the script from executing correctly. This usually happens due to third-party extensions or plugins, especially performance optimizers that minify, combine, defer or delay JavaScript files. This scenario is quite common on WordPress websites with several plugins installed. It’s strongly recommended to open the browser developer console (F12) and check for JavaScript errors. In most cases, the issue is caused by optimization plugins that modify the JavaScript loading order. On WordPress, this commonly includes performance plugins such as: WP Rocket Autoptimize LiteSpeed Cache W3 Total Cache SG Optimizer FlyingPress Perfmatters These plugins may combine JavaScript files, defer or delay their execution, or move scripts to the footer, breaking the execution order required by GPTranslate. If this is the case, you should review your optimization plugin settings and disable or adjust the following options: JavaScript file aggregation / combine Defer JavaScript execution Delay JavaScript execution (especially “delay all scripts”) Load JavaScript in footer Preserve modern Javascript files of type ‘module’ Inline JavaScript minification or compression Make sure to exclude the following GPTranslate JavaScript files from any optimization process: gptranslate.js jsonrepair/index.js responsivevoice.js toast.min.js If supported by your optimization plugin, you should also exclude GPTranslate inline JavaScript from minification, deferring or delaying, as inline scripts depend on the immediate availability of the files listed above. Typical exclusion fields where GPTranslate scripts should be added include: “Excluded JavaScript files” “Scripts excluded from defer” “Scripts excluded from delay” “Excluded inline scripts” If your optimization plugin provides a “safe mode”, “compatibility mode” or “no-conflict mode”, try enabling it and then clear all caches. If automatic compatibility options do not solve the issue, manually adding the GPTranslate scripts to the exclusion list is required to ensure they are loaded and executed in the correct order. As a last resort, you can temporarily disable JavaScript optimization features entirely to confirm that the issue is caused by script optimization. Also check if your WordPress theme includes built-in performance or optimization options. If so, make sure GPTranslate scripts are excluded there as well, or temporarily disable theme-level JavaScript optimization.