As best I can tell, osTicket does not have true "plugins". There are "mods" that are simply hacks of the code. By their very nature, these can break existing functionality, possibly in hidden ways that compromise security. Even if they work with the current version, any future version could break them or be broken by them (if they don't get overwritten in version upgrades).My suggestion is to add true plugin support, for discrete, modular plugins. The Wordpress model would be a great example. In that case plugins must meet certain standards. Then they simply go into a plugin directory, and they can be installed, enabled, disabled, and removed from the Admin interface. Plugins don't have ugly tentacles embedded into the site software, their entire codebase is in their own directory in /plugins. If a site upgrade breaks a plugin, simply disable it until the plugin author publishes an update. That's how they OUGHT to work.Jack