This thread is resolved. Here is a description of the problem and solution.
Problem: The client is seeking a refund for WPML due to issues with translating Divi's dynamic text and buttons. Additionally, they encountered problems where the menu stops working, dynamic content doesn't translate, or the automatic date displays incorrectly. Solution: To request a refund, the client should visit https://wpml.org/purchase/refunds/ if the purchase was made within the last 30 days. For issues related to Divi's buttons not translating, the client should refer to their existing support ticket at https://wpml.org/forums/topic/divi-buttons-arent-translating/. If new problems arise or if the translated content stops displaying, it is crucial to provide detailed information about the translation method, plugins used, server and memory configurations, theme details, and any custom code to the WPML support team for further investigation.
Please note that the solution provided might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket for further assistance at WPML support forum.
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.
Background of the issue:
I am trying to get a refund for WPML because Divi's dynamic text and buttons aren't translating, and no solution has been provided. I spent a whole day translating the entire page with all the modules, but WPML always has some problems.
Symptoms:
The menu stops working, dynamic content doesn't translate, or the automatic date goes wrong.
Questions:
Could you please tell me what I need to do to get my money back?
It's just that right now, instead of solving the problem, the support team is focused on obtaining information about our server and software. This request seems like an evasion of responsibility for plugin errors, as server and software information isn't needed to resolve this issue with WPML (the problem is too specific). This is most likely a WPML and Divi optimization issue.
Other plugins translate the same website without any support requests. This is exactly what we expect.
What about translating dynamic text? Is it possible or not?
In short, we've found a solution to the problem with translating dynamic text in buttons. The problem was that WPML couldn't find the string we needed to translate, and when it did, the translation didn't produce any results. Through trial and error, we figured it out and now understand what needs to be done to get WPML to translate the dynamic text. All we needed from support was to share the solution (or possible solutions). The solution is fairly simple, but due to the complexity of the WPML plugin, all the dependencies aren't immediately clear. It would be great if these dependencies were described somewhere, but we couldn't find any information on the WPML website about how to translate when these errors occur.
In short, we've found a solution, but due to the specifics of Divi, there are limitations to using WPML. It would be great if WPML could seamlessly translate dynamic text throughout the entire site, including blocks created off-page in the Theme Builder section. Currently, you can translate the footer created in Theme Builder, but when using dynamic text (such as a date), it doesn't translate, and searching for the code yields no results.
Basically, a refund is not required. We'll keep trying and looking for a solution, hoping that the WPML team will gradually fix the issues with dynamic text (dynamic text is becoming the new standard in web development).
We just solved one problem when another one popped up. What should we configure so that language version links always redirect to pages in the same language (we've tried a lot, including the Sticky Links plugin)? Now we have to change each link in the editor, and this setting resets immediately after a translation update. Any solutions?
Another problem has popped up: the translated content stops displaying, and it's unclear how to restore it. Any solutions?
This is a real pain!!! You solve one problem and 10 more pop up!!!
We can write a long review about how many bugs WPML has and share it with our subscribers (we have over 250,000 subscribers across all our projects) so they can spread the word even more. This could attract high-level developers who can help you solve your WPML issues. Apparently, you're not solving problems; you're writing articles about what to do and what not to do—an approach that was outdated 10 years ago. You need to fix the issues in the plugin itself. So, shall we do it?!
"Tell me when can I expect a refund?"
If you still haven't, you need to ask for a refund in https://wpml.org/purchase/refunds/. You are eligible if you bought WPML in the last 30 days.
Please note that we can have one issue per ticket, and this one was created to address the refund question.
I see that you already have an open ticket for the non-displayed information issue. If you have any other questions on that subject, please proceed there:
I understand that you're frustrated with WPML. As you can see yourself, making dynamic content localizable is not a simple task, as each website has different server settings, plugins, themes, and so on.
It seems that the solutions and information you're expecting are not so simple to answer.
"Another problem has popped up: the translated content stops displaying, and it's unclear how to restore it. Any solutions?"
We need to investigate it. We have no idea which translation you're referring to, how it was created, which plugins you're using, your memory and server configurations, what theme you're using, if you have custom code, which strings you have registered and so on. I need that information and possibly website access to understand what might be causing that. It's debugging, it's not something we as supporters know from memory or can guess without investigating.
Please provide the requested information to my colleague Otto, so he can proceed with support. The more you provide us with the information we request, the better and faster we'll be able to support you and solve your problem.
Again, this ticket was created to address the refund issue. If you have any comments on the other issue, please answer there. Any new issues or questions, please open a new ticket.
We learned more empirically than we did from your support team. You don't understand your own software at all. Do you have any real professionals who can dig into this, figure it out, and provide a valuable, qualified answer?
