It means WPML registered them in String Translation and added them to a configuration file.
You cannot unlock such strings, but you can still translate them. Please notice that with WPML you can't change the original strings, just the translations.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello!
You are confusing things. What you can unlock are settings, not strings. The ones you have shown us in the screenshot are custom post types translation preferences, not strings.
The strings you see as "locked" mean they were pre-registered by a plugin or theme, in this case called "homey" and it looks like an option, so maybe coming from blocksy?
If it appears like that, it means that it should be registered, so may I ask what are your trying to achieve so I can see if that lets me find s way to help you solve your problem?
I am trying to figure out the differences to help in finding some strings for translations which can not locate using different WPML methods. I translated all except few strings.
Such strings
In Homey theme and Homey main Core plugin
1- Check-in & Check-out in calendar
2- Affiliate Booking Link
Enter Affiliate Booking Link
3- Listing Mode
4- ID
5- please wait...
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Thanks for the answer.
So am i correct in thinking the problem is that you have some strings that doesn't appear as translated in the front-end?
In that case, locking/unlocking strings will not really help much, instead it could even hurt you. if a string appears as locked, then it means that the author of the theme or plugin thought those strings needed or could've been translated and pre-registered them for you.
Them being pre-registered will not create any kind of trouble and if the string is not appearing then it could be they are not registered to be translated.
I'd suggest that as a next step, you ask the theme author if they can tell you the location of such strings and if they are JS strings, because those are the only strings that are not easy to translate or are untranslatable.