heula 189 Posted June 30, 2016 Share Posted June 30, 2016 I have this in my keymap.xml and that worked fine until 2.2.10 <?xml version="1.0" encoding="UTF-8"?> <keymap> <global> <keyboard> <d>RunPlugin(plugin://plugin.video.emby?mode=delete)</d><!-- Delete emby item context menu shortcut will activate when pressing "d" --> </keyboard> </global> </keymap> Then I see this text in Emby for Kodi beta topic Version 2.2.10 This is the last beta, I'll be releasing to stable in a few hours. This build is mostly for small fixes. New: Keymap shotcut to delete emby content using: RunPlugin(plugin://plugin.video.emby?mode=delete). The skip confirmation deletion does apply, please be careful with enabling the setting. It may take a few seconds to see the content disappear (this is a shortcut for the Emby context menu options > Delete). I changed my line from <d>RunPlugin(plugin://plugin.video.emby?mode=delete)</d><!-- Delete emby item context menu shortcut will activate when pressing "d" --> to RunPlugin(plugin://plugin.video.emby?mode=delete) but then nothing happens. With the old line I will get an error. Kodi log What must I do to have the delete option working again. Thanks Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted June 30, 2016 Share Posted June 30, 2016 (edited) What must I do to have the delete option working again. Very easy - report the problem as soon as you see it and it will get fixed. Give this build a try, let me know if it resolves your issue. Thanks Edited June 30, 2016 by Angelblue05 Link to comment Share on other sites More sharing options...
heula 189 Posted July 1, 2016 Author Share Posted July 1, 2016 Very easy - report the problem as soon as you see it and it will get fixed. Give this build a try, let me know if it resolves your issue. Thanks I thougt it was already fixed because I saw another topic with the same issue in 2.2.11 Version 2.2.13 alpha works perfect again. Thanks 1 Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted July 1, 2016 Share Posted July 1, 2016 Thanks for confirming! Ahhh, yeah it was a different bug. The fix will be in the next beta version. 1 Link to comment Share on other sites More sharing options...
Recommended Posts