Thanks @paulmatth, apparently Sébastien (the developer of the plug-in interface) has fixed this, last friday, so it should working as expected for the next release (2.3.6).
Thanks @paulmatth, apparently Sébastien (the developer of the plug-in interface) has fixed this, last friday, so it should working as expected for the next release (2.3.6).