[mogelinas]

Hi,

Any updates on that problem, I’m having the exact same problem with Neighborhood 1.90, Woocommerce 2.1.12, WP 3.9.1

When I first started to build my site, I entered french values for every Theme Options that I needed to be in french. Then I realized it needed to stay in English in Theme Options and translate it to french in WPML String Translations. That’s what I’m trying to do right now, but every time I revert the values back to english (to translate them in WPML) they go back to the translation I do in WPML String Translation. So step by step here’s what’s happening:

1. In Theme Options : The Values are in french (from the first time I changed them), then I change them to english and press save. Everything is OK for now.
2. I go to WPML strings translation : The new english string I just changed in Theme Options appears as
Context : admin_texts_theme_neighborhood
Title : [sf_neighborhood_options]checkout_new_account_text
String : Creating an account with… —> (The text I just added in Theme Options)
3. When I add the French translation for this string and check the box for translation complete, Status is now Translation Complete
4. When I go back to Theme Options, the value is now changed for the french translation I just did!

I don’t know if it will help you, but I noticed some old strings I created (in english) appear as : Context : theme swiftframework (instead of admin_texts_theme_neighborhood). And if I write these exact strings in my Theme Options page, the translation to French works fine on the frontend. The only problem is that I don’t have a theme swiftframework context for each strings I create. Instead, they appear as admin_texts_theme_neighborhood, and when I translate these values, it changes in my Theme Options and not on the Frontend.

It looks like it doesn’t find every theme swiftframework strings I create and instead creates a admin_texts_theme_neighborhood that changes the values I create in Theme Options.

Please help me with this SwiftIdeas! Thanks

[mogelinas]

Hi,

I had the same problem and Post Types Order plugin worked for me.

Cheers!

[mogelinas]

Hi,

I had the same problem, you absolutely need to put a price for each variation to show in the dropdown.

Hope that helps.