I did a clean install of 3.5.2, then proceeded to install the Media Player Advance plugin. After the installation steps had completed and I pressed the final "Continue" button, I couldn't get anything but a white screen no matter which page I tried to navigate to.
After turning debugging on and repeating the process, I got the following errors after clicking the button:
And these when trying to navigate to the front page afterwards:
I also tried installing another plugin and that worked without problems, so I'm guessing the problem is in the plugin code. I'm not sure where to report it after looking at the information on this site. I don't think it should be allowed to take the whole site down, though.
Results of some further research:
I don't think it should be allowed to take the whole site down, though.
Absolutely. This is one of the things gpEasy 3.6 will do much better. Plugin hooks that result in fatal errors will automatically be disabled.
I'm guessing the problem is in the plugin code
There's no /<INSTALL_DIR>/data/_addondata/ directory
I'm a little worried there's something going on with gpEasy here. The missing addondata folder is a little concerning, but I'm even more concerned about the /data/_addoncode folder. Does "/data/_addoncode/icesta6/dominion-mp3player/plugins" exist?
It's good to hear that this will be handled better in the next release!
The directory plugins does exist:
You can download a zip archive of my data-folder, if it helps.
I haven't tried this plugin yet but it might be helpful: http://ckeditor.com/addon/oembed
It would be easy to add to gpEasy 3.6rc3.
It seems I had disabled email updates for this topic by accident.
Thanks for the suggestion! That seems interesting and I'll need to try it out when building a site myself. It isn't really suitable for this purpose, though. Understanding, installing and using gpEasy plugins is hard enough for many of the students, so I'll avoid adding the complexity of explaining what CKEditor is and how to install plugins for it. Also, the audio to embed is a local file and a quick glance seems to suggest that this plugin doesn't handle those.
My solution was to drop audio embedding from the things we practice and explain some ways to do it in supplemental material for those interested in delving deeper.