[Plugin: WP-Members] Localization – multilanguage support

Thanks!

Yes, that is on the project list.

Great ??
Looking forward to it!

I volunteer to contribute the Hebrew translation and market it in Israel ??

That sounds great!

Could you shoot me an message via the contact page on my plugin’s site (https://butlerblog.com/contact/) so I can contact you directly when I’m ready?

…subscribing

…I just rewrote your plugin and localized it for Ukrainian. Took me several hours, but it was doable.

One of the problems that I saw with your plugin, in it’s present condition, aside from the actual gettext wrapping that I did, was that you need to be logged in with the language you intend to have the front-end interface (of your registration form) in, because once you install it, if you change your localization, it’s stuck in the db, unless you delete them and reinstall. I think this is a major thing that needs to be rewritten, if your localization is going to be successful. I am specifically talking about the “Manage Fields” section, under “Field Label.” Also, the “WP-Members Dialogs and Error Messages” works the same way, upon installation. Furthermore, you need to work on how the “WP-Members Dialogs and Error Messages” fields act with certain text. In Ukrainian, we use the apostrophe for words like ?м’я. I tried to use this in my localization and your Dialogs and Error Messages fields, here in the administration kept putting a \ before my ‘. That doesn’t work; it looks ugly on the front-end. If I think of other issues, I’ll let you know. But that is what I came across as I was working. Also, I had a problem with “get_user_meta” in your code. This doesn’t work on WordPress 2.9.2. It throws a rather ugly Fatal Error message on the front-end edit user details form. So, I had to change it to “get_usermeta” and it worked after that. You probably need to re-write this in your plugin, so that both can be used, depending on if you are pre-3.0 or 3.0 and up.

Thanks for the comments. Those are things that I have considered and there are a couple ways of dealing with them. But I’m always open to suggestions as well, so feel free if you find anything and have a good idea.

As far as the get_user_meta issue, get_usermeta is one of a number of WP functions that has been deprecated in WP, as you have discovered. Supporting outdated versions of WordPress simply is not viable possibility. On our end, it creates much more work in testing upgrades. On the user end, it does nothing to motivate users to upgrade their outdated (meaning obsolete and insecure) versions of WP. With that said, while this was noted in the changelog, I did neglect to appropriately indicate 3.0+ compatibility in the heading of the readme. That has been corrected.

@cbutlerjr – thanks for your response. The problem, with this particular transition, is that not all plugins are totally ready and stable for WordPress 3.0. So, at this particular moment, I am waiting until the plugins catch up and then I will try test installations and test upgrades, before upgrading my site(s) to WordPress 3.0 and the supported plugins. So, in this particular case, I would have thought that your plugin would work with the latest 2.9.x release, since it was only very recent that WordPress 3.0 came out. Anyway, thankfully I was able to figure out what to change to get it to work with my 2.9.2 site.