Background of the issue:
I am trying to determine if a Directorist error is causing issues with WPML. I noticed an error and am wondering if it relates to any issues being escalated. The error is: Warning: Undefined variable $current_directory_type in /home/u598602579/domains/nicaseeker.com/public_html/stage/wp-content/plugins/directorist/includes/classes/class-custom-taxonomy.php on line 215. I was attempting to edit or view something when this issue occurred. The issue can be seen on this page: hidden link.
Symptoms:
I expected to see no error messages, but instead, I got the error: Warning: Undefined variable $current_directory_type in /home/u598602579/domains/nicaseeker.com/public_html/stage/wp-content/plugins/directorist/includes/classes/class-custom-taxonomy.php on line 215.
Questions:
Could the Directorist error be related to the WPML issues being escalated?
Other than the issue that Andreas handled with you, I didn't find a similar report.
If it's possible for you, do this quick test:
❌ Please make a full website backup before proceeding ❌
Deactivate WPML for a moment, check if the issue persists. If it does, it's not related to WPML. If it's gone, there may be a compatibility problem.
Andreas invited me to separate all the Directorist-related issues into different threads, because they all relate to the fact that Directorist is incompatible with WPML in a number of ways. The incompatability issue, for a plugin that is advertised by WPML as compatible with WPML is of course concerning and the matter has been escalated to the compatibility team.
I have just come across this error and I felt that this was very relevant and important to pass on as the relevant team is going to work to help me, given that this is not my fault, and WPML has advertised Directorist as compatible when it turns out that they are not.
So please don't disregard this ticket, simply because when you switch off WPML, the issue remains!
If the issue persists even with WPML deactivated, why do you think it's a compatibility problem and not an issue of the Directorist plugin itself that needs to be handled by its support?
Directorist has never provided support and when their support went into my site, they brought the live site down. I had to hire a developer to fix all bugs. Now I discover that on top of everything, while it claims - and WPML includes it on the list of WPML compatible plugins, it is not. Andreas has confirmed this and it's being escalated and Andreas said WPML will do their best to find workarounds for me and Directorist will be removed from the list of plugins it advertises are WPML compatible.
So, all I'm doing is providing more information regarding issues with Directorist that could be adding to the compatibility issues.
Thanks for the clarification, and thank you very much for taking the time to share this extra information.
I’ll make sure this Directorist PHP warning is noted and shared with our compatibility team, alongside the other Directorist + WPML issues that Andreas already escalated. Any way this warning might interact with the multilingual setup will be taken into account in that ongoing investigation.
At the same time, because this specific warning still appears even when WPML is completely deactivated, it points to a problem inside Directorist’s own code rather than something WPML can directly fix. According to our support policy, we can only debug and resolve issues caused by WPML itself or by the integration layer between WPML and other plugins. We can't take over support or bug-fixing for third-party plugins when the issue also exists without WPML.
So, in summary:
I will share this error with the compatibility team as additional context for the Directorist + WPML case.
However, the underlying PHP warning in Directorist’s codebase needs to be addressed by the Directorist developers or your own developer, since it also occurs without WPML.
We’ll continue to focus on the multilingual/compatibility part and do our best to help from the WPML side.
