ericH-23
|
Hi,
In the meantime I had a conversation with Skyverge about translation of the membership names. Unfortunately they said, it is a matter of WPML or a customisation.
I searched for solution now a while and found some entries in your forum and so we have 2 possibilities to work with Woocommerce Memberships:
1) set Membership Plans to non translate
2) set Membership Plan to translate
to 1)
the membership plan titel is not translated, so in another forum ticket of me you told me as like Skyverge does, this is a matter of customisation
to 2)
regarding this ticket I decided then to use the translation features of WPML also for the Membership plans but run into a severe issue, so that this possibility cannot be used: a membership is created in every language for one user with buying one subscription product, so he have bought not one but for example 5 memberships, one of every language, that makes no sense (this problem was also mentioned in another ticket in 2023 without result)
So at this point I am wondering, why you say, that the compatibility of Woocommerce Membership plugin is "WooCommerce Memberships is compatible with WPML. This plugin has been tested thoroughly, and you can use it to build multilingual sites without experiencing issues." (https://wpml.org/plugin/woocommerce-memberships/)
My question is: how shall I set up the Woocommerce Membership plugin with WPML to have no issues?
Moreover: I decided to go way 1) and accept for the moment to have the membership names not translated to going forward (this topic needs so much time !), but here I have the problem, that the product categories restriction work in the standard language (English), but not with the other languages. So an user has access to products, that he must not see. But here I don't know whether it is a problem in my configuration or it is not possible generally (help is needed, please).
Hope we can solve my way 1) now. But the best way would be you make it possible to have translated names of the membership plans, by this the woocommerce membership plugin from Skyverge have no issue, as you said it at https://wpml.org/plugin/woocommerce-memberships/.
Of course, it is also possible that I am wrong and there is a solution, maybe a code snippet or something. I would be pleased if you could explain this to me.
Thanks a lot, kind regards
|
ericH-23
|
Hi,
Today I have a similar problem with the translation of Member Types of Buddyboss and found this: https://wpml.org/forums/topic/buddyboss-profile-types-cannot-be-translated-with-wpml/
Therefore I want to ask, whether the possibility for the translation of Woocommerce Membership Plans could be established in a similar way?
My problem with the product categories restriction in another language with a Membership Plan is a further top ...
Thanks, kind regards
|
ericH-23
|
Hi,
Okok, I started to setup the sandbox site, but this is need to add: https://wpml.org/plugin/woocommerce-memberships/, the two fixes must be added, at the moment a restriction content in a membership cannot be stored.
How I can get access to the sandbox, or can you please add this (why it is not added in the meantime into the latest version?).
Thanks, kind regards
|
ericH-23
|
Hi,
I activated the filemanager plugin and added the fix, so now you have the problem with the restricted content here:
A testuser has no access to the category Products, this is working in EN
hidden link
Switch to DE allows him to see the rescricted category and their products
hidden link
See the two screenshots.
In the next test I will buy a premium membership and write the result in the next ticket.
Kind regards
|
ericH-23
|
Hi,
In the sandbox the member with the free membership bought a premium membership. He gots two! The DE and the EN membership. That is false, he don't need two but only one, which shows the texts of the membership in the current language.
At the moment the Membership Plans are set to "translation", that was the standard.
I don't change this now, because I would like to show you the current situation.
I know, if I change the Membership Plans to "non translation", the names cannot be translated and are shown only in the standard language, so here in my eyes following could be done:
I have the idea, that a fix like in https://wpml.org/forums/topic/buddyboss-profile-types-cannot-be-translated-with-wpml/ could be added so that the Membership Plans name and description can be translated. But please take a look and decide the next steps.
Together with a further fix regarding the restrictions the Woocommerce Membership plugin could be working. At the moment - unfortunately - this is not the case.
Thanks, kind regards
|
Mateus Getulio
Supporter
Languages:
English (English )
Portuguese (Brazil) (Português )
Timezone:
America/Sao_Paulo (GMT-03:00)
|
Hello and thank you for your patience.
I have escalated this to our Compatibility team. I will be working with the developers to find the cause and resolution and will keep you updated here. Please keep in mind that a solution may depend on the plugin author's response. Thanks for your patience while we continue to troubleshoot.
We'll keep you posted with our progress while investigating it.
Thank you,
Mateus
|
Mateus Getulio
Supporter
Languages:
English (English )
Portuguese (Brazil) (Português )
Timezone:
America/Sao_Paulo (GMT-03:00)
|
Hello there,
Thank you for your patience while we worked on this.
We checked it and this issue has been reported previously. We have an open ticket within our developers to analyze and eventually change this behavior.
Upon further review, we were able to find a workaround that might help mitigate the issue in the meantime.
This could be done with the following steps:
- Open the app/public/wp-content/plugins/woocommerce-memberships/templates/myaccount/my-memberships.php file
- Replace the following snippet (around line 76):
<?php foreach ( $customer_memberships as $customer_membership ) : ?>
<?php if ( ! $customer_membership->get_plan() ) { continue; } ?>
- With:
<?php foreach ( $customer_memberships as $customer_membership ) : ?>
<?php if ( ! $customer_membership->get_plan() ) { continue; } ?>
<?php
// WPML Workaround for compsupp-7163
if ( class_exists('Sitepress') ) {
$wpml_current_lang = apply_filters( 'wpml_current_language', NULL );
$membership_wpml_language_details = apply_filters( 'wpml_post_language_details', NULL, $customer_membership->plan_id ) ;
if ( $wpml_current_lang != $membership_wpml_language_details['language_code'] ) {
continue;
}
}
?>
But please note that this can also have side effects. For example, if you cancel a membership in the original language, you will not be automatically cancelling the memberships in secondary languages, and they will also not be available in that screen (unless you switch the language).
I tested it in the sandbox I provided you with and it seems to be working properly in there.
Can you please make a full backup of the live site and test the workaround above?
Thank you, please let us know.
Mateus
|
ericH-23
|
Hi,
Thank you very much! But I have a question:
You wrote: "For example, if you cancel a membership in the original language, you will not be automatically cancelling the memberships in secondary languages, and they will also not be available in that screen (unless you switch the language)."
In my eyes the error begins with: a user buys a membership and gets not the one he bought but this membership in every language. So he have 4 memberships if you have 4 languages active. Thats makes absolutely no sense.
The user should buy a membership and that's it. The normal behavior as without WPML, but then with WPML only the name and the slug should be translatable. And the given restriction rights with this membership must be valid in every language.
Is it possible, that this can be achieved please?
Thanks, kind regards
|
Mateus Getulio
Supporter
Languages:
English (English )
Portuguese (Brazil) (Português )
Timezone:
America/Sao_Paulo (GMT-03:00)
|
Hello there,
This is the behavior of the workaround above.
For a definitive solution I'm afraid we need to wait on our developers to analyze this request and eventually implement the needed changes.
I'll keep you posted.
Mateus
|
ericH-23
|
Hi,
Yes, I thank you for the workaround for the moment!
Hope that at the end only the translation of name and slug is possible, no futher memberships are created with a translation and that the restriction rights work in every language.
All the best and thank you for your fantastic help!
|
ericH-23
|
Hi,
Let me add the last answer of my conversation with Skyverge hereto:
"..... However, if the restrictions are not working in this case, then it seems there's an incompatibility between the two plugins, and we would need to wait for the WPML developers to see if they can figure this out since the issue has been escalated.
To my knowledge, they still haven't reached out to our team, so if they'd like to work together with our developers, they should reach out to us at support@skyverge.com."
So Skyverge is aware already of this topic.
Would be great to have here a solution soon.
As I said: the easiest and best way would be, to have the restrictions problem fixed and don't create extra memberships for every language but offer only a translation of the name.
Thanks again, kind regards
|
ericH-23
|
Hi,
I am waiting now for more than 2 months and would like to ask for a result here. I cannot use Skyverge Woo Memberships with WPML and that is a main problem. Please improve this here as soon as you can. Thanks you. Kind regards
|
Mateus Getulio
Supporter
Languages:
English (English )
Portuguese (Brazil) (Português )
Timezone:
America/Sao_Paulo (GMT-03:00)
|
Hi Eric,
Thank you for your patience while we continue to investigate this issue.
I wanted to provide an update on the current status. Our developers are still working on a permanent fix for the issue with WooCommerce Memberships and WPML. I'm afraid we don't have a precisa ETA for when this fix will be available.
In the meantime, while we understand it is not perfect, the workaround provided earlier remains the only mitigation we have. This workaround can help ensure that the product restrictions work as expected across different languages, although it does require manual adjustments and has some limitations.
We appreciate your understanding and patience. If there are any further updates or if our developers come up with a better solution, we will notify you immediately.
Kind regards,
Mateus
|
ericH-23
|
Hi Mateus,
Thanks for your answer! I understand and I am waiting further. Hope it can be published in the next 2 months. The workaround is not the right workflow for me but thanks for this solution anyway.
Kind regards
Eric
|
