I can't find a better way... is the only way to test for a module
plugin is by trapping the error "PluginService.ModulePluginNotFound"?
Just thinking a hasPlugin might be useful but I don't see it.
thanks,
.brett
I can't find a better way... is the only way to test for a module
plugin is by trapping the error "PluginService.ModulePluginNotFound"?
Just thinking a hasPlugin might be useful but I don't see it.
thanks,
.brett
Yea that does naot exist yet. You can
Also get the module settings instantiation path and then do a file exists
Okay will do. Obviously low priority...
thanks,
.brett