@kalavan is correct.
I have updated the to 2.0.0, still having the same problem. I see @shadowwolf218 recommendation is implemented, but its not working for me. The main reason is that, in the player, ".mediaelementjs" referenced multiple times, that breaks the player.
So I have created a patch for it.
And again I am using 4.2.x version of the player. Currently its 7.0.x. Using this patch the player is working, but there is a change after 4.2.x, the location of mejs-controls.svg file, its now in configuration. Using 7.0 player version, console shows its missing, as a result the main play button is missing. For that, I think path of mejs-controls.svg need to provide, which actually can be done through standalone call.
iconSprite: 'mejs-controls.svg'
Here is the patch
shafiqhossain → created an issue.
My opinion:
I see lot of sites are migrating from Drupal to elsewhere everyday. I think major issue is that, there are lot of potential contributed modules, which were in Drupal 7, either not migrated to Drupal 10, or not in stable or stay behind the Drupal version.
A simple example, Drupal Commerce module or Ubercart. Using Drupal 9/10 I did not able to deliver a complete eCommerce site yet. Either related modules are not migrated or currently using old API or giving error due to jQuery migration, or PHP version mismatch or third party API dependency version not matched or behind the Drupal version (e.g. Payment gateway modules, Shipping modules or Market place modules). And I am stuck with that for long. Previously in Drupal 7 we have lot of modules. And surely eCommerce is a major part of any CMS.
This is similar for other modules. Its sure there are lot of modules migrated, but still there are lot of modules left as well. For two clients, I am unable to migrate from 9.5 to 10, because some of the modules, still don't have any Drupal 10 release.
Due to this, all projects are in limbo. What to say to the client? Client will not accept to wait further to move on. I think for this reason, developers have to move on into another platform.
BTW, I am willing to help in any projects to move on!
shafiqhossain → created an issue.
shafiqhossain → created an issue.
Update:
This error is linked to Field Layout core module. The error start showing when I was trying to uninstall the Field Layout module. Rather showing the confirmation, it shows the error. Then whatever module I tried to uninstall, it shows the same error.
So I re-installed the RDF module. After some time (I don't know what I did), I see I can see other modules un-install confirmation page. And when I tried to uninstall the Field Layout module, it start showing the error, and keep showing when I tried other modules to un-install.
shafiqhossain → created an issue.