Issue with new media field, IF no API key configured, then old VIdeo Data are lost

Hello

the code example was mean to say,
- that we did not intentionally break anything
- you are not supposed to understand it , just see that the code is supposed to be compatible

about API Key required that is another topic,
embeed.ly supports more video source, but it is not obligatory,

- you can still use native APIs (that is what you were using in previous versions)
but note youtube API is being changed and that was a reason for this change

so we turned to embeed.ly but also after some effort we restored support for youtube new API

for access do
- create a NEW super admin account
- send me a PM with access
- delete the super admin account after we are done
[i delete PMs with access after a few days anyway]

sent ( i have to understand what was a PM on your site)

Hello

you may send me A PM, by
- clicking on my profile
- then click "Send message"

Hello

i checked no bug,

but 2 things
- you have not enabled "Use native APIs" in configuration of ALL sharemedia fields (at the LAST Tab)

- after enabling Use native APIs (i have done this)
then you still need YOUTUBE API V3 key

and if you save form without KEY then YES you loose your data
- about YOUTUBE API V3 key

it is requirement of YOUTUBE new API, we can not do something and the old API will stop working soon
so this change was not enforced by US

here is what to do:
- get YOUTUBE API key from ... developers.google.com/youtube/v3/getting-started
- then you can click to load older item version for items that you have saved already and you lost the data
so your data were not lost (should not be ) , unless you have saved more than 5 times

- but there is an issue that we need to keep OLD data ... if user has not configured a key yet !!!
that was a shortcoming on our side
- because users may not get KEY immediately ...

this will be addressed in v3.0.14 final
- so that if users does not have KEY yet the old data wil be preserved on item save

i am not sure i understand all : it will no be enough to have the video url to use the field ?
Once again why do we need an api key ?