We believe Multilingualizer may work well for more traditional environments, but it is not compatible with modern React single page apps hosted on Replit. Since we followed all instructions, translated the full site, and exhausted all troubleshooting options without any viable results, we are requesting a full refund of the license fee. If you can fix the issue that would be great.
1
July 27, 2025 @ 3:05 pm
Our site is built using React.js (version 18+) with TypeScript, compiled via Vite, and hosted on Replit as a single page application. We use Wouter for client-side routing and Express.js on the backend. We followed your installation instructions precisely, including placing the Multilingualizer script inside our index.html file. We manually added proper language markers such as “||fr||” throughout all visible text and fully translated the content of the site into French. Every word was translated and inserted following the formatting standards described in your setup guide. We ensured syntax accuracy, spacing, and encoding compliance.
To force detection, we also implemented custom logic using React lifecycle methods like useEffect and setTimeout to trigger scan() calls. We attempted to preserve language selection with localStorage and configured noreloadonlanguagechange as instructed. We also delayed DOM rendering to allow your scanner to process the content and experimented with rerunning scans on route change events. Despite these considerable efforts, the integration never functioned reliably.
The translation switching only worked on initial page load. After navigation or any re-render event triggered by React, the translated content would disappear or flash briefly before reverting to the default language. Translation markers (||fr||) sometimes became visible to users. Navigation menus broke on route changes. Mobile users experienced severe instability. Console errors such as “ml_scan_queue is not defined,” “scan is not a function,” and “Multilingualizer failed to initialize properly” occurred regularly.