Why are plugin dependencies different between my instances?

[Joshua Berger]

I am trying to activate com.snc.knowledge_advanced.installer plugin, to have the article version and template features.  I have tested this in one instance without issue. When I try to activate it in another instance the dependencies are different. Now it will not let me activate without the com.glide.localization_framework pluggin, translation features I don't want. I have confirmed in the first instance com.snc.knowledge_advanced.installer is active and the article version and template features function, and the com.glide.localization_framework plugin is inactive. 

Is there a way to install and ignore plugin decencies? Why can I do this in one instance and not the other? 

[Mike_R · Accepted solution]

I think this warrants opening up a support case with ServiceNow.

[Mike_R]

That seems strange. Can you post a screenshot of what you see when you go to install Knowledge Management Advanced Installer (com.snc.knowledge_advanced.installer)?

[Joshua Berger]

First instance, com.snc.knowledge_advanced is active

And com.glide.localization_framework is inactive: 

On the second instance, when I try to install com.snc.knowledge_advanced this is what I see: 

It won't proceed without the com.glide.localization_framework

I've tried this in both dev and production instances, and in a private dev instance in Rome and Tokyo. Sometimes it's required, sometimes it's not.

[Mike_R · Accepted solution]

I think this warrants opening up a support case with ServiceNow.

[Joshua Berger · Accepted solution]

Update for anyone else running into this problem: 

We just activated the plugin through the 'automation store' on the Now Support page. The unwanted plugin dependency was not activated, and the plugin I wanted activated successfully.