After reviewing my previous comment, I must admit that my final conclusion came out wrong. I shouldn't have written that "WPML doesn't work for WooCommerce Memberships". WPML clearly does something with WooCommerce Memberships ... perhaps, as part of this ticket, your team could publish some details about the actual, scoped integration features, so it becomes easier for me (and others out there) to understand and review that feature set rather than assuming certain behaviours and then be dissappointed by the reality.
Either case, thanks for working with me on this issue! Appreciated!
Just for clarity: at the very heart of it, I was hoping for the following scenario to be supported by the integration between WPML and WooCommerce Memberships:
As initially described, my customers are buying WooCommerce products to get access to "premium" pages that are otherwise hidden from the public. This works already in one main language and now I want to translate the entire website to secondary languages to be able to offer my premium content to an international audience.
Now, here's what I specifcally hoped for:
1) If a customer buys a trigger product in a particular language, then the customer will not only be able to access the according premium content page in that same language, but also all translated pages of that same premium content. So on the surface, a customer should be (transparently) enrolled in all translations of that membership plan.
1a) If I later on add a new language to the WPML config and a new Membership Plan translation for that new lanuage, then the premium content should be automatically available to all existing customers in that new language.
2) The customer should be able to review the original purchase record in the my-account area. Please remember that product translations can have widely varying prices, so we need a fixed record of what the customer originally purchased and at what price.
3) The customer should be able to review the membership enrollment details in the my-account area and the displayed information should be complete independently of the currently diplayed language.
Since you mentioned about that area particularly recently, I suspect if this may also be relevant in your case.
Can you please check that thread and apply that workaround on your site (in addition to the previously suggested)? And review your recent points, specially #1, #1a and #3.
About #2, I think that all depends on how WC orders are stored and then later on presented in members area, like receipts and previous purchases. These tend to be stay fixed at time of purchase and should reflect the same amounts when bought.
Please let me know after applying the fix mentioned in the other thread.
I just tried the work-around linked above in my staging environment. It doesn't seem to solve a lot, though (anything?). That whole ticket seems to circle around how WPML handles membership page-restrictions, when pages protected by these page-restrictions are deleted. I'm not sure that has to do with what I am seeing.
Did you hear back from your dev team, yet? I don't want to be overly pushy, but I really need to move on. Since it seems that neither you or I can figure out intuitively how to set up multi-lingual memberships properly, I would like to respectfully ask for a firm response to these questions:
- Is my use-case being supported by design (yes or no)?
- If no, then please state this cleary, so I can be on my way.
- If yes, then how do I set this up?
- If it's not possible to set this up right now (due to incompatiblies etc), but WPML aims to resolve this, then please provide an estimate for when this might happen.
1) If a customer buys a trigger product in a particular language, then the customer will not only be able to access the according premium content page in that same language, but also all translated pages of that same premium content. So on the surface, a customer should be (transparently) enrolled in all translations of that membership plan.
- Yes, this is the expected result. When purchasing a product in one language, the user also receives access to the same content in the secondary languages. That's why both languages were displayed on the "thank you" page (issue #2, which we provided a workaround).
However, during the investigation, we found that the same was not happening when purchasing the product through the second language (Issue #3). We provided a workaround and escalate the issue to our development team.
1a) If I later on add a new language to the WPML config and a new Membership Plan translation for that new lanuage, then the premium content should be automatically available to all existing customers in that new language.
- The translations are handled as different products, so the original/translated memberships are assigned to the user at the time of purchase (e.g. when buying the original, the user also gains access to the existing translations).
Because of that, if we add a new language AFTER the user has purchased the product, I think it would not work this way (only for new users/purchases). For existing users, it would be needed to assign the new translations manually.
2) The customer should be able to review the original purchase record in the my-account area. Please remember that product translations can have widely varying prices, so we need a fixed record of what the customer originally purchased and at what price.
- Yes, the user should be able to check the order history. I did a quick test and added a screenshot on how it works (see attached).
3) The customer should be able to review the membership enrollment details in the my-account area and the displayed information should be complete independently of the currently diplayed language.
Same here. In the memberships section, the user should be able to see all memberships that they got access, regardless of the language (see screenshot attached).
Do these answers clarify your doubts?
__________________________
Issues about restricted content
You mentioned that you are having problems with restricted content, but at the moment it is not clear what this problem is.
So far, we are aware of 2 issues: - Restricted content visible in second language: This is the issue #1 we found in this ticket. It happens because the translation is using the same slug as the default language. If we modify the translated slug of the page, it works as expected.
Hi Diego and thanks for your response - all read and understood.
Wrapped in a lot of text, you confirm that there is an issue with enrolling customers in the respective memberships when purchasing translated products. This is the core of this issue, hence the title of this ticket.
The work-arounds you presented in this ticket are merely debugging tools. When applying them to your sandbox, we could not show that they even solve the issue. Even if they did, then I would certinaly not consider such work-arounds validated production level code changes. I must thus ask one more time for a timeline of when a official fix will be available.
Languages: English (English )Spanish (Español )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello Maria,
About the workaround:
I tried the steps and it fixes the issue on my local copy. If you get a different result, please let us know and I will review it.
About the official fix:
This issue (and also the other issues reported) are at our development queue, and it was originally scheduled for WCML version 5.4.
I talked to our development team and asked them to increase the priority, so we're going to include this specific fix in WCML version 5.3.0 (expected to be released between September and the end of the year).
For what it's worth: I don't think that copy-pasting bits and pieces into the code base of other plugins is a solution, though. And waiting for months for an actual solution isn't the kind of product or support level that I can be relying on.
