This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | - | 9:00 – 18:00 | 9:00 – 18:00 | 9:00 – 18:00 | 9:00 – 18:00 | 9:00 – 18:00 |
| - | - | - | - | - | - | - |
Supporter timezone: America/Lima (GMT-05:00)
Tagged: Compatibility
This topic contains 36 replies, has 0 voices.
Last updated by sharonH-6 1 day, 5 hours ago.
Assisted by: Andreas W..
| Author | Posts |
|---|---|
| November 6, 2025 at 10:46 pm #17555727 | |
|
sharonH-6 |
Following up ... 1. Directorist will not have the technical capability to resolve these issues. This I know from bitter experience. They cannot even understand the issues, when written out very clearly and supported visually with detailed looms. I have still forwarded your message to their support, but I already have about 10 tickets spanning over a year that remain pending. This one will be no different. 2. I checked the recommended settings and they were already all set to Translatable only show translated items - which worries me as does that mean they should be working and aren't? 3. You alluded to the possibility of providing assistance if Directorist could not. If I created separate tickets for each, would that make it possible to receive this assistance? Regarding the exceptions: - Add Listing Form - you say there is no workaround - does that mean this cannot be rectified with your assistance? - All Locations and other dynamic widgets - is this something you could assist with in a separate ticket? - Search form - Shortcodes used by Directorist -(eg All Listings shortcode) are you able to assist with this in a separate ticket? |
| November 6, 2025 at 10:54 pm #17555728 | |
|
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
The issue currently is that these Elementor Widgets are not translating for two reasons: 1) They are missing a custom XML configuration so that the texts from those widgets appear inside the WPML Translation Editor. I provided such a config. 2) Most widgets rely on dynamic data for listings, taxonomies, or user data that aren't text inside of the widgets. These are pulled from the database, and this means that the plugin needs to use "WPML Hooks" inside the code of the plugin, so that WordPress will be able to display the correct dynamic content per language. For some widgets, this is already working, for others not. There are further widgets that seem to pull code directly from the plugin's code, and this will not work - I would say in cases like the "Add listing" widget, the author did not really create a complete Elementor widget - it seems like he simply passes the plugin's code through, similar to a shortcode, like the ones use on the pages. If you visit my sandbox and revise the translated page "WPML Test DE" you can see how the translation for the Elementor Widgets will appear after having followed all my mentioned steps. There are only some strings that are actually translatable inside the WPML Translation Editor. At this point, I could usually offer to escalate the open issues to our compatibility team, but I am afraid that there are too many open issues, and this should be handled more effectively through our partnership program. It would be ideal if the author applied here: |
| November 6, 2025 at 11:05 pm #17555735 | |
|
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
My apologies, I see that we do recommend the plugin: There is also a known issue that Elementor widgets and Gutenberg blocks cannot be translated, and we have already contacted the author about this: I will create an extensive report for the issues I found and escalate internally so that our team can try to contact the author again. Note that our team will not be able to solve those issues, as we have no influence on the code of third-party plugins, but we will try to get in contact and recommend necessary changes. |
| November 6, 2025 at 11:27 pm #17555742 | |
|
sharonH-6 |
Hi Andreas, I am not in the least bit surprised that Directorist know about these deficiencies and continue to advertise their plugins when they do not work. I will have to hire the developer who has been working with me to patch up all the core and extension Directorist failings to fix these as well I guess. I honestly think that WPML need to warn people that Directorist is NOT compatible with WPML before they go ahead and purchase the plugin. Surely it should NOT be on the list of recommended plugins?? |
| November 7, 2025 at 12:03 am #17555778 | |
|
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
This is correct, and if our team does not obtain the cooperation of the author, we will need to consider not recommending the plugin, until all open issues are solved. I am about to create a report tonight that sums all open issues of my test and then escalate internally to the compatibility team. We might be able to provide workarounds for at least some of the issues, but I need to ask you for some patience. |
| November 7, 2025 at 12:17 am #17555781 | |
|
sharonH-6 |
Thank you Andreas, it's been a year of pure hell with Directorist and the bugs in all of their software. I wouldn't want anyone else to get as far as I have overcoming all of that, and then discover that they can't make their site multi-lang. If you were able to help in some way, I'd be so grateful. I've spent thousands on developers so far, for a site that is still not making any money and is like a black hole. |
| November 7, 2025 at 3:42 am #17555881 | |
|
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
Kindly take note that currently, I am only running the following plugins on the sandbox: - Directorist - Business Directory Plugin Result: [directorist_all_listing] The main issue here seems to be that those shortcodes are not considering any translated listings. The only translated pages that work as expected on my test are the login page and the dashboard. I am escalating this issue now to the compatilbity team and will keep you updated in case the team comes up with a workaround. I suggest we first focus on solving this issue and then create another escalation for the Elementor Widgets - if still needed. |
| November 7, 2025 at 3:50 am #17555882 | |
|
sharonH-6 |
Thank you Andreas. I'll wait to hear from you and appreciate your support. |
| November 7, 2025 at 6:48 pm #17558315 | |
|
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
I just realized something in my sandbox today. Each listing has a Directory Type, and currently, all listings use the Business Type. If I visit the translated pages on the sandbox and select "Business" I can see the translated listings, and the "All listings", "Add listing" or "Search form" will work as expected. See screenshot. Example: Page with widgets: It also works for the translated Elementor Widgets, if you select the proper directory type filter. Please take a look into this and let me know if you have further questions. This said, the translated pages and Elementor widgets do work, I am simply not understanding why on translated pages I first need to select the directory type, and on original pages there is no such select option. I can no longer confirm that Directorist is not translatable; it is just unexpected that there is a directory type filter on translated pages but not on original pages. I am consulting this with the compatilbity team. I am further escalating regarding the missing custom XML configuration for the Elementor widgets. |
| November 7, 2025 at 7:00 pm #17558353 | |
|
sharonH-6 |
Hi Andreas, Thank you so much for your latest message and your ongoing support. So, that is another Directorist bug: I have more than one directory but I only want the Business directory to show. In Directorist, there is a setting where you can make Business (in my case) your primary directory and turn off the others from displaying. But guess what ... there is a bug that means that it doesn't actually work on the front end. So I had my developer fix this issue but then it returned with a new Directorist update and he only recently fixed it again. In my stage.nicaseeker.com site, he's fixed the issue and pushed that fix to the live site. But on checking your sandbox, if you switch multi-directory off, the bug is still there - it doesn't save. Well, it does appear to save but if you refresh the page, multi-directory reverts to on. So does that mean everything is translatable then - and that I can continue translating and the translations will save or is there still a long list of issues that need to be addressed? I look forward to your update on the other issue in due course. |
| November 7, 2025 at 7:05 pm #17558387 | |
|
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
Of course, our team will take a closer look at this. I only need to ask you for some patience. Thank you for the provided details and your cooperation! |
| November 7, 2025 at 7:42 pm #17558517 | |
|
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
The directory type issue can be solved by going to WPML > Taxonomy Translation and making sure that "Listing Directory" is translated. Important is also important to translate the base slug atbdp_listing_types. See screenshot. Please give this a test on your site. |
| November 7, 2025 at 8:47 pm #17558638 | |
|
sharonH-6 |
Thank you so much Andreas, so with the base slug, I need to translate it into Spanish? I'll implement those other translations as advised. Below are screenshots of what I've done ... |
| November 7, 2025 at 9:04 pm #17558699 | |
|
sharonH-6 |
Silly question, but how do I test it on my site? So far, I've only translated the home page (which didn't really work) and the About page, which didn't save a lot of the translation. |
| November 7, 2025 at 9:14 pm #17558702 | |
|
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) Spanish (Español ) German (Deutsch ) Timezone: America/Lima (GMT-05:00) |
I have not tested to translate the base slug and would suggest using in this case the same slug atbdp_listing_types in both languages. Indeed, you would need to create some translations to confirm if the issue is solved. For now, make sure that my suggested custom XML config is saved inside WPML > Settings > Custom XML Configuration. Also, revise WPML > Settings > Custom Field Translation for proper settings. Check also after clicking "Show system fields". You can use my sandbox as a reference for the correct settings: |





