A note for the author, as I can see you working a lot with your plugin.
…look into WPML yet
If your work is not prepared with translations in mind, and as @fjalestad mention, that for now the schemas not recognized on translated “ordinary” pages like About us, you have full time weeks to look into WPML.
I suggest you say : No, WPML not supported, maybe in future.
I been working with WPML in many years, and also using your plugin in some installs. As you do a great job with your plugin baby, I suggest you consider this when starting “translation plugins support” and cut down a week or two:
Set first GOAL: As this plugin load schemas from ‘saved’ (post) meta. A translated page must transfer your meta on creation. BUT not be synced to follow ‘master page’ custom field changes.
This can be done by 1) coded manually, or 2) make it clear for the users to check Your (schema plugin) meta field(s) in WPML settings “dublicate” data rules on custom fields settings, and much more, or 3) XML file config file – forcing WPML to follow some rules. But the latter would (propably) not be enough for your plugin.
The problem will occur when user changes the master and expect the translations to follow. To avoid master’s schemas titles and images to show up on translated pages schemas, the meta must be re-rendered “individually”, and with that your time-stamp update check system.
You propably end up learning the WPML trid ‘id’ functions, parsing all siblings while one is changed.
Unf, WPML documentations sucks and support takes weeks before get development-level-answers. However WPML is the best multilang tool by far, on advanced pro installs.
as CONFORT
I think your functions grabs the current page view id as key to render all the schemas stuff, and WPML translated architecture is just individual posts/ terms, the front end would not be any issues at all as it is.
BTW:
Your main meta key name should not be hidden with _underscore, it should be easy to find for admins, and also most plugins tries to find you, if you NOT using hidden namespaces for crucial combat fields. WPML has ‘one click theme copatibility checkbox’ but I doubt that will solve this problem. However, this checkbox is not recommended on pro installs as it slow down the site.
Good luck
