Background of the issue:
I am trying to resolve a critical issue on my site hidden link where the Dokan vendor dashboard page at the URL /dashboard/products/ returns a 404 'Page Not Found' error when WPML Multilingual CMS is active. I have confirmed the conflict is with WPML, as the error disappears when the plugin is deactivated. I have flushed permalinks multiple times, confirmed Dokan's page settings are correct, and increased the WP_MEMORY_LIMIT to 128M as suggested, but the issue persists. We do not have a 'WPML Integration' module in our Dokan Pro version.
Symptoms:
404 'Page Not Found' error on Dokan vendor dashboard page when WPML is active.
Questions:
What are the next steps to make WPML and Dokan work together?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi,
I recommend you to teach out to the Dokan support. They developed the compatibility add-on for WPML and not we. However, please note that your error happens on a default language page outside of control of WPML.
I have an important update. I performed a final plugin conflict test.
I deactivated all plugins except for Dokan, Dokan Pro, WooCommerce, WPML Multilingual CMS, and the Dokan WPML compatibility plugin. The 404 error still happened.
Then, while keeping all of those active, I deactivated only the main WPML Multilingual CMS plugin. The 404 error was resolved immediately.
This confirms 100% that the conflict is with your core WPML Multilingual CMS plugin itself, even when the official Dokan WPML extension is active.
Please advise. This is a critical issue for our site.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi [Name],
Thank you for the details. Unfortunately, if the issue is caused by an incompatibility, we can’t resolve it within our codebase. The correct way to ensure compatibility is through the Dokan Add-On itself.
If you’re able to reproduce the issue from scratch on hidden link">this isolated Sandbox by installing Dokan and triggering the problem, I can forward it to our compatibility team. From there, we can reach out to the Dokan developers and request that they implement a fix or help them providing a workaround. Please note, however, that we’re unable to address this directly in our code.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
You're very welcome! This works fine for us. If they're unable to assist, we're happy to explore a workaround on our end.
However, for a long-term solution, their collaboration is really important — especially to ensure that any workaround we implement isn’t overwritten by a future plugin update. Their support would go a long way in helping us establish something more sustainable.