Just checking if this issue was eventually resolved in another thread? Or by yourself separately to us? Or by us over email with you? Or using our live support?

If so, no need to reply, that's great news.

If not, or you have any more questions related to this thread, please feel free to post them below including any new symptoms or errors and tick the 'Mark as Not Resolved (re-open)' box below the post area (or else we'll miss it!)

Lower case 's' to subscription as _e() is case sensitive. I did update the .mo, but there was a difference in case between the .php and the .po file. I can't beleive the amount of time it took me to solve this. Of course it just so happened that the string I used to test the translation was not properly ported to thew supplied .po file. Figures!

<p class="help-block"><?php _e('We have the following subscriptions available for our site. To join, simply click on the <strong>Sign Up</strong> button and then complete the registration details.','membership'); ?></p>

Thanks for the 411 Arun. I think updating membership.po is a pretty big priority. My client is asking me to translate the sign up form and I'm finding myself in an awkward situation because of this. I don't want to manually translate all the .php files only to be given the actual.po file 2 weeks later.

Can anyone else confirm that membership.po in Membership3 RC1 is outdated?

I am not trying to be a smart butt or anything but basically you have confirmed that the po file in Membership V3 RC 1 is outdated and we are thankful for you bringing this to our attention of course.

The best we can hope for is that it is updated hopefully with the next release.

I did want to point out the following fact, though this does not help the situation any, but does give a clearer understanding of what is going on, that any version of a software, script, etc. that has RC in it officially means "Release Candidate" which in turn means a bug shake out.

Therefore if you did not already know, anything marked RC/Release Candidate is bound to possibly have several bugs in it or issues within it as you have no doubt have found one and there are bound to be others.

Just wanted to be informative and to let you know that one can expect bugs and problems with any RC version.

@aecnu
As stated in my previous post, I did NOT install RC1. But thank you for explaining the meaning of 'RC' to me like I was a 5 years old.

Please note that I am running 3.0 (which btw, is absent from the "previous version" section). Still had the same issues. I painstakingly translated membership.po v2.4x and everything worked fine. The nightmares began after upgrading to 3.0 (which was strongly recommended by your support staff). Now, all that work has to be redone.

Also note that this is not a glitch or a bug. This is a glaring, unprofessional omission.

I would also like to make it abundantly clear that I am NOT running RC1 but 3.0.

I am no longer making money with my current project. I am now LOOSING money trying to make Membership play nice. I would gladly drop Membership from my project in favor of another solution (S2) but I have spent so much time/effort/money trying to make it play nice. Paying customers have already subscribed to my client's site via Membership. I am now regretfully committed to Membership.

Furthermore I now have to:
- Wait until RC2 is rolled out, with NO timeline provided from the developer
- Confirm that membership.po has been updated
- REDO all translations I have already billed my client for when installing 2.4 - at my own expenses.

Please update membership.po and provide a timeline so I can advise my client and move on.

Just installed RC2. First 2 strings I looked for in membership.mo are not present

1) "Select a Subscription" (.mo is case sensative, so I had to lower case the 'S' in the source of subscription.form.php to match the string in membership.po)
2) "We have the following subscriptions available for our site. To join, simply click on the Sign Up button and then complete the registration details." - not present all.

If you are still having an issue please let us know so that we may try to get you fixed up as soon as possible by choosing to check mark this ticket as unresolved below and posting any new errors or symptoms you are noticing.

This action will also bring your ticket up front back in plain view again within the ticket system.

How do you rate me?

Thank you for rating your experience!

We’re thrilled to hear you had a great experience with . Would you like to leave a comment about your experience?
Thanks for voting on your experience with , we’d love to get some feedback please.
Ohh no! We’re really sorry to hear you didn’t have a pleasant experience with , we’re always looking at how we can improve and would appreciate you provide some further feedback here please.
Type your feedback here

it's great that you had a positive one. Based on your experience in this ticket would you please be kind enough to rate us externally on: